ThinManager Troubleshooting Guide

This is a list of common configuration errors and a guide for fixing them.

Note: When any problem arises, check Downloads at http://www.thinmanager.com/support/downloads.shtml for the latest Service Packs and firmware. The problem you are experiencing may have already been fixed and released in a later version of firmware and using the latest version will cure the current problem. Try applying the latest firmware, and then reboot the thin client to see if the problem still exists. The current version (v.3.02.X) is backwards compatible to earlier versions of ThinManager (2.3.1, 2.4, 2.5, 2.6, 3.0, etc.)

Section 1 - From Power on to Terminal Server Login

1) Powering on the Thin Client

A) No Power

  • Check power cable, power supply, and power outlets.

B) No Video

  • Check video cable and monitor.

    Warning: Never go into the thin client BIOS and change the Integrated Peripherals>Display Status from CRT to LCD. This changes the video output of the motherboard from the VGA port to a socket on the motherboard used for integrated LCD panels. Changing this from CRT will prevent any video from being displayed on a monitor.

2) Booting - ACP Network Boot Loader

A) Cannot get IP address using DHCP

  • Is the ThinManager Ready thin client set to DHCP? They are set to DHCP by default, but can be changed.
  • Is the Thin Client on the same side of the router as the DHCP server?
  • Does the DHCP server have addresses to give out?

B) Cannot get IP address using Static IP menu

  • Certain models (ThinAdapters and older DC-40-100s with black PS/2 ports) cannot use static IP.
  • Static IP hasn't been set. Use the spacebar when the "Select any Key to Configure IP Settings" is displayed and set the client IP address

3) Cannot Load Firmware

A) Is Thin Client connecting to ThinManager Server?

i) Using DHCP

  • Has Option 066 been set to the ThinManager Server IP Address?
  • Is there a link light on the network port?
  • Check router address, IP Addresses, and Subnet Mask

ii) Using Static IP

  • Has the ThinManager Server IP Address been entered in the IP Configuration Menu?

B) Is the network blocked?

ACP Enabled thin clients that communicate through routers, gateways, or firewalls may need some ports opened to allow data flow through these devices. If the thin client communicates through one of these and it is having trouble, check to see if these ports are allowed.

The required ports are:

  • UDP/4900 - TFTP - Used for the TFTP download of the firmware.
  • TCP/2031 - Configuration - Used to pass the configuration from the ThinManager Server to the thin client.
  • TCP/1494 - Citrix - Used by the ICA protocol (if using ICA instead of RDP).
  • TCP/3389 - RDP - Used by the RDP protocol (if using RDP in v2.4.1 or later).
  • TCP/5900 - Shadowing - Used to shadow terminals.
  • Ping and DHCP - These need configured as needed.

C) Loads firmware intermittently/slowly

  • Check for IP conflicts
  • Check cable connections
  • Make sure ThinManager Server CPU usage is below 100%
  • Check the IGMP settings on the routers. If the IGMP is blocked, the Multicast of firmware will be interrupted. Unselecting Multicast in the ThinManager Server Configuration wizard will allow firmware downloads if the IGMP is blocked.

4) Thin Client Loads Firmware but shows blue message screen

A) "Please Define on Server"

  • Enter ThinManager and define the terminal.

B) "License Not Available"

  • Check your license usage in ThinManager. You are out of an ACP-supplied License

C) "This Terminal Disabled"

  • A ThinManager administrator has disabled this terminal. Re-enable it.

D) "Network Error - Check Network Connections"

  • Check the network cable. Link light, and network.

E) Was Disabled, but did not go on when Re-enabled.

  • Reboot.

F) Terminal Selection menu is shown, but keyboard does not work

  • Check keyboard and reboot
  • Use PS/2 splitter if the unit has only one PS/2 port
  • Switch the mouse and the keyboard if plugged into a PS/2 splitter.

5) Graphical ACP Logo is shown, but boot process stops

A) Does not attempt to connect to the terminal server

  • Check Terminal Configuration Wizard to make sure a terminal server is specified

B) Cannot load configuration

  • Make sure that the WinTMC client is not installed on the ThinManager Server. The WinTMC client will try to open the 2031 port that ThinManager needs to communicate with thin clients, causing a port conflict. Unistall the WinTMC client if it is installed.

C) Cannot Connect to Server xxx (0.0.0.0)

  • The terminal server doesn't have an IP address configured in the Terminal Server Configuration Wizard.
  • If using DNS, check the terminal server's registration.
  • If you are using a Citrix MetaFrame Published Application, you may need to specify the ICA browser.

D) Cannot Connect to Server xxx (w.x.y.z)

  • Check the event viewer. If it says "Could not issue client license", you need a Microsoft Terminal Server Client Access License (MS TS CAL) and/or a Microsoft Terminal Server Licensing server.
  • Check the Subnet Mask in the ACP Boot Loader on the thin client. If it is set to 255.255.255.255 instead of 255.255.255.0, it will fail to connect to the terminal server.
    Reboot the thin client and use the spacebar when the "Select any Key to Configure IP Settings" is displayed. Change the subnet mask in the ACP Boot Loader menu.

E) Error 50 - Disconnected

  • Check the event viewer. If it says "Could not issue client license", you need a MS TS Cal / MS TS Licensing server.

