not entirely true because win2k pro and server come with a terminal server
license. They changed how the licensing works with Win2k terminal server.
The server no longer keeps all of the licenses but instead issues them to a
client that will always have it. Very hard to administer in my opinion since
once the license is taken you can not get it back without calling up
microsoft and having them change it for you. The question that i would have
is: Is server 1 an NT 4 terminal server or are they both Win2k terminal
servers running in admin mode? If both are win2k servers then the license
theory is dead since it would have the correct licensing on the machine
because it can attach to one of the Win2k machines. The next things i would
look at would be to check and make sure that you can ping it from that
machine, User profile is administrator of the box, and upgrade to the win2k
terminal services client if you have not done so already. Not sure if that
would help any since the old one should be able to connect to the server but
just not be able to use the new features. It probably is not that 2 people
have already connected to it since that error message indicates that the
number of connections has been exceeded. Sorry couldn't help more.
Greg T.
-----Original Message-----
From: Bill Higgins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 20, 2001 10:28 AM
To: NT System Admin Issues
Subject: RE: Problem Connecting to Terminal Server
shouldn't be a licenese issue... the Terminal Server is running in
Administrative Mode (no licensing required) not Application Sharing Mode...
If it was Licensing, I would expect that no clients could connect to
Server1:
-----Original Message-----
From: Mal Sasalu [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 20, 2001 08:26
To: NT System Admin Issues
Subject: RE: Problem Connecting to Terminal Server
Could this be a license issue?. We had similar problems on our citrix.
-----Original Message-----
From: Bill Higgins [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 20, 2001 8:52 AM
To: NT System Admin Issues
Subject: Problem Connecting to Terminal Server
Server1: W2K Advanced Server, SP2, running Terminal Server in remote
administration mode
Server2: W2K Advanced Server, SP1, running Terminal Server in remote
administration mode
Client1: Win98
Client2: W2K Advanced Server, SP1
Client3: W2K Pro
Client2 and Client3 can connect to Server1 and Server2 with no problems.
Client1 can connect to Server2 with no problem
Client1 cannot connect to Server1, get "the terminal server has ended the
connection" dialog box before a login box.
I have checked Technet and it is not:
http://support.microsoft.com/support/kb/articles/Q237/7/92.ASP?LN=EN-US&SD=g
n&FR=0&qry=%26quot%3Bthe%20terminal%20server%20has%20ended%20the%20connectio
n%26quot%3B&rnk=11&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL (running in admin mode,
not app mode)
Any suggestions?
Bill Higgins
Lead NT Systems Engineer
(415) 402-3444 office
(415) 720-7053 cell
[EMAIL PROTECTED]
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
