Motorola WiNG 4.4 Reference Manual page 564

C - 6 WiNG 4.4 Switch System Reference Guide
C.1.3.1 Access Port Adopted, but MU is Not Being Associated
Access Port associated with an MU is not yet being adopted. The table below provides suggestions to troubleshoot this
issue.
Possible Problem
Unadopted Access Port
Incorrect ESSID applied
to the MU
Ethernet port
configuration issues
Incorrect security
settings
All else...
C.1.3.2 MUs Cannot Associate and/or Authenticate with Access Ports
MUs cannot associate and/or authenticate with Access Ports.
The table below provides suggestions to troubleshoot this issue.
Possible Problem
Preamble differences
Device key issues
MU is not in Adopt List
Keyguard not set on
client
Encryption Problems
Authentication Problems
Encryption or
Authentication Problems
Suggestions to Correct
Verify that the switch has adopted the Access Port with which the MU is
trying to associate.
Verify on the MU that the correct ESSID has been applied to the MU.
• Verify that the Ethernet port connected to the network and has a valid
configuration.
• If DHCP is used, verify that the Ethernet cable is connected to the same
NIC upon which DHCP services are enabled.
Verify that the correct security settings are applied to a WLAN in which
the MU is trying to associate.
Contact Motorola Solutions Support.
Suggestions to Correct
Verify that the preamble type matches between switch and MUs. Try a
different setting.
Verify in Syslog that there is not a high rate of decryption error messages.
This could indicate that a device key is incorrect.
Verify the device is not in the "do not adopt ACL".
Verify Keyguard is set on the client if the Security/WLAN Policy calls for
Keyguard.
If Encryption is being used, verify that the encryption settings on the MU
and the switch match.
If WEP Encryption is being used with non-Symbol or Motorola Solutions
MUs, ensure that the key being entered is in HEX format and not a
Passphrase.
If the switch is configured to use RADIUS authentication, check the
RADIUS log file for any failure information.
If you are using Authentication and/or Encryption on the switch, and the
previous troubleshooting steps have not fixed the problem, try temporarily
disabling Authentication and Encryption to see if that fixes the problem.