Troubleshooting A Tcp/Ip Network Using A Ping Utility; Testing The Lan Path To Your Router - NETGEAR RT338 Reference Manual

Reference Guide for the Model RT338 ISDN Router

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 responds with an echo reply. Troubleshoot a TCP/IP network
by using the ping utility in the built-in Manager interface (Menu 24.4) or in the PC or workstation.

Testing the LAN Path to Your Router

To verify that the LAN path to the router is set up correctly:
Ping the router from your computer.
1.
On a PC using Windows 95 (Windows 98 or Windows NT), click Start and select Run.
2.
In the Run dialog box, type "Ping" followed by the IP address of the router. For example:
3.
ping 192.168.0.1
Click OK.
4.
The following message may appear:
Pinging <IP address> with 32 bytes of data
If the path is working, the following message may appear:
Reply from <IP address>: bytes=32 time=NN ms TTL=xxx
If the path is not working, the following message may appear:
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 LINK/ACT LED is lit. If not, follow the instructions in
Link LED" on page
— Check that the corresponding Link LED is on for the network interface card and the
hub port (if any) is connected to the workstation or router.
• Wrong network configuration
— Verify that the Ethernet card driver software and TCP/IP software are both installed
and configured on the PC or workstation.
— Verify that the IP address for the router and the workstation are correct. Make sure that
the addresses are on the same subnet.
12-4
12-2.
"LAN
Troubleshooting