Re: bandwidth requirements for Remote Desktop

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Pure gold, Pegasus... thanks...

I'm 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) wrote:
- 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)


"Brains,None" <noone@xxxxxxxxxxxxxx> wrote in message
news:46093D8B.5050509@xxxxxxxxxxxxxxxxx
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.


Pegasus (MVP) wrote:
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.


"Brains,None" <noone@xxxxxxxxxxxxxx> wrote in message
news:46092216.1060608@xxxxxxxxxxxxxxxxx
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) wrote:
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.


"Dragon" <noSpam_baadil@xxxxxxxxxxx> wrote in message
news:uACN$j$bHHA.260@xxxxxxxxxxxxxxxxxxxxxxx
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.

"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:ePWsP7%23bHHA.2552@xxxxxxxxxxxxxxxxxxxxxxx
"Dragon" <noSpam_baadil@xxxxxxxxxxx> wrote in message
news:usQnF18bHHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
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.
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.





.

Relevant Pages

  • Re: Client behind a firewall!
    ... Microsoft MVP - Terminal Server ... Internet with Remote Desktop enabled when I'm at work, ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)
  • Re: Client behind a firewall!
    ... Internet with Remote Desktop enabled when I'm at work, ... ISA Server proxy, which will only let HTTP traffic through; ... Remote Desktop client is blocked, and I just can't use it. ...
    (microsoft.public.windows.terminal_services)
  • Re: bandwidth requirements for Remote Desktop
    ... Pegasus wrote: ... Make sure that Remote Desktop is enabled on the host. ... If the client does not have mstsc.exe, ... If you eventually intend to access the host over the Internet, ...
    (microsoft.public.windows.server.general)
  • Re: bandwidth requirements for Remote Desktop
    ... Thanks so Much, Pegasus... ... 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. ... to use Remote Desktop between internal PCs or over the Internet. ... can collect information regarding how much bandwidth we need for out ...
    (microsoft.public.windows.server.general)
  • Re: bandwidth requirements for Remote Desktop
    ... Thanks so Much, Pegasus... ... 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. ... to use Remote Desktop between internal PCs or over the Internet. ... can collect information regarding how much bandwidth we need for out ...
    (microsoft.public.windows.server.general)