N150 and N300 Wireless Routers
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 might have one of the following problems:
•Wrong physical connections
For a wired connection, make sure that the numbered Ethernet port LED is lit for the port to which you are connected.
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 LEDs are lit 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.
Test 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.
1.From the Windows toolbar, click the Start button and select Run.
2.In the field provided, type: ping
where <IP address> is the IP address of a remote device such as your ISP DNS server.
If the path is functioning correctly, replies like those examples shown in Test the LAN Path to Your Router on page 72 are displayed.
If you do not receive replies, try the following:
•Check that your computer has the IP address of your router listed as the default gateway. If a DHCP server assigns the IP configuration of your computer, this information is not visible on your computer’s Network Control Panel. Verify that the IP address of the router is listed as the default gateway.
•Check to see that the network address of your computer (the portion of the IP address specified by the subnet mask) is different from the network address of the remote device.
•Check that your cable or DSL broadband modem is connected and functioning.
Troubleshooting
73