Thx Joe, that's what I was referring to as well. I have a few mixed
modes that the TS box holds the CALS and a few Win2k DCs that the CALS
must be on the DC box itself. The odd thing though is that the message
out of licenses doesn't seem correct. When I run out of licenses it just
kicks me out..
-----Original Message-----
From: Joe L. Casale [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 01, 2001 3:20 AM
To: NT System Admin Issues
Subject: RE: Win2000Server Terminal Services Licensing Problem
Support WebCast: Microsoft Windows 2000 Terminal Server Licensing
Description and Troubleshooting
March 15, 2001
"...A frequent question that we're asked is where exactly do I need to
install the Terminal Server licensing (slide 6)? And the answer for that
depends on the environment that our customers are in. If there's a
Windows 2000 Terminal Server in a Windows NT 4.0 domain, then the
Terminal Server Licensing service can be installed on a Windows 2000
member server. In fact, that would be required, because if you have a
Windows 2000 domain controller, then you are in a Windows 2000 domain.
In a Windows 2000 domain, this is required to be installed on a Windows
2000 domain controller. There's no restriction in the installation
Terminal Services License services themselves, but the service will fail
to start unless the machine is the domain controller in a Windows 2000
domain..."
Eval versions offer a slightly relaxed license model until you go into
production/expire @ 90 days.
Where did you install the license server?
What do your logs say?
More info...
jlc
-----Original Message-----
From: Benjamin Zachary [mailto:[EMAIL PROTECTED]]
Sent: Saturday, September 01, 2001 12:53 AM
To: NT System Admin Issues
Subject: RE: Win2000Server Terminal Services Licensing Problem
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
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
