pcAnywhere Host, RDP, Terminal Server and Citrix don't work at the same time
|Article:TECH137703|||||Created: 2010-08-12|||||Updated: 2011-09-21|||||Article URL http://www.symantec.com/docs/TECH137703|
Attempts to establish an RDP or Terminal Server session to a computer which has the pcAnywhere host service running may not work as expected. Also, running and publishing a pcAnywhere host package as a Citrix application doesn't work.
When connecting to a computer in a Terminal Server session or Citrix server with a pcAnywhere host or starting a host in this environment may yield the following errors.
- "The host cannot run in a remote terminal services session. Please run the host locally at the server."
- "Could not start the Symantec pcAnywhere Host Service service on the local computer."
- "Error 1053: The service did not respond to the start or control request in a timely fashion."
- Communications error: Unable to attach to specified device.
pcAnywhere Host is not supported on a computer that has more than one active windows session. Windows NT/2000/2003/2008 Terminal Services and Citrix servers allow for more than one user to have an active session running on the same computer. The pcAnywhere Host service will then try to initialize in each active session, the Symantec pcAnywhere Host Service (awhost32) may crash, and it may be necessary to reboot the computer to regain pcAnywhere functionality.
The pcAnywhere Host service cannot be started or restarted while in a remote control session. The pcAnywhere Host service must be restarted locally on the computer when no remote sessions or remote control actions are being made to the computer.
pcAnywhere is not supported in an environment where other remote control services are running. To avoid undesirable behaviour, uninstall or disable other remote control services. Or, stop the Symantec pcAnywhere Host Service prior to using other remote control services.
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Article URL http://www.symantec.com/docs/TECH137703