Netgear RT338 RT338 Reference Manual - Page 187
Troubleshooting a TCP/IP Network Using a Ping Utility, Testing the LAN Path to Your Router
UPC - 606449004250
View all Netgear RT338 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 187 highlights
Trouble.fm Page 4 Friday, October 6, 2000 5:31 PM 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: 1. Ping the router from your computer. 2. On a PC running Windows 95 (or Windows 98 or Windows NT®), click the Start button and select Run. 3. In the box provided, type Ping followed by the IP address of the router, as in this example: ping 192.168.0.1 4. Click OK. You should see a message like this one: Pinging 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 "LAN Link LED" on page 12-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 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. 12-4 Troubleshooting