
We occasionally receive reports that a customer's mail program is unable to connect to our servers. In most cases, restarting your computer will solve this kind of problem.
If restarting the computer doesn't help, the rest of this page explains how to tell if the problem is with the mail program, or if something else (such as a firewall on your computer or at your ISP) is blocking the connections.
As mentioned above, please try restarting your computer as a first step. This will fix many connection problems.
If you are connecting to the Internet via a wireless network, your computer may have connected to a different wireless network than you expected it to. Check your wireless network connection to verify how you are connecting to the Internet.
Click here to see your current IP address and hostname. (The right-most part of your hostname will indicate how you are connecting to the Internet.)
The first thing to try is temporarily disabling any firewall software you use. (What a firewall really does is block certain connections. If some connections are mysteriously getting blocked, it may be caused by firewall software that has decided the connections are "suspicious".)
We have instructions explaining how to disable the Windows Firewall software and the firewalls included in various Norton Internet Security and Norton AntiVirus products. If you use different firewall software, please see the instructions that came with that software.
If temporarily disabling the firewall allows you to connect to our servers, you should review the documentation that comes with the software to learn how to tell it to allow normal e-mail connections with the firewall turned on. If you have trouble, please contact the company that makes the program for assistance.
If you are just having problems sending messages, and you can receive mail from other people, then your ISP may be blocking your outgoing connection. Check that your e-mail program is set to use port 587 for outgoing mail. If it's using port 25 try changing the outgoing port number to 587.
After changing the port number, move (or delete) any messages in the outbox and try sending a new message. If successful, then try recreating the other messages (don't send the previous ones that were in the outbox).
The next thing we recommend if your mail program still can't connect is trying a different mail program to see if it works. A popular free mail program is Mozilla Thunderbird. You can download and install it at no charge, then follow our Thunderbird setup instructions to see if it works. If it does, you'll know that your connections aren't being blocked.
If you can't get a different mail program to work, either, you can try a different kind of test. The instructions below explain how to make a text-based connection to our mail servers, mimicking what your mail program usually does invisibly.
You can do this in a few easy steps:
Telnet is not installed by default on Windows Vista, so you may need to activate it. You can skip this step if you use Windows XP or Mac OS X.
To open a command window:
Once the command window is open, type this text and press "Enter" if you're having trouble with incoming mail:
telnet mail.tigertech.net 110
You should see these two lines (among others) in the response:
Connected to something.tigertech.net. +OK POP3 ready
(The "something" may be any word.)
Similarly, if you're having trouble with outgoing mail, type this and press "Enter":
telnet mail.tigertech.net 587
And you should see these two lines (among others) in the response:
Connected to something.tigertech.net. 220 something.tigertech.net ESMTP Postfix
(Again, don't worry about what the "something" is.)
If you don't see these lines in the response, contact us and let us know exactly what you do see, because it means that something is blocking your computer's connections to our mail servers. Please be sure to copy and paste all of the command window text into your message to us, since it's all important. We'll do our best to help you figure out what's causing the problem, although in some cases you may need to ask your network administrator.
(By the way, you can just close the command window when you're finished with the tests above.)