StayLinked clients are designed to return various messages. Each message represents a specific set of issues. This means that the first step in troubleshooting will be to confirm the message presented by the client at the time of the issue.
The following are the most common messages and the steps you might take to resolve the issue:
Server Code esp0003: This message is returned when the device type and emulation do not have a keyboard defined on your server. Adding a keyboard map can be done using the StayLinked Administrator console and is explained in detail in the Administrator User’s Guide.
Upgrading a client version may result in improved recognition of the device model, resulting in a new device type. The server requires a keyboard installed for each unique device type and emulation group.
Part of the device type may be returned by the device operating system. In some cases, updates or changes to the device may change this response and require the installation of a new keyboard map to match the new device type.
Server Code esp0004: These messages are returned when the connection cannot be created because of StayLinked licensing issues. The StayLinked Administrator can be used to review the current license keys, the StayLinked server process’ serial number, and the current number of seats in use. In many cases, terminating old sessions can free up seats for new devices. More information on automating the cleanup of sessions can be found in the user experience guide.
Other esp00XX Error Codes: These messages are described in detail in the Administrator User’s Guide troubleshooting section. If the device returns the same message multiple times, please review the Administrator User’s Guide for troubleshooting tips.
Out-of-range: Indicates that the device’s radio is reporting that it is not associated with an access point. During normal operation, the StayLinked client will request the association status of the device radio. If the operating system reports that it is not associated, it will display the ‘Out of Range’ message to the user. Common causes of "out-of-range" conditions:
- Device is physically moved outside the radio coverage area supported by the radio hardware.
- Communication path to access point is obstructed.
- Antenna on the device is bad.
- Unsupported Radio hardware or firmware.
When an "out-of-range" state is detected the device will display an "!" character in the top right corner of the screen. The "!" will alternate between normal and inverse video for a short period as the device monitors the out-of-range state. If the device detects that it is back in radio coverage it will return to the session screen.
The first step is to review the device radio configuration and make sure it is able to reach the StayLinked server. If the device can ping the StayLinked server, adding a line to the device file staylink.ini always_in_range=1 will force the client to ignore association status.
Linking: Indicates that the client and server are not exchanging packets in a timely manner. Diagnosing interruptions in network are best completed with Ping and other network tools.
When a "Linking" state is detected, the device will display an " * " character in the top right corner of the screen. The " * " will alternate between normal and inverse video for a short period as the device monitors the link state. If the device detects that the link is restored, it will return to the session screen.
More information on troubleshooting steps can be found in the client-server communications guide.
Host Timeout: indicates that the connection between the client and StayLinked server has failed. Occasional host timeout messages are not uncommon in a wireless environment. Continued host timeout messages indicate network difficulties and should be resolved using typical network diagnostics. More information on the StayLinked handshake can be found in the Host Timeout technical reference guide.
Telnet Timeout: indicates that the telnet host is not responding or has denied the request for a telnet session. The first step will be to confirm that your StayLinked server is properly configured with a valid telnet host entry and that your device falls in to a device group that uses your desired host entry.
WSID Timeout: It can also be important to make sure the telnet server is enabled on your telnet host. For the iSeries, the virtual device name may not be available or cannot be created. Some versions of the StayLinked server may return a Telnet Timeout that may also indicate a required subsystem or QAUTOCFG is disabled. Review of the iSeries configuration, virtual device names and subsystems may be required.
Share the post "Client Troubleshooting"