Slow Or No Connection Via DSL & Satellite

[coastranger]

My server is quite simple. It's Windows 2000 running Metaframe XPs FR3. Life seems good now that the printers are behaving.

The ISP I'm using is TimeWarner's Roadrunner business class. I can connect to it quite well from other roadrunner accounts. However, one of my DSL accounts has trouble connecting via the ICA client (client versions 7 & 8). It works about 1 in 10 tries. If I ping the server, the response is 90 to 250 ms. If I connect just using the terminal services client, it seems sluggish but never fails to connect.

Three of my work sites are located in South Sticks, just beyond Boondock, USA. Their only option (cost conscious) for "broadband" internet is DirecWay. Using the satellite service, the ICA client won't connect at all. The ping times range from 250 to 1200 ms.

Does the ICA client have a timeout? And can it be adjusted to allow for lengthy connections? Is it possible that everything is cool and my problem is related moreso to desert birds?

Thanks in advance,

CR

 

[dietcokebottle]

I have seein and used citrix with latency over 300ms so anything less than 200ms is brilliant and citrix terminal services works good check ur mtu settings or fiddle with them maybe they need adjusting

 

[ProfFate]

Generally Citrix and satellite connections don't mix. I haven't heard of many who have made it work. Check out this document from Citrix, it might help.

http://knowledgebase.citrix.com/kb/...tegoryID=118&entryID=2131&fromSearchPage=true

MikeL

 

[lb63640]

Just now addressing a similar problem with no connections for a Citrix client and Direcway Internet connection. I'm assuming the latency is the problem because the Terminal Services RDP client will make the connection, although it's slow.

Any ideas about where to change the settings...maybe on the server?

 

[fs483]

I for one can confirm that Citrix and Satellite connections does work and Citrix is nearly the only way for users that are on extremely slow links to be able to work from remote. I currently have 3 clients in the middle of the jungle in Africa that connect to Citrix servers in North America in order to do their work. They are on remote mine sites with the closest civilization at over 400km away and even there, the best they can get is telephone modem at 30kpbs connecctions. The only way to communicate with these users are through Sat links from 64K to 256K for an average of 4 to 10 users all at once. When the sat goes down, they are on their own ! The average latency with one of my higher speed sites is around 650ms (normally 300ms uplink from ground station and 300ms downlink from sat to receiver dish + regular latency). VPN is incredibly slow. RDP is better but still very slow and with Citrix its workable. When the Sat link is loaded (ie, 2 VOIP conversations and 2 or 3 users online), you get about the speed of a 2400 bps modem or slower because VOIP has priority before data. I didn't need to do any tweaking to my Citrix for these users. The only thing I changed is the Idle session timeout limit and disconnected timeout limit in the ICA-TCP properties to allow a disconnected users to relog back into their session before it gets flushed. For the native users, they are used to the speed but when I need to connect to their local servers to fix problems, boy do I need a lot of patience. Imagine having line per line refresh, you can actually see the whole screen refresh and if you click on another window or button, you see your whole screen refresh again... I usually get bored waiting so I switch back to my local app to do something (multi-tasking as usual) and it becomes even worse because once I switch back, the whole screen needs to refresh again ! I can't wait till the day my remote sites can afford real high speed dsl links.

akwong

 

[lb63640]

Where do I go to change the settings for the idle timeout?

 

[fs483]

Go to Control-Panel ->Administrative Tools -> Terminal Services Configuration -> select ICA-TCP -> right-click and select Properties -> select Sessions Tab.

 

[lb63640]

All of ours are defaulted to NEVER.

 

[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!