6) Attempts to connect to terminal server, but dies

  • Some servers (Dell and its Dellwall.bmp, for example) load a complex bitmapped background that can interfere with loading. Find the offending wallpaper file on the console session and renamed it so that it doesn't load at login

7) Connects to connect to terminal server, but cannot login

  • Is the user a valid user? Is the password correct?
  • Does the user have permission to connect through Terminal Services (user properties in the User Manager)
  • If logging in to a Windows 2003 terminal server, is the user a member of the Administrators group or Remote Desktop Users group?
  • Check the event viewer. If it says "Could not issue client license", you need a MicroSoft TS Cal and or a MicroSoft TS Licensing server.

8) Login to Terminal Server prompts for password even though the username and password are filled in ThinManager

  • The password may be entered wrong in ThinManager.
  • Windows 2000 Server is set to always prompt for password at login for RDP users. Select Programs>Administrative Tools>Terminal Services Configuration and double click on RDP-tcp Properties in the right-hand window. Uncheck the Always Prompt for Password checkbox on the Login Settings tab.

Top

Section 2 - Thin Client is Booted, Connected, and Running a Session on the Terminal Server

9) Disconnects randomly

  • Make sure each user is logging on with a unique user name. Windows 2003 will only allow one session per name by default.
  • Check the physical network connection.
  • Check for a different computer (e.g. a laptop) with the same IP address.
  • Slow down the Monitoring Interval on the Monitoring Connection page of the Terminal Configuration Wizard by increasing the timeout and retry values.

10) The session in Windows 2003 requires frequent logins

  • Turn off the Windows screen saver. User accounts in Windows 2003 use a secure screen saver by default that requires this frequent login.

11) Mouse works but the application is unresponsive

  • Application on terminal server is locked up - kill the application and let the thin client reconnect to terminal server and restart the application

12) Sound doesn't work

  • Make sure that you are using a Windows 2003 terminal server
  • Make sure that Audio Mapping is allowed on the Client Settings of the RDP-tcp Properties in the Terminal Server Configuration Console.
  • Make sure that you are using a ThinManager Ready thin client that has sound capability
  • Use the Sound Module for that specific thin client
  • Connect a powered speaker to the "Line Out" plug. Line Out isn't amplified so it requires a powered speaker.
  • Properly working sound will play a drip sound at boot.

13) The touch screen doesn't work

  • Make sure you are using the right Touch Screen Module for the touch screen controller.
  • Make sure that the serial cable is plugged into the correct serial port
  • Make sure that the Touch Screen Module is using the correct baud rate.

14) The touch screen mouse doesn't match the touches.

  • Calibrate the touch screen by highlighting the unit in the ThinManager tree and select Tools > Calibrate Touch Screen.

15) Changes to the configuration in ThinManager don't show up on the thin client.

  • Reboot the thin client. Changes are only set to a thin client at bootup.

16) The configuration of the primary ThinManager Server and the secondary ThinManager Server are different.

  • Synchronize the configurations by selecting ThinManagerServer >Synchronize in the ThinManager menu bar.

17) The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red.

  • Add both ThinManager Servers to the ThinManager Server Monitor List in the Terminal Configuration Wizard (then reboot the terminals and synchronize the ThinManagers as in Number 15) and Number 16).

18) The client is showing the time of the terminal server in a different time zone and not the local time.

  • Use the Time Zone Redirection Module on the client with the local time zone selected.
  • Make sure that the security policy of the terminal server or domain allows it. Look at Computer Configuration > Administrative Templates> Windows Components > Terminal Services >Client/Server data redirection >Allow Time Zone Redirection and set it to Enabled

19) When "Terminal Servers" is highlighted in the ThinManager tree, the Details pane doesn't show OK for the connections.

A) No login information supplied

  • Run the Terminal Server List Wizard and add an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.

B) User specified does not have permission to connect

  • This indicates that the Terminal Server had an invalid username and password added on the Terminal Server Name page of the Terminal Server List Wizard. Run the Terminal Server List Wizard and change to an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
  • Use the domain in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
  • If not in a domain, try using the terminal server name in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.

C) WTSAPI32.dll connection failed

  • This occurs when the terminal server is off or unreachable. Try pinging the terminal server.
20) The Users, Sessions, and Processes tabs don't show data for a terminal server

A) No login information supplied

  • Run the Terminal Server List Wizard and add an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.

B) User specified does not have permission to connect

  • This indicates that the Terminal Server had an invalid username and password added on the Terminal Server Name page of the Terminal Server List Wizard. Run the Terminal Server List Wizard and change to an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
  • Use the domain in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
  • If not in a domain, try using the terminal server name in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.

21) The Users and Sessions tabs show data for a terminal server, but the Processes tabs shows no data.

  • Shorten the name of the terminal.
    Microsoft truncates the terminal names to 15 characters. The Process information won't display for terminals with a name longer than 15 characters.

22) When shadowing a client the mouse doesn't work in the shadowed session.

  • The user must be logged into the shadowing computer as an administrator or as a ThinManager Administrator to use interactive shadowing.
  • The interactive shadow must be checked in RemoteView on the ThinManager menu.
  • A terminal using the Share Keyboard and Mouse module will only be interactive if the mouse is active in that session.

Top

(Updated 11/14/2008)