Netgear WGX102NA Reference Manual - Page 105

Troubleshooting a TCP/IP Network Using a Ping Utility, Testing the LAN Path to the WGX102

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

Page 105 highlights

Reference Manual for the 54 Mbps Wall-Plugged Wireless Range Extender WGX102 Troubleshooting a TCP/IP Network Using a 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. Troubleshooting a TCP/IP network is made very easy by using the ping utility in your computer or workstation. Testing the LAN Path to the WGX102 You can ping the range extender from your computer to verify that the LAN path to your range extender is set up correctly. To ping the range extender from a PC 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 WGX102, as in this example: ping 192.168.0.101 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 the Wireless port LED is lit. - Check that the Link LEDs are on for your network interface card. - Using the Wireless configuration utility provided with your wireless client card, make sure the SSID of your client card is the same as the WGX102. The default is NETGEAR. - Make sure the security settings of your client card are the same as the WGX102. The default is to have WEP and WPA-PSK disabled. Troubleshooting 9-5 September 2004 202-10042-01

  • 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
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
Reference Manual for the 54 Mbps Wall-Plugged Wireless Range Extender WGX102
Troubleshooting
9-5
September 2004 202-10042-01
Troubleshooting a TCP/IP Network Using a 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. Troubleshooting a TCP/IP
network is made very easy by using the ping utility in your computer or workstation.
Testing the LAN Path to the WGX102
You can ping the range extender from your computer to verify that the LAN path to your range
extender is set up correctly.
To ping the range extender from a PC 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 WGX102, as in this example:
ping 192.168.0.101
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 the Wireless port LED is lit.
—
Check that the Link LEDs are on for your network interface card.
—
Using the Wireless configuration utility provided with your wireless client card, make
sure the SSID of your client card is the same as the WGX102. The default is
NETGEAR.
—
Make sure the security settings of your client card are the same as the WGX102. The
default is to have WEP and WPA-PSK disabled.