NETGEAR CG814WG V3 - Manual (Page 56)

Wireless Cable Modem Gateway CG814WG v3 Reference Manual
5-4 Troubleshooting
v1.0, June 2007
Troubleshooting a TCP/IP Network Using a Ping Utility
Most TCP/IP terminal devices and routers contain a ping utility that sends an echo request packet
to the designated device. The device then responds with an echo reply. Troubleshooting a TCP/IP
network is made easier by using the ping utility in your PC or workstation.
Testing the LAN Path to Your Gateway
You can use ping to verify that the LAN path to your gateway is set up correctly.
To ping the gateway from a PC running Windows 95 or later:
1. From the Windows toolbar, click on the Start button and select Run.
2. In the field provided, type Ping followed by the IP address of the gateway, as in this example:
ping 192.168.0.1
3. Click OK.
You should see a message like this one:
Pinging <IP address> with 32 bytes of data
If the path is working, you see this message:
Reply from < IP address >: bytes=32 time=NN ms TTL=xxx
If the path is not working, you see this message:
Request timed out
If the path is not working correctly, you could have one of the following problems:
• Wrong physical connections.
– Make sure the LAN port LED is on. If the LED is off, see “Using LEDs to
Troubleshoot” on page 5-2 .
– Check that the corresponding Link LEDs are on for your network interface card and
for the hub ports (if any) that are connected to your workstation and gateway.
• Wrong network configuration.
– Verify that the Ethernet card driver software and TCP/IP software are both installed
and configured on your PC or workstation.
– Verify that the IP address for your gateway and your workstation are correct and that
the addresses are on the same subnet.