Windows Server - bandwidth requirements for Remote Desktop

Asked By Dragon on 26-Mar-07 12:36 PM
Hi,

We are planning on setting up a WAN between multiple locations using limited
bandwidth. Over these connections we will have our custom applications
sending data as well as using it for Remote Desktop (Support Purposes). We
can collect information regarding how much bandwidth we need for out
applications but I need to know what is the minimum bandwidth I need to be
able to connect two sessions at a time and still have decent experience (No
Audio/Video etc). It will simply be used for supporting regular Windows
application. Graphics requirements could be compared to Office 2003
applications.

Thank you.




Pegasus \(MVP\) replied on 26-Mar-07 04:36 PM
limited
(No

Remote Desktop works reasonably well if both machines are on a
256/64 ADSL link but becomes a lot more responsive if the host is
on a 1500/256 link with the client having 512/128 kBits/s.
Dragon replied on 26-Mar-07 05:49 PM
Thank you Pegasus.

Unfortunately, DSL is not an option for us as it is extremely unreliable at
these locations. We are thinking about Frame links. Currently, everyone is
suggesting 64K links (think cost). With going to 128K, our cost goes more
than double. What do you think?

Thanks.
Herb Martin replied on 26-Mar-07 05:56 PM
Depends on what you wish to use it for.

It can work across fairly slow lines if you optimize it (cache graphics,
turn off desktop features etc) but it will become progressively more
irritating as the speed decreases AND as the SCREEN you are viewing
needs to be updated more rapidly.

And remember, that raw speed is actually not directly relevant -- the
key is rather AVAILABLE bandwidth and so if more people use it
or use it for other things it will suffer, AND  Latency which is how
long it takes to get back an answer as opposed to moving a lot of
traffic.
Dragon replied on 26-Mar-07 06:07 PM
Thank you Herb. I understand the comments you have made.
Currently we are in the process of figuring out how much bandwidth is needed
for our applications. Once that is fullfilled, I will be asked for how much
bandwidth I need for supporting these sites. Since, these will be frame
sites, I should have guarenteed bandwidth. For example, if 14k is needed for
our applications, I should have 50k (Minus any overhead etc) for my support.

Thanks.
Pegasus \(MVP\) replied on 26-Mar-07 06:10 PM
I have used Remote Desktop on dial-up links (which is a little slower
than Frame Relay). As Herb says, it works but it gets somewhat
irritating. Fortnunately there are some settings you can select so that
the product makes the best possible use of the limited bandwith.
IMHO RDP is still faster that WinVNC and much, much faster
than pcAnywhere, hence it's the best you can use.


at
Dragon replied on 26-Mar-07 06:17 PM
Thank you Pegasus.
Brains,None replied on 27-Mar-07 08:54 AM
Dear Pegasus, I'm interested in this technology, since soon maybe I'll
have to put my servers somewhere other than under my desk..

how is security set up on Remote Desktop, and is there any how-tos for a
total newbie at this?  I've done terminal i/o on older vms and unix'es,
and pc-anywhere also, configuring encryptions, passwords and so forth.

I'd LOVE to learn more, esp. since it's built-in into the OS..

j.
Pegasus \(MVP\) replied on 27-Mar-07 09:07 AM
Have a look at the links below. They describe various security
aspects and encryption methods.
http://support.microsoft.com/kb/275727
http://download.microsoft.com/download/8/1/5/81550d5c-761f-4946-9731-a3afd1a80b10/remoteaccess.doc
http://www.microsoft.com/technet/itsolutions/network/vpn/vpnfaq.mspx
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c08621675.mspx

Before I can give you any configuration advice, you need to state if you
wish
to use Remote Desktop between internal PCs or over the Internet.


unreliable
is
more
applications
Purposes).
to
experience
Windows
Brains,None replied on 27-Mar-07 10:51 AM
Thanks so Much, Pegasus...  Links like these are EXACTLY what I needed.

our primary goal is to access 'em over the internal internet, at first,
in the same subnet, then, later, maybe between subnets in a class C address.

111.222.333.x at first, then

111.222.333.x controlling 'em at 111.222.555.x...

that's the basic idea. we have firewalls around the 111.222.x.x..
(hopefully...)

j.
Brains,None replied on 27-Mar-07 10:52 AM
Thanks so Much, Pegasus...  Links like these are EXACTLY what I needed.
Oh, i forgot...  these are win 2000 and win 2003 servers, the 2003 is
not a R2..

our primary goal is to access 'em over the internal internet, at first,
in the same subnet, then, later, maybe between subnets in a class C address.

111.222.333.x at first, then

111.222.333.x controlling 'em at 111.222.555.x...

that's the basic idea. we have firewalls around the 111.222.x.x..
(hopefully...)

j.
Pegasus \(MVP\) replied on 27-Mar-07 04:37 PM
- Make sure that the Terminal Server service is running on the
Remote Desktop server.
- Make sure that Remote Desktop is enabled on the host.
It's been a while since I did this - you may have to dig around
to find where to enable it.
- Run this command on the Remote Desktop client:
mstsc 111.222.123.64

If the client does not have mstsc.exe, download and install it
from here:
http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp

If you eventually intend to access the host over the Internet, consider
changing the RD port number in order to make it less visible. You
can do it here:
HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\Por
tNumber
The command would then be:
mstsc 111.222.123.64:23123 (for example)


address.
http://download.microsoft.com/download/8/1/5/81550d5c-761f-4946-9731-a3afd1a80b10/remoteaccess.doc
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c08621675.mspx
a
that
everyone
using
out
need
DevilsPGD replied on 27-Mar-07 06:38 PM
Most important, in my experience, is the latency.  I'll take a
128Kb/128Kb loop at 10ms over a full dedicated T1 at 200ms if I'm
working across an RDP session all day.
--
Insert something clever here.
Brains,None replied on 28-Mar-07 09:13 AM
Pure gold, Pegasus... thanks...

I am real sure i'll have other questions, but for now this is really the
best i've seen yet..

I should email you a cup of coffee....

J.
Pegasus \(MVP\) replied on 28-Mar-07 09:21 AM
Thanks for the feedback.

HKLM\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\Por
http://download.microsoft.com/download/8/1/5/81550d5c-761f-4946-9731-a3afd1a80b10/remoteaccess.doc
http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c08621675.mspx
you
I'll
for
unix'es,
forth.
slower
goes
2003