Remote Desktop Connection on new machines

[Danny Counts]

All of my older machines are fine. When I buy new XP Home
or Pro and try to connect to my terminal server (which
has a static and public IP) I get the same message on
about 5 new systems I have bought and that is:

The client could not establish a connection to the remote
computer. The most likely causes are for this error are:
1. Remote connections might not be enabled at the remote
computer. (It is enabled and 10 people are currently
connected)
2. The maximum number of connections was exceeded at the
remote computer. (This is not the case as I have
unlimited number of connections and can login in several
times on my older system)
3. A network error occured while establishing a
connection (yet IE works fine).

Why do all the new systems I buy these days not connect
properly to my remote server via RDC?

 

[Eric]

-----Original Message-----
All of my older machines are fine. When I buy new XP Home
or Pro and try to connect to my terminal server (which
has a static and public IP) I get the same message on
about 5 new systems I have bought and that is:

The client could not establish a connection to the remote
computer. The most likely causes are for this error are:
1. Remote connections might not be enabled at the remote
computer. (It is enabled and 10 people are currently
connected)
2. The maximum number of connections was exceeded at the
remote computer. (This is not the case as I have
unlimited number of connections and can login in several
times on my older system)
3. A network error occured while establishing a
connection (yet IE works fine).

Why do all the new systems I buy these days not connect
properly to my remote server via RDC?
.
This is also happening on our computers which have XP

home (not XP pro) after doing a windows update -
unfortunately, we don't know which one. Hopefully the
MVPs do....

 

[Guest]

Terminal Services requires a Terminal Services Licensing Service to be running, which can identify if the client has a TSCAL or not. In 2000 TS, 2000 & XP "Pro" machines receive a free TSCAL when connection to the TSLS, however in 2003 TS all clients require TSCALs

The first thing to check are the event logs on the terminal server to see what the problem is, i.e. can't locate a TSLS, no TSCALs available..

The second thing to check is the TS Licensing Management Console, to see if there are licenses available

Licensing info here

http://www.workthin.com/tsls2k.htm (for 2000 TS



http://www.workthin.com/tsls2k3.htm (for 2003 TS

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

----- Eric wrote: ----

