Netgear WB7520 User Manual - Page 363

Check the Internet Browser, Troubleshoot a TCP/IP Network Using the Ping Utility

Page 363 highlights

ProSAFE Wireless Controller Check the Internet Browser If the Ethernet cabling and IP address configuration are fine, the Internet browser might prevent you from accessing the web management interface. Check the following: • Make sure that you are using the http://address login rather than the https://address login. • Make sure that Java, JavaScript, or ActiveX is enabled in your browser. If you are using Internet Explorer, click the Refresh button to be sure that the Java applet is loaded. • Try quitting the browser and launching it again. • Make sure that you are using the correct login information. The factory default login name is admin, and the password is password. Make sure that Caps Lock is off when entering this information. If the wireless controller does not save changes that you make in the web management interface, check the following: • When entering configuration settings, be sure to click the Apply button before moving to another tab or page, or your changes are lost. • Click the Refresh or Reload button in the web browser. It is possible that the changes occurred but that the old settings remain in the web browser's cache. After you upgrade the firmware, if the browser does not display the latest features of the web management interface, clear the browser's cache, and refresh the page. 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 troubleshoot a TCP/IP network by using the ping utility in your computer. You can ping the wireless controller from your computer to verify that the LAN path to your wireless controller is set up correctly.  To ping the wireless controller from a computer running Windows: 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 wireless controller, as in this example: ping 192.168.0.250 3. Click the OK button. A message like the following one displays: 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 Troubleshooting and Diagnostics 363

  • 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
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398

Troubleshooting and Diagnostics
363
ProSAFE Wireless Controller
Check the Internet Browser
If the Ethernet cabling and IP address configuration are fine, the Internet browser might
prevent you from accessing the web management interface. Check the following:
Make sure that you are using the http://address login rather than the https://address login.
Make sure that Java, JavaScript, or ActiveX is enabled in your browser. If you are using
Internet Explorer, click the
Refresh
button to be sure that the Java applet is loaded.
Try quitting the browser and launching it again.
Make sure that you are using the correct login information. The factory default login name
is admin, and the password is password. Make sure that Caps Lock is off when entering
this information.
If the wireless controller does not save changes that you make in the web management
interface, check the following:
When entering configuration settings, be sure to click the
Apply
button before moving to
another tab or page, or your changes are lost.
Click the
Refresh
or
Reload
button in the web browser. It is possible that the changes
occurred but that the old settings remain in the web browser’s cache.
After you upgrade the firmware, if the browser does not display the latest features of the web
management interface, clear the browser’s cache, and refresh the page.
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
troubleshoot a TCP/IP network by using the ping utility in your computer.
You can ping the wireless controller from your computer to verify that the LAN path to your
wireless controller is set up correctly.
To ping the wireless controller from a computer running Windows:
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 wireless controller, as in
this example:
ping 192.168.0.250
3.
Click the
OK
button.
A message like the following one displays:
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