Netgear WC7600 Reference Manual - Page 300

Resolve Problems with Access Points, Resolve Discovery Problems, Resolve Connection Problems

Page 300 highlights

ProSAFE Wireless Controller WC7600 When the date shown is January 1, 2000, the wireless controller has not yet successfully reached a network time server. Verify that the wireless controller can reach the Internet. If you have completed configuring the wireless controller, wait at least five minutes and check the date and time again. Resolve Problems with Access Points If you encounter access point discovery or connection problems, the information in this section might help you to resolve these problems. Resolve Discovery Problems If the wireless controller does not discover any or all access points, check the configuration of the wireless controller and access points. For all access points, check the following: • Make sure that the wireless controller is connected to the LAN (see Ethernet Port LEDs Are Not Lit on page 297). • Make sure that you have entered the correct IP range if the access points function in different VLANs, are behind an IP subnet, or are already installed and working in standalone mode (see Access Point Discovery Guidelines on page 120). • Make sure that the access points run at least their initial firmware release or a newer version. For firmware requirements, see NETGEAR ProSAFE Access Points on page 16. For local access points that are installed across a Layer 3 network, check the following: • Verify that access points that are already installed and working in standalone mode have SSH and SNMP enabled (which is the default setting). • Make sure that UDP port number 7890 is unblocked in the firewall. • Except for access points in factory default state that are in the same Layer 2 network, if more than one access point has the same IP address, only one of them is discovered at a time. You must add the access point to the managed list, change its IP address, and run discovery again to discover the next access point with that IP address. • Make sure that DHCP option 43 (vendor-specific information) is enabled on an external DHCP server. (Specifying an internal DHCP server on the wireless controller automatically enables DHCP option 43 with the IP address of the wireless controller.) For more information, see Access Point Discovery Guidelines on page 120. Resolve Connection Problems When an access point is converted from standalone AP mode to managed AP mode, its static IP address is changed to an IP address that a DHCP server has issued, either a DHCP server in the network or a DHCP server that is configured on the wireless controller. This change occurs to ensure that each managed access point has a unique IP address. Troubleshooting 300

  • 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

Troubleshooting
300
ProSAFE Wireless Controller WC7600
When the date shown is January 1, 2000, the wireless controller has not yet successfully
reached a network time server. Verify that the wireless controller can reach the Internet. If
you have completed configuring the wireless controller, wait at least five
minutes and check
the date and time again.
Resolve Problems with Access Points
If you encounter access point discovery or connection problems, the information in this
section might help you to resolve these problems.
Resolve Discovery Problems
If the wireless controller does not discover any or all access points, check the configuration of
the wireless controller and access points.
For all access points, check the following:
Make sure that the wireless controller is connected to the LAN (see
Ethernet Port LEDs
Are Not Lit
on page
297).
Make sure that you have entered the correct IP range if the access points function in
different VLANs, are behind an IP subnet, or are already installed and working in
standalone mode (see
Access Point Discovery Guidelines
on page
120).
Make sure that the access points run at least their initial firmware release or a newer
version. For firmware requirements, see
NETGEAR ProSAFE Access Points
on page
16.
For local access points that are installed across a Layer 3 network, check the following:
Verify that access points that are already installed and working in standalone mode have
SSH and SNMP enabled (which is the default setting).
Make sure that UDP port number 7890 is unblocked in the firewall.
Except for access points in factory default state that are in the same Layer 2 network, if
more than one access point has the same IP address, only one of them is discovered at a
time. You must add the access point to the managed list, change its IP address, and run
discovery again to discover the next access point with that IP address.
Make sure that DHCP option 43 (vendor-specific information) is enabled on an external
DHCP server. (Specifying an internal DHCP server on the wireless controller
automatically enables DHCP option
43 with the IP address of the wireless controller.)
For more information, see
Access Point Discovery Guidelines
on page
120.
Resolve Connection Problems
When an access point is converted from standalone AP mode to managed AP mode, its
static IP address is changed to an IP address that a DHCP server has issued, either a DHCP
server in the network or a DHCP server that is configured on the wireless controller. This
change occurs to ensure that each managed access point has a unique IP address.