Netgear MR314 Reference Guide - Page 86

LNK/ACT or LNK LEDs Not On, - driver

Get Netgear MR314 - Wireless Router PDF manuals and user guides
UPC - 606449022148
View all Netgear MR314 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

Reference Guide for the Model MR314 Cable/DSL Wireless Router 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 the LAN LNK/ACT LED is on. If the LNK/ACT LED is off, follow the instructions in "LNK/ACT or LNK LEDs Not On" on page 7-2. - 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 PC to a Remote Device After verifying that the LAN path works correctly, test the path from your PC to a remote device. From the Windows run menu, type: PING -n 10 where is the IP address of a remote device such as your ISP's DNS server. If the path is functioning correctly, replies as in the previous section are displayed. If you do not receive replies: - Check that your PC has the IP address of your router listed as the default gateway. If the IP configuration of your PC is assigned by DHCP, this information will not be visible in the control panel network utility. Go to the Run... window and run winipcfg. The IP address of the router should appear as the Default Gateway. - Check to see that the network address of your PC (the portion of the IP address specified by the netmask) is different from the network address of the remote device. 7-6 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
Reference Guide for the Model MR314 Cable/DSL Wireless Router
7-6
Troubleshooting
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 the LAN LNK/ACT LED is on. If the LNK/ACT LED is off, follow the
instructions in
“LNK/ACT or LNK LEDs Not On
” on
page 7-2
.
— 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 PC to a Remote Device
After verifying that the LAN path works correctly, test the path from your PC to a remote device.
From the Windows run menu, type:
PING -n 10
<
IP address
>
where <
IP address
> is the IP address of a remote device such as your ISP’s DNS server.
If the path is functioning correctly, replies as in the previous section are displayed. If you do not
receive replies:
— Check that your PC has the IP address of your router listed as the default gateway. If the IP
configuration of your PC is assigned by DHCP, this information will not be visible in the
control panel network utility. Go to the Run… window and run winipcfg. The IP address
of the router should appear as the Default Gateway.
— Check to see that the network address of your PC (the portion of the IP address specified
by the netmask) is different from the network address of the remote device.