Remote Desktop Connection mystery...

  • Thread starter Thread starter Danny Counts
  • Start date Start date
D

Danny Counts

I used to not have any issues with RDC working; as long
as I have a valid internet connection, everything works,
but no longer.

Everytime I buy a new notebook for the company with it's
own version of XP home or pro, establish the internet
connection, I get the message that the client could not
establish a connection to the remote computer when using
RDC. I spent 3 hours on the phone with Microsoft where we
altered a reg key and this worked for a few systems, but
this does not work any longer. WHY IS THIS NOT WORKING
ANYMORE? It is a bit frustrating.
 
Can you elaborate? Are you using Windows XP Remote Desktop "Client" on these computers to connect to a terminal server, or are they logging onto their desktop computers (using RDC) from their notebooks

If they're logging onto a TS then there's licensing involved. More Terminal Services Licensing info here

http://www.workthin.com/tsls2k.htm (for 2000 Terminal Servers
http://www.workthin.com/tsls2k3.htm (for 2003 Terminal Servers

Patrick Rous
Micrsoft MVP - Terminal Serve
http://www.workthin.co

----- Danny Counts wrote: ----

I used to not have any issues with RDC working; as long
as I have a valid internet connection, everything works,
but no longer

Everytime I buy a new notebook for the company with it's
own version of XP home or pro, establish the internet
connection, I get the message that the client could not
establish a connection to the remote computer when using
RDC. I spent 3 hours on the phone with Microsoft where we
altered a reg key and this worked for a few systems, but
this does not work any longer. WHY IS THIS NOT WORKING
ANYMORE? It is a bit frustrating
 
I am connecting to a remote server. How come I can connect
two RDC sessions on my old system simultenously, but not
even once on the new system. I have asked all 10 of my
employees to log off the terminal server, but I still
cannot gain access to the terminal server or start even
one session on any new system, or new install of XP Pro.
Does the terminal server detect a new machine or machine
name and thus not let it connect, even if there are no
other current connections/

-----Original Message-----
Can you elaborate? Are you using Windows XP Remote
Desktop "Client" on these computers to connect to a
terminal server, or are they logging onto their desktop
computers (using RDC) from their notebooks.
If they're logging onto a TS then there's licensing
involved. More Terminal Services Licensing info here:
 
What OS is the server running on? If it is a Win2K3, you aren't going
to get any "comp"-ed licenses by running Windows XP. This could be
what is causing your difficulties.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Back
Top