Netgear MBR1310 MBR1310 User Manual - Page 92

Troubleshoot a TCP/IP Network Using the Ping Utility, Test the LAN Path to Your Router

Get Netgear MBR1310 PDF manuals and user guides View all Netgear MBR1310 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 92 highlights

NETGEAR Mobile Broadband 11n Wireless Router MBR1310 configuration, reboot your computer and verify the DNS addresses. Alternatively, you can configure your computer manually with DNS addresses, as explained in your operating system documentation. • Your computer might not have the router configured as its TCP/IP router. If your computer obtains its information from the router by DHCP, reboot the computer, and verify the router address. Troubleshoot 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. Test the LAN Path to Your 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 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 working correctly, you could have one of the following problems: • Wrong physical connections - Make sure that the ACT LED is on. If the LED is off, follow the instructions in Basic Functioning on page 88. - 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. Troubleshooting 92

  • 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
Troubleshooting
92
NETGEAR Mobile Broadband 11n Wireless Router MBR1310
configuration, reboot your computer and verify the DNS addresses. Alternatively, you can
configure your computer manually with DNS addresses, as explained in your operating
system documentation
.
•
Your computer might not have the router configured as its TCP/IP router.
If your computer obtains its information from the router by DHCP, reboot the computer,
and verify the router address.
Troubleshoot 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.
Test the LAN Path to Your 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 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 working correctly, you could have one of the following problems:
•
Wrong physical connections
-
Make sure that the ACT LED is on. If the LED is off, follow the instructions in
Basic
Functioning
on page 88.
-
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.