Testing The Lan Path To Your Router; Testing The Path From Your Computer To A Remote Device - NETGEAR WNR612v2 User Manual

Wireless-N 150 Router WNR612v2 User Manual

Testing 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 running Windows PC:
From the Windows toolbar, click Start, and then select Run.
1.
In the field provided, type ping followed by the IP address of the router, as in this example:
2.
ping www.routerlogin.net
Click OK.
3.
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
•
For a wired connection, make sure that the numbered LAN port light is on for the
-
port to which you are connected. If the light is off, follow the instructions in
Troubleshooting Basic Functions
Check that the appropriate LEDs are on for your network devices. If your router
-
and computer are connected to a separate Ethernet switch, make sure that the
link lights are on for the switch ports that are connected to your computer and
router.
Wrong network configuration
•
Verify that the Ethernet card driver software and TCP/IP software are both
-
installed and configured on your computer.
Verify that the IP address for your router and your computer 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 computer to a remote
device.
From the Windows toolbar, click the Start button, and then select Run.
1.
In the Windows Run window, type:
2.
ping -n 10 <IP address>
where <IP address> is the IP address of a remote device such as your ISP's DNS server.
on page 77.
Chapter 7: Troubleshooting | 81