[K12OSN] rdesktop bandwidth?

[Casey Woods]

I'm taking it one step at a time!

I doubt if we'll ever get rid of the Windows terminal servers as the 
primary servers.

The first step is the thin clients (which will be ltsp and will be 
served by an ltsp serer).  These will be for staff and running all the 
Windows apps that can't (just won't) go away.  Once we have the thin 
clients running well with Windows, we'll configure them to access both 
Linux and Windows terminal servers.

They won't know what him them!

I asked about rdesktop here because I know there are people using the 
rdesktop thin client to access both Linux and Windows terminal servers.

Casey

Terrell Prudé wrote:

> On Mon, 2005-10-24 at 14:24 -0600, Casey Woods wrote:
>
>>I have a network with approximately 200 aging Win2K machines that we're 
>>looking to convert to thin clients.  I'm curious as to what the 
>>bandwidth requirements are going to be like on the network?  Can anyone 
>>give me a ballpark figure on how much bandwidth each RDP client will eat 
>>up when doing a Windows Terminal Server session?  I have the resources 
>>to make significant upgrades to the network, but I don't want to spend 
>>the money if its not necessary.
>>
>>Thanks!
>>
>>Casey Woods
>>    
>>
>
>
> Why not consider doing a K12LTSP thin client solution?  :-)
>
> Seriously, though, since this is a K12 *Linux* Terminal Server 
> Project, I don't know if people have done bandwidth analyses for the 
> Windows protocols.  However, I can tell you that, with K12LTSP, 
> TuxType can use up 73Mb/sec of X11 traffic per client.  Therefore, in 
> a LTSP situation like K12LTSP, you'd definitely want to go with 100Mb 
> on the desktop.
>
> --TP
>
>------------------------------------------------------------------------
>
>_______________________________________________
>K12OSN mailing list
>K12OSN at redhat.com
>https://www.redhat.com/mailman/listinfo/k12osn
>For more info see <http://www.k12os.org>
>