asked on

How does RDP client determine when to end a connection and then try?

I have a remote site with only 1.5 mbps... It's a symmetrical connection. We have 1.5 up and down.. Whenever I have 4-5 users trying to RDP into the remote server they randomly end their connections and start to retry. From what I can tell when allow of them are connected and if a few users try to download items via HTTP the circuit gets congested and starts to drop RDP sessions. I changed the RDP clients to use dial up experience mode and we'll see how this works out. But. How does the RDP client actually determine when to timeout and disconnect? If it based on available throughput/bandwidth at the moment in time or is it based on latency? I would assume it's based on what experience level you have it set on and the available throughput/bandwidth...

ASKER CERTIFIED SOLUTION

Neale Williams

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gopher_49

ASKER

This is a good article.. I'm considering changing the packet acknowledgement values on the TCP/IP stack... Some of our remote sites on have 1.5 mbps and it's easily congested. I'm thinking that if I increase the packet acknowledgement values on the TCP/IP stack users will see a lag but not actually get disconnected. I think that will be a better experience. I thought about implementing best of QoS at the edge of my network, however, it almost seems I need to bandwidth throttle too.

Thanks.,

Neale Williams

Glad it helped!
If you have the budget you could also look at WAN accelerators.

gopher_49

ASKER

This article gives clarification of how RDP and Citrix handle poor bandwidth.