ICA Connections Hangs or Stops at 'Connection Established, Negotiating Capabilities'
ICA connections hang or stop at "Connection established. Negotiating capabilities” specific to client workstation or domain user . Also connecting to a specific server always hang at “Connection Established, Negotiating Capabilities”.
My machine + his\her credentials = success
Another machine + his\her credentials = success
His\Her home machine + his\her credentials = failure
His\Her home machine + test ID = failure
Usually this is caused by an inaccessible license server.
Server results in not getting a correct license, probably the license server detects that several servers are using the same license and blocks it, especially if servers are cloned.
Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Back up the registry before you edit it.
1. On client workstations with this issue, change the permissions on the registry key HKLM\SOFTWARE\Microsoft\MSLicensing. Give the Users Group Full Control or specific domain user account.
If you delete the key, Terminal Services recreates it when it acquires a license. However, the permissions on this key are set to read-only by default. Only administrators have full control rights. This means that only an administrator can request a Terminal Services license for this server. Once it is acquired, every user can use it.
2. Delete (rename or export key to be safe) the HKLM\Software\Microsoft\MSLicensing\HardwareID and HKLM\Software\Microsoft\MSLicensing\Store keys
For Windows 2000 Professional systems: delete the License000x key to resolve the issue.
On each of your Citrix Presentation servers open the registry editor and navigate to
"HKEY Local Machine/System/Current ControlSet/Services/TermService/Parameters".
Delete the following keys (after making a backup):
X509 Certificate ID
Reboot your server and verify that the issue is gone.