Netgear DGND3800B DGND3800B User Manual (PDF) - Page 140

TCP/IP Network Not Responding, Test the LAN Path to Your Modem Router - drivers

Page 140 highlights

N600 Wireless Dual Band Gigabit VDSL2 Modem Router DGND3800B TCP/IP Network Not Responding Most TCP/IP terminal devices and routers have a ping utility for sending an echo request packet to the designated device. The device responds with an echo reply to tell whether a TCP/IP network is responding to requests. Test the LAN Path to Your 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 Computer running Windows 95 or later: 1. From the Windows task bar, 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 LAN LED Is Off on page 136. - 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 computer or workstation. - Verify that the IP address for your router and your workstation are correct and that the addresses are on the same subnet. Troubleshooting 140

  • 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
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175

Troubleshooting
140
N600 Wireless Dual Band Gigabit VDSL2 Modem Router DGND3800B
TCP/IP Network Not Responding
Most TCP/IP terminal devices and routers have a ping utility for sending an echo request
packet to the designated device. The device responds with an echo reply to tell whether a
TCP/IP network is responding to requests.
Test the LAN Path to Your 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 Computer running Windows 95 or later:
1.
From the Windows task bar, 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
LAN LED Is Off
on page
136.
-
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 computer or workstation.
-
Verify that the IP address for your router and your workstation are correct and that
the addresses are on the same subnet.