Testing The Path From Your Computer To A Remote Device - NETGEAR DG632 Reference Manual

In the field provided, type Ping followed by the IP address of the router, as in this example:
2.
ping 192.168.0.1
Click OK.
3.
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 functioning 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, follow the instructions in
or WAN Port LEDs Not On"
— 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 router.
• 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 router and your workstation are correct and that the
addresses are on the same subnet.

Testing the Path from Your Computer to a Remote Device

After verifying that the LAN path works correctly, test the path from your PC to a remote device.
From the Windows run menu, type:
PING -n 10 <IP address>
where <IP address> is the IP address of a remote device such as your ISP's DNS server.
If the path is functioning correctly, replies as in the previous section are displayed. If you do not
receive replies:
Troubleshooting
Reference Manual for the Model DG632 ADSL Modem Router
on page 7-2.
"LAN
7-7