Test TCP/IP

When you have installed TCP/IP on all the machines, they should all be able ping the WinGate machine. We will explain this shortly. Ping is a useful utility that comes with TCP/IP. Pinging a computers IP address sends out a message to that IP address saying “Are you there”. The pinged machine sends a reply.

Ping the WinGate machine

At the command line type:

ping 192.168.0.1

The response should be

Pinging [192.168.0.1] with 32 bytes of data

Reply from 192.168.0.1: bytes=32 time<=10ms TTL=32

Reply from 192.168.0.1: bytes=32 time<=10ms TTL=32

Reply from 192.168.0.1: bytes=32 time<=10ms TTL=32

Reply from 192.168.0.1: bytes=32 time<=10ms TTL=32

That is the sign that TCP/IP is working. This result should be the same from any machine on the network. If this is the case move on to the next step.

Note:

If you get a

Destination host unreachable

Or a

Bad IP

Then you need to check your TCP/IP settings as mentioned earlier.

Ping an external site

At the command line type:

ping www.cnn.com

Any machine on the network except the WinGate machine should produce this response, (although the IP may vary)

Pinging cnn.com [207.25.71.29] with 32 bytes of data

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Or if you have defined a default Gateway (192.168.0.4 in this example, don’t worry what this means)

Pinging cnn.com [207.25.71.29] with 32 bytes of data

Reply from 192.168.0.4: Destination host unreachable.

Reply from 192.168.0.4: Destination host unreachable.

Reply from 192.168.0.4: Destination host unreachable.

Reply from 192.168.0.4: Destination host unreachable.

This means that DNS is working. The DNS has looked-up the name, and returned the corresponding IP address.

Note: You can never get response times for an external computer (eg www.cnn.com) from a workstation, ie one that is connected via WinGate.