Testing TCP/IP using Telnet and Ping

If you are experiencing problems connecting to your FTGate machine from a workstation, you will need to test the TCP/IP network connection, without using the mail client. This is done by using two very useful utilities windows installs on your system for you. These are Ping and Telnet; together they will help you to establish whether there is a problem with the Network or TCP/IP connection to the FTGate machine/server. First follow these steps to test your TCP/IP network connection. Note: Ping and Telnet are installed with the TCP/IP protocol.

 

Ping to the FTGate machine

 

Using one of your workstations (users machines) bring up the DOS screen Start | Programs | MS-DOS prompt. At the DOS prompt (C:\ or C:\Windows) type ‘Ping ftgatemachinename’ (no quotes) and press Enter. Replace ftgatemachinename with the LAN name of the Machine FTGate is running on.

 

Below is the result of a successful "ping"."clarabel" is the name of a computer machine on our network. It has the IP number 194.70.211.227 NOTE: The reply from clarabel lists 0ms (no milliseconds) as the "Approximate round trip time", this is due to our fast 100Mb network. Your reply is likely to be slower, and this is quite normal.

 

 

If your response is similar to this, continue on to the Telnet section.

 

An unsuccessful ping will return a response similar to this:

 

 

If the "ping" fails you need to check your TCP/IP set-up in the Network Neighborhood. Here is a list of a few things to check on both the FTGate machine and the Workstation:

On a Peer-to-Peer network:

  1. Is TCP/IP installed on the TCP/IP page of the Network Neighborhood properties?

  2. Yes, Good. Move on to number 2

    No, You will need to install it, by clicking ‘Add’ and selecting ‘Protocol’ then select Microsoft on the left pane, then TCP/IP on the right pane, then click ok. Note: You will need the Windows CD at this point.

  3. Is there an IP number defined on the TCP/IP page of the Network Neighborhood properties?

  4. Yes, Note the number and Subnet Mask number. Move to number 3

    No, You will need to add one and the machine name if it has not got one.

  5. Is the Subnet Masks the same, on each machine, across the network?

  6. Yes, Move on to number 4

    No, You will need to ensure all machines use the same Subnet Mask, correct them where necessary.

  7. Is there a hosts file defined on all systems and placed in the C:\Windows folder of all machines?

  8. Yes, move on to number 5

    No, You will need to create one.

  9. Is the ‘hosts’ (no quotes) file named only hosts with NO extension?

  10. Yes, try again from the top.

    No, you need to save the hosts file with no extension for it to work.

  11. If you are running a third party DHCP server, is it set-up correctly?

 

Note: There is a file called hosts.sam in the windows folder with full instructions on the location and format of the hosts file. The only thing it does not include is the "No extension" part.

On an NT server based network (server and workstation checks)

  1. Is TCP/IP installed on the TCP/IP page of the Network Neighborhood properties?

  2. Yes, Move on to number 2

    No, You will need to install it, by clicking ‘Add’ and selecting ‘Protocol’ then select Microsoft on the left pane, then TCP/IP on the right pane, then click ok. Note: You will need the Windows CD at this point.

  3. Is there an IP number defined on the TCP/IP page of the Network Neighborhood properties?

  4. Yes, Is the Subnet Mask defined for this machine, the same as the Subnet Mask on the other machines?

    No, Move on to number 3

  5. If you are using DHCP (dynamic IP assignment) has the DHCP scope been defined with the same Subnet Mask as the static IP’s Subnet Mask of the server?

  6. Yes, Move on to number 4

    No, Change the Subnet Mask in the DHCP scope to the same as the one defined in the Server’s TCP/IP properties.

  7. Is the DHCP scope active?

  8. Yes. Click ok and carry on, the server will prompt you to re-start, it may be a good idea to restart at this point.

    No, Activate it from the DHCP manager using the route Start | Administration tools | DHCP server manager

  9. Are there enough IP numbers available in the Scope?

Yes, retry the ‘ping’

    No, you will need to redefine the scope to allow more IP numbers for the number of machines you have.

 

You may need to remove and re-install TCP/IP on the workstation and/or the FTGate machine in either the Peer-to-Peer or Server based network if you are unable to carry out a successful ping. When you have made any necessary corrections to the systems and you get a successful ‘Ping’ to the FTGate machine you can then go on to the next section Telnet.

Telnet to the SMTP server in FTGate

To start a telnet session, ensure the SMTP & POP3 servers are enabled on the SMTP and Ports properties pages respectively. Press the start button then select and press ‘Run’ type in the following line:

telnet ftgatemachinename 25

 

 

(Remember: clarabel is a machine on our network)

Then press Enter. You will see a window like this one come up (the text line will appear a few seconds after the window has opened).

 

 

Telnet to the POP3 server in FTGate

To start a telnet session press the start button then select and press ‘Run’ type in the following line

telnet ftgatemachinename 110

 

 

(Remember: clarabel is a machine on our network)

 

Then press Enter, you will see a window like this one come up, (the text line will appear a few seconds after the window has opened). Note the different text in the telnet window, this is because you are connected to the different server, POP3

 

 

If your ping and telnet to FTGate are successful you should be able to connect to your mail server using one of the popular mail clients currently available on the market today.

 

If either Telnet fails check the items on the list below:

 

1. Is FTGate running?

Yes. Move on to 2.

No. FTGate must be running to allow a connection to it whether it is a telnet session or for mail transfer

 

2. Is the relevant server enabled in FTGate?

To connect to either the SMTP or POP3 servers in FTGate they need to be enabled.

Check the SMTP server is Started on the Services List page.

Check the POP3 server is Started on the Services List page.

 

3. Is the relevant server bound to an IP number/address?

The SMTP & POP servers should not be bound to any IP number/address.

Check the SMTP server is set to "Any unbound address" on the SMTP Service's properties page.

Check the POP3 server is set to "Any unbound address" on the POP3 Service's properties page.

 

4. Is the port number correct, SMTP = 25, POP3 = 110?

The SMTP & POP3 servers should be set to use these ports by default.

 

Check the SMTP server is set to use port 25 on the SMTP Service's properties page.

Check the POP3 server is set to use port 110 on the POP3 Service's properties page.

 

Notes: SMTP = Simple Mail Transfer Protocol

POP3 = Post Office Protocol version 3