What are the reasons a Thin Client will lose a connection with its terminal server?
The most common reasons that a Thin Client disconnects from the server are (1) a non-responsive terminal server, (2) a duplicate IP address, or (3) a saturated network. All ThinManager Ready Thin Clients have a program that constantly monitors the Windows Terminal Server. Configuration for this program is found on the Monitoring page of the Terminal (or Group) Configuration Wizard. One of the main functions of this program is to check for responses from the terminal server. If at any time the server doesn’t respond, the Thin Client will break the socket connection to the server and try to reconnect. If it determines that the server is unavailable, the client will move on and try to connect to the next terminal server in its configuration list. Under normal conditions, the only way an ACP thin client will lose a connection to a terminal server is that the terminal server doesn’t respond to the client, causing the client to drop the connection. One obvious reason the server may not respo
