Common Configuration Problems

Below is a list of common configuration problems, ordered from thin client power on to Terminal Server Login.

Powering on the Thin Client

No Power

• Check power cable, power supply and outlets.

No Video

• Check video cable, monitor power cable and outlets.

Booting - ACP Network Boot Loader

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?

Cannot get IP address using Static IP menu

• Certain models like PXE boot ThinManager Compatible thin clients 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

A Non-ThinManager Ready (PXE) Client Will Not Boot.

• PXE-E32: TFTP open timeout
  • Using a standard DCHP server with boot options
  • Verify that there is not a firewall preventing the client from downloading the boot file
  • Verify option 67 is set to acpboot.bin
  • Check that acpboot.bin is located in the ThinManager installation directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
• PXE-E51: No DHCP or proxyDHCP offers were received
  • Not using a standard DHCP server: check that there is not a firewall preventing the client to connect
  • Make sure the client has a connection to the network with where the DHCP server resides
• PXE-E52: proxyDHCP offers were received. No DHCP offers were received.
  • Verify that the standard DHCP server is functioning correctly
  • Configure the ThinManager PXE Server to not use a standard DHCP server.
• PXE-E53: No boot filename received.
  • Using a relay agent: verify that the relay agent is configured properly
  • Using a standard DHCP server with boot options: verify that option 67 is set to acpboot.bin
• PXE-E55: ProxyDHCP service did not reply to request on port 4011
  • Install the latest service pack for your version of ThinManager
• PXE-E61: Media test failure, check cable
  • Make sure the client has a physical connection to the network

Cannot Load Firmware

Is Thin Client connecting to the ThinManager Server?

• 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
• Using Static IP
  • Has the ThinManager Server IP Address been entered in the IP Configuration Menu?
  • Check router address, IP Addresses, and Subnet Mask

Is the network blocked?

• ThinManager Ready thin client that communicate through routers, gateways, or firewalls may need some ports opened to allow data flow through these devices. See the Ports Page for a complete list of ports utilitized by ACP Products.

Loads firmware intermittently/slowly

• Check for IP conflicts
• Check cable connections
• Make sure ThinManager Server CPU usage is below 100%

Thin Client Loads Firmware but fails to load configuration

"Please Define on Server"

• Enter ThinManager and define the terminal.

"License Not Available"

• Check your license usage in ThinManager. You are out of an ACP-supplied License.
• The Installation ID may come from the motherboard serial number, the MAC address on the network cards, or the GUID from the operation system. Don't change or disable the network cards after licensing to prevent changing the Installation ID, which can affect the validity of the license.

"This Terminal Disabled"

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

"Network Error - Check Network Connections"

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

Was Disabled, but did not go on when re-enabled.

• Reboot the thin client.

Is WinTMC Loaded on ThinManager Server?

• 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. WinTMC is for PCs, not servers. Uninstall the WinTMC client if it is present.

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.

Graphical ACP Logo is shown, but boot process stops

Does not attempt to connect to the terminal server

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

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 Published Application, you may need to specify the ICA browser.

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

• Check the event viewer on the terminal server. 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.

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