Citrix Not Accepting

[BlckJckFrnk]

Help!!!!
Have a Citrix server running MFXP and WIN2K. I had to install a new NIC card on a COMPAQ ML350 SERVER and used all the same IP address's. I can logon as a client to NFUSE, but when I go to us an application, I get the following "Citrix Server is not accepting connections"?????

Thanks for any help.....

 

[victorv]

hi,

1) is the old nic still on the machine? is it configured
( in another ip address )

2) try to connect to to server by a normal ICA client
( as administrator and as user ) and see the result.
Avoid use NFuse during this problem determination phase.

3) In Citrix Connection Configuration (the hammer in the
toolbar), in the ICA-tcp/Edit, is the new adapter
excluded from access to LAN ?

4) What appens if connecting server via RDP, instead ICA ?

5) Are your License still valid after change/add of nic ?


bye

 

[chjinmind]

Hi!

I just had the same issue but it occured when we added several ip-adresses to the NIC och the MetaFrame server.

Some things to check and do...

1. Download Tcpview from sysinternals.com and extract on the failing server.
2. Execute tcpview.exe on the failing server and search for the process called termsrv.exe.
Most probably the PID for the thread/process is anything else than 544 (in tcpview you can se it like termsrv.exe:544, leftmost column). This means that the ica port listener only listen to 1 specific NIC or ip-adress on the server.

Solution to let all NIC's and ipadresses be listeners:

Go to the Citrix Connection Configuration and set the Lan adapter for ICA protocol to use "All network adapters configured with this protocol".

Check in tcpview that the process has changed PID to 544 and shows like termsrv.exe:544 and local adress is 0.0.0.0:1494, state listen.

You might have to reboot...

If this does not solve the issue check further with the help of this CTX-document (from Citrix Knowledgebase). It did not solve the issue for me, the above mentioned actins did...

Check Registry for WDICA key

Symtoms

1. Unable to telnet to port 1494. Connecting to servername. Could not open a connection to host on port 1494: Connect failed.

2. NetStat -a does not show the server listening on port 1494.

3. A Microsoft RDP connection works.

4. Idle sessions are available and the ICA listener is created and enabled.

Reproducible Steps

1. Run regedt32.

2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDICA.

3. Save the key.

4. Delete the key.

5. Reboot the server.

6. Make a custom ICA connection to the server IP address.

Resolution

1. Run regedt32.

2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

3. Create a key named WDICA.

4. Manually add the following values:

ErrorControl: REG_DWORD : 0

Start: REG_DWORD : 0x3

Type: REG_DWORD : 0x1

5. Reboot the server.

6. During the reboot of the server in step 5, a subkey named Enum will be created with the following values.

0 : REG_SZ : Root\LEGACY_WDICA\0000

Count : REG_DWORD : 0x1

NextInstance : REG_DWORD : 0x1

7. Make a Custom ICA Connection to the servers IP address.

If the above steps do not resolve the issue, check for the existence of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WDICA and its subkeys. You may need to add permissions to this key in order to save and restore the key from a working server. When this key is manually deleted and the server is rebooted, the key should regenerate itself. If the key does not automatically regenerate itself, you can restore a copy of this key from a known good server or manually create the entries. When replacing this key with a copy of the key from another server it is necessary to navigate to the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WDICA\0000\Control

Delete the data of the following value located within the above referenced key and then reboot the server:

"DeviceReference"=dword:8188fd10

Upon reboot the data should repopulate.

NOTE: The cause for the disappearance or corruption of these registry keys is currently unknown.


Let us know if this solves your problem,
cheers,
chris