I have a Server2003 Terminal Server that past its 120 day terminal
server eval period.

We do have a lincensing server on the domain, which is a win2000 server,
which is also one of our domain controllers.

I made sure the licensing server is activated and added some client
access licenses to it. The Server2003 Terminal Server says that it is
unable to find a licensing server on the domain. If I bring up Terminal
Server Licensing on the 2003 Terminal Server, it says it can't find a
licensing server and says to 'connect' to one. So, I chose Server and
Connect and put in the dns name of our licensing server (domain
controller) and it connects to it fine.

So, why wouldn't it be able to find it on the domain? No one can connect
to the terminal server until I can figure this one out. Connections are
allowed up to the point they put in their username/password then they
get a message saying they aren't allowed to connect to this session.

A 2003 Terminal Server *must* use a 2003 TS Licensing Server, so it's
normal that it doesn't want to recognize your W2K TS Licensing server
as a valid LS.

You need to install the TS Licensing Service on a 2003 server (can be
the same server as the TS, and doesn't have to run on a DC anymore.
Then you have to buy and install 2003 TS CALs on the LS, since a 2003
TS cannot use W2K TS CALs.
If the TS doesn't automatically detect the 2003 LS, you can point the
TS to it:

279561 - How to Override the License Server Discovery Process in
Windows Server 2003 Terminal Services
http://support.microsoft.com/?kbid=279561

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/priclic
faq.mspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Jim in Arizona <tiltowait DeleteThis @hotmail.com> wrote on 15 sep 2006 in
microsoft.public.win2000.termserv.apps:

> I have a Server2003 Terminal Server that past its 120 day
> terminal server eval period.
>
> We do have a lincensing server on the domain, which is a win2000
> server, which is also one of our domain controllers.
>
> I made sure the licensing server is activated and added some
> client access licenses to it. The Server2003 Terminal Server
> says that it is unable to find a licensing server on the domain.
> If I bring up Terminal Server Licensing on the 2003 Terminal
> Server, it says it can't find a licensing server and says to
> 'connect' to one. So, I chose Server and Connect and put in the
> dns name of our licensing server (domain controller) and it
> connects to it fine.
>
> So, why wouldn't it be able to find it on the domain? No one can
> connect to the terminal server until I can figure this one out.
> Connections are allowed up to the point they put in their
> username/password then they get a message saying they aren't
> allowed to connect to this session.