Troubleshooting mail client connections to FTGate

Problems? û Questions and answers

 

These questions and answers should help track down the problem:

 

Q. Is the FTGate server running?

 

A. NO? Then you will need to start it. FTGate should be running at all times that you need to connect to it.

 

Q. Have you entered the correct machine name or IP number for the incoming and outgoing mail servers?

 

A. Check the machine name/IP number of the FTGate machine by typing winipcfg at the DOS (command) prompt (and press ENTER) on the FTGate machine.

 

Q. Is the IP number in the correct format, e.g. 192.168.0.1?

 

A. Any IP number must be in the correct format, i.e. four sets of numbers up to 255 each separated by a æ.Æ Full stop (period) - this is known as decimal notation.

 

Q. Is the user name correct, and spelt the same as the mailbox name?

 

A. Check the name of the mailbox on FTGate which you are trying to connect to. It should have the same spelling in FTGate and Outlook Express.

 

Q. Is the password correct? By default all mailboxes in FTGate are created with the password set to 'password' (no quotes).

 

A. Redefine the password in FTGate if you have problems with it. Change the password on the mailbox properties page in Web Admin.

 

Q. I am having problems connecting to the POP3 mailbox on the mail server. What should I do?

 

A. If you experience any difficulty connecting to the mailbox, use the full email address, e.g. user@domainname.com where user is the mailbox name within FTGate for the user you are setting up and domainname.com is your correct, registered domain name.

 

If you experience any further problems, you may need to add a hosts file to the windows folder on the client machine, to help the operating system identify the FTGate machine across the network.

 

See Do I need a hosts file in the Network issues section of this document for more information.

 

Further information is available with regard to testing the network connection, see Testing TCP using telnet and ping in the Troubleshooting section or this document for more information