|
If you would like to speak with one of our engineers, please Submit a Question or give us a call at the phone number here. In North America, To route your phone support request directly to a technical support engineer, call toll-free 1-888-382-1583 or 1-440-646-3434, select Option 3 (Technical Support), then select Option 5 (More Options). When prompted, enter the ThinManager Direct Dial Code 201. |
Difference between revisions of "Common Configuration Problems"
(→Booting - ACP Network Boot Loader) |
(→Cannot Load Firmware) |
||
| Line 34: | Line 34: | ||
==Cannot Load Firmware== | ==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== | ==Thin Client Loads Firmware but fails to load configuration== | ||
==Graphical ACP Logo is shown, but boot process stops== | ==Graphical ACP Logo is shown, but boot process stops== | ||
Revision as of 13:08, 24 October 2012
Below is a list of common configuration problems, ordered from thin client power on to Terminal Server Login.
Contents
- 1 Powering on the Thin Client
- 2 Booting - ACP Network Boot Loader
- 3 Cannot Load Firmware
- 4 Thin Client Loads Firmware but fails to load configuration
- 5 Graphical ACP Logo is shown, but boot process stops
- 6 Attempts to connect to terminal server, but dies
- 7 Connects to connect to terminal server, but cannot login
- 8 Login to Terminal Server prompts for password even though the username and password are filled in ThinManager
- 9 After the session is established, it will disconnect randomly
- 10 Mouse works but the application is unresponsive
- 11 Sound doesn't work
- 12 The touch screen doesn't work
- 13 The touch screen mouse doesn't match the touches
- 14 Changes to the configuration in ThinManager don't show up on the thin client
- 15 The configuration of the primary ThinManager Server and the secondary ThinManager Server are different
- 16 The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red
- 17 The client is showing the time of the terminal server in a different time zone and not the local time
- 18 When "Terminal Servers" is highlighted in the ThinManager tree, the Details pane doesn't show OK for the connections
- 19 The Users, Sessions, and Processes tabs don't show data for a terminal server
- 20 The Users and Sessions tabs show data for a terminal server, but the Processes tabs shows no data
- 21 When shadowing a client the mouse doesn't work in the shadowed session
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%
