Citrix Client Connections-some work some don't

[cpusolutions]

We've set up a Citrix server and succesfully published an app. Some remote clients can connect and some cannot. All clients are using IE6. Some clients at the same remote location can connect, but the guy sitting next to him can't. OS does not seem to be related. Does not seem to be a licensing issue. Does not seem to be a firewall issue (clients behind same firewall get different results). Those who cannot connect get the login screen and the program icon, but when they click the icon, it says it's initializing, then just disapears. Tried connecting a brand new pc to the app and could not connect, so it couldn't have anything to do with other installed software. Clients that can't connect have downloaded the ICA client dierectly from Citrix's web site, no help.

Any Ideas- Anyone?

Any help would be greatly appreciated.

Thanks.

 

[MrMister]

Try to empty the cash.

 

[erickgrau]

I had a similar problem. Try this:

by editing the terminal server’s registry, you can bypass the license server discovery process and direct the license requests to a specific server. You need to add the value (type REG_SZ) DefaultLicenseServer to the following key:
HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters

For the value, specify the name (must be resolvable by DNS or WINS) of your selected license server. As with the enterprise mode model, this setting is suitable for multiple domains, and outside Active Directory, it allows a terminal server to contact a license server on the other side of a router.

A disadvantage of this method is that it will result in Event ID 1010 (TermService) being logged to the terminal server’s event log every six hours. You can ignore this; it simply informs you that normal licensing server discovery is not succeeding. More critical, however, is the fact that this method has no failover if it cannot locate the specified server. In that case, client connections will simply be refused. Unfortunately, you can't list a number of servers to try in sequence, and if the specified server can't be contacted, the terminal server doesn’t revert to standard license server discovery. I’m told this will be implemented in Windows .NET Server 2003.