Common Configuration Problems - Revision history

Toddgarmon: /* Graphical ACP Logo is shown, but boot process stops */

2023-05-01T20:51:43Z

Graphical ACP Logo is shown, but boot process stops

← Older revision		Revision as of 20:51, 1 May 2023
Line 78:		Line 78:
	*Switch the mouse and the keyboard if plugged into a PS/2 splitter.		*Switch the mouse and the keyboard if plugged into a PS/2 splitter.

	==Graphical ~~ACP~~ Logo is shown, but boot process stops==		==Graphical ThinManager Logo is shown, but boot process stops==
	Does not attempt to connect to the terminal server		Does not attempt to connect to the terminal server
	*Check Terminal Configuration Wizard to make sure a terminal server is specified		*Check Terminal Configuration Wizard to make sure a terminal server is specified

Toddgarmon: /* Booting - ACP Network Boot Loader */

2023-05-01T20:51:03Z

Booting - ACP Network Boot Loader

← Older revision		Revision as of 20:51, 1 May 2023
Line 7:		Line 7:
	No Video		No Video
	*Check video cable, monitor power cable and outlets.		*Check video cable, monitor power cable and outlets.
	==Booting - ~~ACP~~ Network Boot Loader==		==Booting - Network Boot Loader==
	Cannot get IP address using DHCP		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 ThinManager Ready thin client set to DHCP? They are set to DHCP by default, but can be changed.

Pburns at 15:53, 20 December 2019

2019-12-20T15:53:48Z

