On a win2k server, the TS Cals must be installed on a DC I believe. Even
still, this shouldn't be the case, because you can connect 15 pcs for 90
days from temporary licenses. Sounds like something else is wrong. Check
that the users can connect with TS in AD, and check configuration for
ports etc etc. I havent seen that before
-----Original Message-----
From: William Rogge [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 31, 2001 2:15 PM
To: NT System Admin Issues
Subject: RE: Win2000Server Terminal Services Licensing Problem
A possibility, but upon checking, NOPE, it is in Application Server
Mode.
Any other ideas?
-----Original Message-----
From: Bill Kuhn - MCSE [SMTP:[EMAIL PROTECTED]]
Sent: Friday, August 31, 2001 1:14 PM
To: NT System Admin Issues
Subject: RE: Win2000Server Terminal Services Licensing Problem
It sounds like you installed Terminal Services in the Administrative
mode rather than the Application Server mode.
> -----Original Message-----
> From: William Rogge [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 31, 2001 11:59 AM
> To: NT System Admin Issues
> Subject: Win2000Server Terminal Services Licensing Problem
>
>
> We have only 1 Win 2K server in house. We have enabled
> Terminal Services
> to prepare in the migration of our NT-4.0 Terminal Server Edition
> platforms.
>
> We have installed 60 Cals and 15 TS Cals. The TS Cals have
> been activated
> (at least they show as activated).
>
> In this setup, we can only establish 1 connection for another
> system. When
> the second system attempts to establish a connection, it is
> refused. Upon
> checking Event Log, it states that there are no more Terminal Service
> licenses available.
>
> Has anyone seen this, and if so, how can I correct this situation?
>
> Thanks for your expert assistance.
>
> 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
