User's Manual

Chapter 4 — Troubleshooting and Maintaining the CK30
CK30 Handheld Computer User’s Manual 61
Problems While Configuring 802.1x Security (continued)
Problem Possible Solution
The terminal indicates that it is not
authenticated by emitting a high beep and
a low beep.
This error code appears on the Error
Logger screen:
0x513
The root Certificate Authority certificate on your terminal
cannot validate the server certificate.
• Make sure your Odyssey server is using a server
certificate that matches the root certificate loaded on
your terminal.
• Verify the root certificate in the CACERT.PEM file on
your terminal’s C drive. WHERE WILL THIS BE ON
THE CK30?
For help, see the documentation that shipped with your
Odyssey server software.
The terminal indicates that it is not
authenticated by emitting a high beep and
a low beep.
This error code appears on the Error
Logger screen:
0x542
Neither of the server certificate common names configured
on your terminal match the server certificate common
name in the active server certificate on your Odyssey
server.
• Delete both server certificate common names on your
terminal to see if you can authenticate without
checking the server certificate common name.
• Change one or both server certificate common names
on your terminal so that they match the server
certificate common names in the active server
certificate on your Odyssey server.
For help, see “Server Certificate Common Name” in
Chapter 6 of the CK30 Handheld Computer Configuration
Manual.
Problems With RF Connectivity
Problem Solution
You are having problems with your
802.11b RF network coverage.
Make sure that the Multiple Density Distribution
(MDD) command on your access point is not enabled.
When MDD is enabled, the access point distributes
values for these RF coverage parameters to your
terminal: AP Density and Medium Reservation.
Changes made by your access point are not reflected in
the terminal menu system.