Problems While Configuring 802.1X Security - Intermec Trakker Antares 243X User Manual

Chapter 4— Troubleshooting and Maintaining the Terminal
Problems While Configuring the Terminal (continued)
Problem
On the 2435, you see this error message when
exiting the Configuration Menu:
Network configuration error.
Network is enabled. Terminal IP
address or Controller (Host) IP
address set to the same address.
Configuration was not updated.

Problems While Configuring 802.1x Security

Problems While Configuring 802.1x Security
Problem
You are configuring 802.1x TTLS security. The
"AUTHENTICATING" message does not
appear on the screen, and the Network Connect
status icon is not on.
You are configuring 802.1x TTLS security. The
"AUTHENTICATING" message appears on the
screen, but the terminal does not emit a low beep
and a high beep to indicate that it is
authenticated.
70
Possible Solution
The RF network is enabled and there is a problem with the
network configuration. You must change the terminal IP address,
the controller IP address (host IP address for a TCP/IP network),
or both. Choose Primary Network from the Communications
Menu.
The terminal IP address and the controller/host IP address are
both set to the same address. Set a valid IP address for the
terminal and Intermec Gateway or DCS 30X or host.
For help, see "Using RF Communications on the 2435" on page
54. If you cannot fix the addressing problem, check with your
network administrator to get the IP address assigned to the
terminal and the Intermec Gateway or DCS 30X or host.
If you have trouble configuring the terminal for 802.1x TTLS or LEAP
security, check these possible problems and solutions. For more error
numbers and messages, see "802.1x Security Error Numbers and
Messages" in Chapter 4 of the 2400 Family system manual.
This section references error numbers that are displayed on the Error
Logger screen in the TRAKKER Antares 2400 Menu System. To view the
Error Logger screen, from the Main Menu, choose Diagnostics Menu,
Software Diagnostics, and then Error Logger.
Possible Solution
The terminal may not be communicating with your MobileLAN
access point. Make sure that:
•
the network name on the terminal is the same as the network
name (SSID) of the access point that you are trying to
communicate with. The default network name is
"INTERMEC."
•
the Network Activate command is enabled on your terminal.
The 802.1x security network may not be active. Make sure that
the Odyssey™ server software is properly loaded and configured
on the server PC. For help, see the documentation that shipped
with your server software.
The terminal takes up to 60 seconds to authenticate; however,
this process may take longer if there is interference in RF
communications. You may need to wait for the authentication
process to finish.
You may be out of range of the MobileLAN access point that you
are trying to communicate with. Try moving closer to the
MobileLAN access point.
39
nugget
Trakker Antares 243X Handheld Terminal User's Manual