There might be network problems between you and the Runbox servers, your Internet Service Provider might be blocking certain types of connections, or there could be problems within the Runbox services.

  • To see whether there are any known service disruptions within Runbox, please see our Service Status posts .
  • To confirm that the Runbox servers are running and responding to requests you can use third-party tracking services such as host-tracker.com.

To verify that you can connect to the Runbox servers, you can follow these procedures (on Windows; similar commands are available on other platforms).

Verify network connection to Runbox with ping

  1. Click “Start”, then “Programs”, “Accessories”, and select “Command Prompt”.
  2. In the Command Prompt window that opens, enter ping runbox.com and press [Enter].
  3. A number of lines will appear in the window, showing connection information for each packet sent from your computer to Runbox.
  4. You can copy the output and email it to Runbox Support and/or your ISP to investigate the problem.

Verify network connection to Runbox with traceroute

  1. Click “Start”, then “Programs”, “Accessories”, and select “Command Prompt”.
  2. In the Command Prompt window that opens, enter tracert runbox.com and press [Enter].
  3. A number of lines will appear in the window, showing connection information for each server your computer is connecting to on the way to Runbox.
  4. The last line should read “aibo.runbox.com” in the 5. column. Otherwise there might be network problems between you and the Runbox servers at the point indicated by the last legible line. You can copy the output and email it to Runbox Support and/or your ISP to investigate the problem.

Verify POP connection with telnet

  1. Click “Start”, then “Programs”, “Accessories”, and select “Command Prompt”.
  2. In the Command Prompt window that opens, enter telnet secure.runbox.com 110 and press [Enter].
  3. If a Runbox server responds with a string like +OK <27887.1129232543@garm.runbox.com>, you are connected to a Runbox POP server.
  4. To close the connection, skip to #8. If you would like to log in to your account, proceed with #5.
  5. To log in, enter user [username], replacing [username] with your Runbox username. Press [Enter].
  6. Enter pass [password], replacing [password] with your Runbox password. Press [Enter].
  7. The server should respond with +OK.
  8. Enter quit to disconnect from the server, and then exit to close the Command Prompt window.

Verify IMAP connection with telnet

  1. Click “Start”, then “Programs”, “Accessories”, and select “Command Prompt”.
  2. In the Command Prompt window that opens, enter telnet secure.runbox.com 143 and press [Enter].
  3. If a Runbox server responds with a string like * OK IMAP4 Ready patch 000201f1, you are connected to a Runbox IMAP server.
  4. To close the connection, skip to #7. If you would like to log in to your account, proceed with #5.
  5. To log in, enter . login [username] [password] (including the period), replacing [username] and [password] with your Runbox login data. Press [Enter].
  6. The server should respond with . OK LOGIN Ok..
  7. Enter . logout to disconnect from the server, and then exit to close the Command Prompt window.

Verify SMTP connection with telnet

  1. Click “Start”, then “Programs”, “Accessories”, and select “Command Prompt”.
  2. In the Command Prompt window that opens, enter telnet secure.runbox.com 25 and press [Enter].
  3. If a Runbox server responds with a string like 220 penny.runbox.com ESMTP Exim 4.34 Thu, 13 Oct 2005 21:51:00 +0200, you are connected to a Runbox SMTP server. If you get no response, your ISP might be blocking port 25. Try port 26 or 587 instead.
  4. Enter quit to disconnect from the server, and then exit to close the Command Prompt window.