From: Jason Meers <Jason.M<eers@mv...> - 2006-06-12 16:23:29
I'm currently using rdesktop 1.4.1 to connect to windows2003 terminal
servers. The majority of my users are using desktop PC's as thin clients
using thinstation 2.13 (I noticed a few thinstation users lurking on
this list to)
When using rdesktop on the same LAN as the terminal server performance
is amazing, however when I use identical clients connect over a
dedicated 2Mb MPLS Leased Line circuit, screen updates and scrolling is
very jerky and blocky.
I have spent about 2 weeks troubleshooting this and have eliminated
several possible causes (by examining packets at byte level and using
WAN simulators and bandwidth throttling tools and proxies).
Although 2Mb of bandwidth exists I rarely ever see more than about
400kb/sec being transfered from the server to all 13 clients. In simple
terms each client only seems to draw 30kb/sec even though roughly
170kb/sec is available to all clients simultaneously.
The line is dedicated to RDP traffic and does not run any other
services. During troubleshooting I can max the line out at 2Mb by
copying files backwards and forwards over the line so I know the line is
working correctly. If anybody needs any further info about what tests
I've done I'll post it but I'm absolutely sure that the problems is either:
A) rdesktop is not requesting enough data from the server, or not
requesting it quick enough when used over the WAN
B) The server is not sending back enough data to clients over the WAN
Latency does not seem to be an issue, I get between 20-80ms response
times and very brief highs of approx 200-250ms.
I don't expect any RDP client to give LAN speed performance from the WAN
but I would expect to see it using more than 20% of the available
bandwidth. If anything I expect a greedy protocol like RDP to take
everything available and still want more.
I have tried every combination of documented command line options for
calling rdesktop, without much success.
Does anybody have any suggestions on what might be causing this behavior
in rdesktop or how I can log/debug/trace what rdesktop is doing.
Any suggestions would be appreciated, all the PC's I use are linux based
and I have the source from CVS this morning so I can try any suggestions
you may have given some specific build instructions.