← Older revision		Revision as of 15:53, 20 December 2019
Line 18:		Line 18:
	*PXE-E32: TFTP open timeout		*PXE-E32: TFTP open timeout
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Check that acpboot.bin is located in the [[ThinManager ~~installation]~~] directory (default of %PROGRAMFILES%\~~Automation Control Products~~\ThinManager)		**Check that acpboot.bin is located in the [https://kb.thinmanager.com/index.php/ThinManager_Installation ThinManager Installation] directory (default of %PROGRAMFILES%\Rockwell Software\ThinManager)
	**If using a standard DCHP server with boot options		**If using a standard DCHP server with boot options
	***Verify option 67 is set to acpboot.bin in the DHCP server scope		***Verify option 67 is set to acpboot.bin in the DHCP server scope

Randycannady at 18:11, 31 May 2017

2017-05-31T18:11:07Z

← Older revision		Revision as of 18:11, 31 May 2017
Line 34:		Line 34:
	*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.		*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.
	**Verify that the standard DHCP server is functioning correctly		**Verify that the standard DHCP server is functioning correctly
	**~~Configure~~ the ThinManager PXE Server to ~~not use a standard~~ DHCP ~~server~~.		**If you do not have a standard DHCP Server, configure the ThinManager PXE Server to "Not using Standard DHCP Server".
	*PXE-E53: No boot filename received.		*PXE-E53: No boot filename received.
	**Using a relay agent: verify that the relay agent is configured properly		**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		**Using a standard DHCP server with boot options: verify that option 67 in the DHCP Server is set to acpboot.bin
	*PXE-E55: ProxyDHCP service did not reply to request on port 4011		*PXE-E55: ProxyDHCP service did not reply to request on port 4011
	**Install the latest service pack for your version of ThinManager		**Install the latest service pack for your version of ThinManager

Randycannady at 17:56, 31 May 2017

2017-05-31T17:56:52Z

← Older revision		Revision as of 17:56, 31 May 2017
Line 19:		Line 19:
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
	*If using a standard DCHP server with boot options		**If using a standard DCHP server with boot options
	**Verify option 67 is set to acpboot.bin in the DHCP server scope		***Verify option 67 is set to acpboot.bin in the DHCP server scope
	*PXE-E51: No DHCP or proxyDHCP offers were received		*PXE-E51: No DHCP or proxyDHCP offers were received
	**Make sure the client has a connection to the network with where the DHCP server resides		**Make sure the client has a connection to the network with where the DHCP server resides
Line 32:		Line 32:
	***Check that there is not a firewall preventing the DHCP requests from reaching the ThinManager servers		***Check that there is not a firewall preventing the DHCP requests from reaching the ThinManager servers
	***If the ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured		***If the ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured

	*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.		*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.
	**Verify that the standard DHCP server is functioning correctly		**Verify that the standard DHCP server is functioning correctly

Randycannady at 17:55, 31 May 2017

2017-05-31T17:55:12Z

← Older revision		Revision as of 17:55, 31 May 2017
Line 19:		Line 19:
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
	If using a standard DCHP server with boot options		*If using a standard DCHP server with boot options
	**Verify option 67 is set to acpboot.bin in the DHCP server scope		**Verify option 67 is set to acpboot.bin in the DHCP server scope
	*PXE-E51: No DHCP or proxyDHCP offers were received		*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		**Make sure the client has a connection to the network with where the DHCP server resides
			**If "Using Standard DHCP server with boot options":
			**Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server
			**If the DHCP server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
			**If "Using Standard DHCP server":
			***Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server or the ThinManager servers
			***If the DHCP server or ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
			**If "Not using a Standard DHCP server":
			***Check that there is not a firewall preventing the DHCP requests from reaching the ThinManager servers
			***If the ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured

	*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.		*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.
	**Verify that the standard DHCP server is functioning correctly		**Verify that the standard DHCP server is functioning correctly

Randycannady at 17:49, 31 May 2017

2017-05-31T17:49:17Z

← Older revision		Revision as of 17:49, 31 May 2017
Line 19:		Line 19:
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
	**If using a standard DCHP server with boot options		If using a standard DCHP server with boot options
	***Verify option 67 is set to acpboot.bin in the DHCP server scope		**Verify option 67 is set to acpboot.bin in the DHCP server scope
	*PXE-E51: No DHCP or proxyDHCP offers were received		*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		**Not using a standard DHCP server: check that there is not a firewall preventing the client to connect

Randycannady at 17:47, 31 May 2017

2017-05-31T17:47:30Z

← Older revision		Revision as of 17:47, 31 May 2017
Line 19:		Line 19:
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
	**~~Using~~ a standard DCHP server with boot options		**If using a standard DCHP server with boot options
	***Verify option 67 is set to acpboot.bin in the DHCP server scope		***Verify option 67 is set to acpboot.bin in the DHCP server scope
	*PXE-E51: No DHCP or proxyDHCP offers were received		*PXE-E51: No DHCP or proxyDHCP offers were received

Randycannady at 17:45, 31 May 2017

2017-05-31T17:45:47Z

← Older revision		Revision as of 17:45, 31 May 2017
Line 17:		Line 17:
	A Non-ThinManager Ready (PXE) Client Will Not Boot.		A Non-ThinManager Ready (PXE) Client Will Not Boot.
	*PXE-E32: TFTP open timeout		*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 that there is not a firewall preventing the client from downloading the boot file
	**Verify option 67 is set to acpboot.bin in the DHCP server scope
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)
			**Using a standard DCHP server with boot options
			***Verify option 67 is set to acpboot.bin in the DHCP server scope
	*PXE-E51: No DHCP or proxyDHCP offers were received		*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		**Not using a standard DHCP server: check that there is not a firewall preventing the client to connect

Randycannady at 17:44, 31 May 2017

2017-05-31T17:44:37Z

← Older revision		Revision as of 17:44, 31 May 2017
Line 19:		Line 19:
	**Using a standard DCHP server with boot options		**Using a standard DCHP server with boot options
	**Verify that there is not a firewall preventing the client from downloading the boot file		**Verify that there is not a firewall preventing the client from downloading the boot file
	**Verify option 67 is set to acpboot.bin		**Verify option 67 is set to acpboot.bin in the DHCP server scope
	**Check that acpboot.bin is located in the [[ThinManager installation]] directory (default of %PROGRAMFILES%\Automation Control Products\ThinManager)		**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		*PXE-E51: No DHCP or proxyDHCP offers were received