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

Testing the LAN Path to Your Router

To verify that the LAN path to your router is set up correctly:
Ping the router from your computer.
1.
On a PC running Windows 95 (or Windows 98 or Windows NT
2.
and select Run.
In the box provided, type Ping followed by the IP address of the router, as in this
3.
example:
ping 192.168.0.1
Click OK.
4.
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 Local LNK/ACT LED is on. If the LNK/ACT LED is off, follow the
instructions in
— 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.
12-4
"LAN Link LED" on page 12-2.
® ), click the Start button
Troubleshooting