-----Original Message----
All of my older machines are fine. When I buy new XP Home
or Pro and try to connect to my terminal server (which
has a static and public IP) I get the same message on
about 5 new systems I have bought and that is
computer. The most likely causes are for this error are
1. Remote connections might not be enabled at the remote
computer. (It is enabled and 10 people are currently
connected
2. The maximum number of connections was exceeded at the
remote computer. (This is not the case as I have
unlimited number of connections and can login in several
times on my older system
3. A network error occured while establishing a
connection (yet IE works fine)
properly to my remote server via RDC

This is also happening on our computers which have XP

home (not XP pro) after doing a windows update -
unfortunately, we don't know which one. Hopefully the
MVPs do...

 

[Guest]

Hi Patrick. I'm working on the problem for Eric. The remote server IS Win 2000 server (not 2003). There should be licenses available, because there were 5 weeks ago before he used windows update on the XP home computers. The XP pro computer still attaches fine. We think the problem may be with remote windows xp home computers. thanks, sheryn.

 

[Jeffrey Randow (MVP)]

XP Home machines are not comped any licenses with a Win2K-based
terminal server.. Only XP (or Win2K) Pro machines are comped a
license...

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

 

[sheryn]

Hi Jeffrey. Thank you for the reply. Does this mean we
now all of a sudden have to buy a couple of licenses (the
win XP home machines could attach up until about 5 weeks
ago)? or upgrade to winXP pro? How to buy the licenses,
that is, what is the product called? I'm also trying to
set this up for a Mac Ibook. Does it need a license also?
thanks. s

-----Original Message-----
XP Home machines are not comped any licenses with a Win2K- based
terminal server.. Only XP (or Win2K) Pro machines are comped a
license...

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

remote server IS Win 2000 server (not 2003). There
should be licenses available, because there were 5 weeks
ago before he used windows update on the XP home
computers. The XP pro computer still attaches fine. We
think the problem may be with remote windows xp home
computers. thanks, sheryn.

 

[sheryn]

PS. found this on a different post: All We want is xp
home clients. And they were working before an auto
windows xp update. ??

Subject: Re: XP Home
From: "Marc Reynolds [MSFT]"
<[email protected]> Sent: 2/27/2004 6:15:23 AM

XP Home can be a remote access client, but not a remote
access host.

-----Original Message-----
XP Home machines are not comped any licenses with a Win2K- based
terminal server.. Only XP (or Win2K) Pro machines are comped a
license...

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

remote server IS Win 2000 server (not 2003). There
should be licenses available, because there were 5 weeks
ago before he used windows update on the XP home
computers. The XP pro computer still attaches fine. We
think the problem may be with remote windows xp home
computers. thanks, sheryn.

 

[Jeffrey Randow (MVP)]

Take a look at
http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfaq.asp
which will give more information on the licensing requirements of
terminal server in application mode...

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

 

[Jeffrey Randow (MVP)]

How long were these clients connecting? If it was around 90 days, you
hit the TS licensing limit...

From the FAQ:
The Windows 2000 terminal server has a 90-day grace period before it
must find a license server. During this grace period, the terminal
server allows connections from clients without license tokens. If this
90-day grace period has passed and the terminal server still has not
located a license server, the terminal server provides sessions only
to clients that have been issued a license token. If a Windows 2000
terminal server locates a Windows 2000 license server during this
grace period, the grace period is immediately ended.


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

PS. found this on a different post: All We want is xp
home clients. And they were working before an auto
windows xp update. ??

Subject: Re: XP Home
From: "Marc Reynolds [MSFT]"
<[email protected]> Sent: 2/27/2004 6:15:23 AM

XP Home can be a remote access client, but not a remote
access host.

-----Original Message-----
XP Home machines are not comped any licenses with a Win2K- based
terminal server.. Only XP (or Win2K) Pro machines are comped a
license...

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

remote server IS Win 2000 server (not 2003). There
should be licenses available, because there were 5 weeks
ago before he used windows update on the XP home
computers. The XP pro computer still attaches fine. We
think the problem may be with remote windows xp home
computers. thanks, sheryn.

.

 

[Jeffrey Randow (MVP)]

XP Pro machines will connect fine...

You stated that you were trying to connect with XP Home, which is not
comped a license. The update would have nothing to do with this...

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

We're not sure where to check the state of the license. BTW it's a win 2000 server and all clients do have win XP Pro. A new XP pro machine wouldn't connect. One computer still does connect - why would one computer not hit a licensing limit?? Also, remember, earlier, I wrote that this problem occurred after running a microsoft windows update (?).

Thanks..


----- Jeffrey Randow (MVP) wrote: -----

How long were these clients connecting? If it was around 90 days, you
hit the TS licensing limit...

From the FAQ:
The Windows 2000 terminal server has a 90-day grace period before it
must find a license server. During this grace period, the terminal
server allows connections from clients without license tokens. If this
90-day grace period has passed and the terminal server still has not
located a license server, the terminal server provides sessions only
to clients that have been issued a license token. If a Windows 2000
terminal server locates a Windows 2000 license server during this
grace period, the grace period is immediately ended.


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

PS. found this on a different post: All We want is xp
home clients. And they were working before an auto
windows xp update. ??

Subject: Re: XP Home

From: "Marc Reynolds [MSFT]"

XP Home can be a remote access client, but not a remote access host.
-----Original Message-----
XP Home machines are not comped any licenses with a Win2K- based
terminal server.. Only XP (or Win2K) Pro machines are comped a
license...
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
On Thu, 26 Feb 2004 12:36:09 -0800, Sheryn
Hi Patrick. I'm working on the problem for Eric. The

remote server IS Win 2000 server (not 2003). There
should be licenses available, because there were 5 weeks
ago before he used windows update on the XP home
computers. The XP pro computer still attaches fine. We
think the problem may be with remote windows xp home
computers. thanks, sheryn.

.