I have a Windows 2000 domain with TS licensing running on
the DC. I also have a 2003 TS running in App mode joined
to the domain and now is giving licensing errors. We have
added 20 more licenses in Device mode but it is still
rejecting connections from inside and outside.

That's because a 2003 TS *must* use a 2003 Licensing Server.
A W2K LS cannot handle the new types of TS CALs that were introduced
with 2003.

The good news is that 2003 does not have the requirement that the LS
must run on a DC. So you can just install the 2003 LS on to the 2003
TS, install your 2003 TS CALs on it and you should be fine.

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserv...ensing/priclic
faq.mspx

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

"Jeramy" <(E-Mail Removed)> wrote in news:012301c3da0d
$660e5070$(E-Mail Removed):

> I have a Windows 2000 domain with TS licensing running on
> the DC. I also have a 2003 TS running in App mode joined
> to the domain and now is giving licensing errors. We have
> added 20 more licenses in Device mode but it is still
> rejecting connections from inside and outside.

Are you using the licensing services of Windows 2003
Server?

If not, this is your problem. Add the licensing service on
your windows 2003 server and add your TSCAL on it (per
device or user mode), it should work well.


Charles
>-----Original Message-----
>I have a Windows 2000 domain with TS licensing running on
>the DC. I also have a 2003 TS running in App mode joined
>to the domain and now is giving licensing errors. We have
>added 20 more licenses in Device mode but it is still
>rejecting connections from inside and outside.
>.
>