Netgear DGN2200M DGN2200M User Manual (PDF) - Page 106

Troubleshooting a TCP/IP Network Using the Ping Utility

Page 106 highlights

N300 Wireless ADSL2+ Modem Router DGN2200M Mobile Edition User Manual Troubleshooting a TCP/IP Network Using the 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. You can easily troubleshoot a TCP/IP network by using the ping utility in your computer. Testing the LAN Path to Your Wireless-N Modem Router You can ping the router from your computer to verify that the LAN path to your router is set up correctly. To ping the router from a PC running Windows 95 or later: 1. From the Windows toolbar, click the Start button, and select Run. 2. In the field provided, type ping followed by the IP address of the router, as in this example: ping 192.168.0.1 3. 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 that the LAN port LED is on. If the LED is off, follow the instructions in Troubleshooting with the LEDs on page 100. - 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. In the Windows Run screen, type: 106 | Chapter 7. Troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123

106
|
Chapter 7.
Troubleshooting
N300 Wireless ADSL2+ Modem Router DGN2200M Mobile Edition User Manual
Troubleshooting a TCP/IP Network Using the 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. You can easily
troubleshoot a TCP/IP network by using the ping utility in your computer.
Testing the LAN Path to Your Wireless-N Modem Router
You can ping the router from your computer to verify that the LAN path to your router is set up
correctly.
To ping the router from a PC running Windows 95 or later:
1.
From the Windows toolbar, click the
Start
button, and select
Run
.
2.
In the field provided, type
ping
followed by the IP address of the router, 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 functioning correctly, you could have one of the following problems:
Wrong physical connections
-
Make sure that the LAN port LED is on. If the LED is off, follow the instructions in
Troubleshooting with the LEDs
on page 100.
-
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. In the Windows Run screen, type: