HP ProCurve 520wl Wireless Access Point - Manual (Page 78)

Symptoms and Solutions
5-4
client connection problems client connection problems client connection problems client connection problems
client software finds no connection client software finds no connection client software finds no connection client software finds no connection
Q
Make sure you have configured your client software with the proper Network Name(s).
Network Names are typically allocated and maintained by your network administrator.
client pc card does not work client pc card does not work client pc card does not work client pc card does not work
1. Make sure you are using the latest PC Card driver software.
2. Download and install the latest client software.
intermittent loss of connection intermittent loss of connection intermittent loss of connection intermittent loss of connection
1. Make sure you are within range of an active WL520 device.
2. You can check the signal strength using the signal strength gauge on your
hp WL520 AP client software.
client does not receive an ip address - cannot connect to internet client does not receive an ip address - cannot connect to internet client does not receive an ip address - cannot connect to internet client does not receive an ip address - cannot connect to internet
1. If the WL520 device is configured as a DHCP server, open the Web-browser Interface and select the Configure Configure Configure Configure button and
then the Network Network Network Network tab to make sure the proper DHCP settings are being used.
2. If you are not using the DHCP feature on the WL520 unit, then make sure that your local DHCP server is operating on the
same subnet as your WL520 device.
3. From the client computer, use the “ping” network command to test the connection with the WL520 unit. If the WL520
device responds, but you still cannot connect to the Internet, there may be a physical network configuration problem
(contact your network support staff).
vlan operation issues vlan operation issues vlan operation issues vlan operation issues
verifying proper operation of the vlan feature verifying proper operation of the vlan feature verifying proper operation of the vlan feature verifying proper operation of the vlan feature
The correct VLAN configuration can be verified by “pinging” both wired and wireless hosts from both sides of the WL520
device and the network switch. Traffic can be “sniffed” on both the wired (Ethernet) and wireless (WDS) backbones (if
configured). Bridge frames generated by wireless clients and viewed on one of the backbones should contain IEEE 802.1Q
compliant VLAN headers or tags. The VLAN ID in the headers should correspond to one of the VLAN User IDs configured for
the WL520 device.
vlan workgroups vlan workgroups vlan workgroups vlan workgroups
The correct VLAN assignment can be verified by pinging the WL520 to ensure connectivity, by pinging the switch to ensure
VLAN properties, and by pinging hosts past the switch to confirm the switch is functional. Ultimately, traffic can be “sniffed” on
the Ethernet or WDS interfaces (if configured) using third-party packages. Most problems can be avoided by ensuring that
802.1Q compliant VLAN tags containing the proper VLAN ID have been inserted in the bridged frames. The VLAN ID in the
header should correspond to the user’s assigned network name.
what if network traffic is being directed to a nonexistent host? what if network traffic is being directed to a nonexistent host? what if network traffic is being directed to a nonexistent host? what if network traffic is being directed to a nonexistent host?
– All sessions are disconnected, traffic is lost, and a manual override is necessary
– Workaround: you can configure the switch to mimic the nonexistent host
i have just configured the management id and now i can't manage the ap? i have just configured the management id and now i can't manage the ap? i have just configured the management id and now i can't manage the ap? i have just configured the management id and now i can't manage the ap?
– Check to ensure your password is correct. If your password is incorrect or all inbound packets do NOT have the correct
tag, then a manual override is necessary.
CAUTION: !
The manual override process disconnects all users and resets all values to factory defaults.