Chapter 4— Troubleshooting and Maintaining the Terminal
nugget
39
AGaramond
74
Trakker Antares 242X Handheld Terminal User’s Manual
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.
One of these error codes appears on the
Error Logger screen:
0x50A
or
0x509
The time and date on your terminal does not fall within the range of
valid dates indicated on the server certificate. Modify the time and date
so that it falls within the range of valid dates. For help, see “Time and
Date” in Chapter 6 of the 2400 Family system manual.
If this is a recurring problem, you may want to update the
BASEDATE.TXT file on your terminal.
1
Make sure that your PC is configured with the correct date and time
and that you have BASEDATE.TXT and LOADER.EXE on your
PC. These files are available as part of the firmware upgrade that can
be downloaded at no charge from the Intermec Web site at
www.intermec.com.
2
Follow Steps 1 through 5 of the procedure To transfer applications
and files to the terminal using LOADER.EXE in Chapter 3,
“Developing and Using Applications,” in the 2400 Family system
manual.
3
On your PC, type:
LOADER
pathname
\BASEDATE.TXT
where
pathname
is the path to the location of BASEDATE.TXT on
your PC.
The Loader screen appears. BASEDATE.TXT is set to the current
time and date on your PC and is transferred to your terminal.
Note:
Do not cold boot the terminal. Cold booting the terminal resets
the time and date.
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:
0x377
Make sure that:
•
the User Name and Password parameters on your terminal match
the user name and password on your Odyssey server. You may need
to re-enter the password on both your terminal and Odyssey server.
•
on your Odyssey server, the user and group are allowed and the
group policy is allowed to log in to the Odyssey server. For help, see
the documentation that shipped with your Odyssey server software.
•
the IP address and secret key for your MobileLAN access point must
match the IP address and secret key on your Odyssey server. You
may need to re-enter the IP address and secret key on both your
MobileLAN access point and Odyssey server.
•
your Odyssey server is active and that it can communicate with your
MobileLAN access point. You can use the PING command to
determine communications.
•
the Odyssey server software is running on the server PC.
•
the UDP port (standard RADIUS port, 1812) on your Odyssey
server is active. For help, see the documentation that shipped with
your Odyssey server software.
Summary of Contents for Trakker Antares 2400
Page 2: ...Trakker Antares 242X Handheld Terminal User s Manual ...
Page 3: ...Trakker Antares 242X Handheld Terminal User s Manual ...
Page 10: ...Contents viii Trakker Antares 242X Handheld Terminal User s Manual ...
Page 113: ...Trakker Antares 242X Handheld Terminal User s Manual 99 Index I ...
Page 121: ......
Page 123: ...Trakker Antares Firmware Version 8 02 Addendum ...
Page 126: ...Contents iv Trakker Antares Firmware Version 8 02 Addendum ...