Long latency time settings 1

[davidchardonnet]

Hello,

I have a Citrix Version 6.00.912 and it works well. But we have set up a new site which is accessed by satellite link and it has a very long latency time and Citrix doesn't work on it.

Is there any particular setting to make?

Thank you

David

 

[Djones1212]

If you are running XML you need to set the XML service timeout on the server. We ran into this problem with a sever in Tokyo. We jacked up the XML timeout and it worked.

 

[lb63640]

We just tried to setup a Citrix user with a Direcway connection, and no joy. Terminal Services RDP client works fine, but we need the Citrix client to work.

Where do you go to make these changes?

 

[ascotta]

It is extremely unlikely that RDP will work any better than ICA.

What are the symptoms ?

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[lb63640]

No real info to report. After you get the splash screen and "negotiating connection" message, the load bar stops and the user reports a message "unable to connect to Citrix server." (May not be verbatim, but you know how those user reported messages can be!)

 

[ascotta]

Have you checked the eventviewer for erros like Licensing of TS?

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[lb63640]

That'll be the first place to look on Monday, although it wasn't an issue only a few days before when the box was using dialup for the connection...and it will connect happily with the RDP client.

The user also informs me that their PC has Windows XP for the OS.

I'll report back with my findings.

As always, thanks for the help!

 

[lb63640]

Ah, Scott...you always have the answer, don't you? I've got some pesky 1008 TS errors (TS licensing grace period has expired and the service has not registerd with a license server) that have cropped up during the same time period.

How do I correct this issue? The Citrix server is not the licensing server. I know that before I joined the company, they even purchased 15 or 20 additional licenses and installed them.

 

[ascotta]

You need to find your license server. Check that you have enough licenses. There is a key you can remove on the client. HKLM\Software\Microsoft\ something or other I will check in the morning.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[lb63640]

OK, I know which server is the license server. When I check the TS Licensing properties, here is the info I get:

ACTIVATION STATUS = activated.
Existing Windows 2000 License (built in) TOTAL & AVAILABLE = unlmited ISSUED = 2
Windows 2000 Server Terminal Services CAL token (per-device) TOTAL & AVAILABLE = 10 ISSUED = 0

I do know the trick about removing the key on the client registry to force a new license.

What do I need to do to my illustrious Citrix Server (which is in the same domain as the license server) to stop it from throwing out those 1008 TS Grace Period Expiration errors?

 

[ascotta]

Its not the citrix server kicking them out as such it is the lack of TS licenses. They have probably got corrupt keys, thats the one to go for.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[lb63640]

That seems like the most likely culprit.

Per the MS KB articles I found on the subject, are these the correct steps to take?

1. Remove the X509 Certificate Registry Keys from the Citrix server box
2. Reboot the Citrix server
3. Reactivate the Terminal Services Licensing Server

Should I also delete the MSLicensing key from the client registry before I try to connect again?

 

[ascotta]

Not sure about 1,2,3 but certainly on the client registry.

Re-booting citrix seems like a good idea anyway.

[blue] Oh you know, just doing what I do.[/blue]

Cheers
Scott

 

[lb63640]

HERE IS THE SOLUTION FOR THE CITRIX/DIRECWAY PROBLEM:

Thanks to everyone who offered suggestions!

When I visited the user's home/office, latency was hideous--but expected. Pings were something like 800ms to 1130 ms!

Are you ready for the big fix? In the ICA custom connection properties, under the OPTIONS tab, SESSION RELIABILITY was enabled, so I disabled it. Following that tiny change, the PN client hopped right on the server and joy was found again!