Hi Todd,
Firstly, is this a 2000 or 2003 terminal server. You say
below 2003, but then add that it is running SP4. There is
no SP4 for 2003!
I'll presume you're running 2003, in which case you must
have a 2003 server with terminal server licensing
installed. As far as I know, a 2000 server cannot serve
licenses for a 2003 TS. However, a 2003 license server
can serve licenses for 2000 and 2003 TS's.
Also, unless you install terminal server licensing on
your TS, or on a 2003 DC, you will have to add the
registry entry you have already mentioned for the TS to
be able to see the 2003 license server.
Hope this helps, and that my info is correct.
Daniel.
>-----Original Message-----
>Ok background info --
>
>Terminal Server = Windows 2003 Standard w/ Terminal
Services SP4 and
>ALL crit patches as of today 2/16/2004.
>
>This server has been in operation for ~ 6 months with NO
licensing
>problems. I have a license server set up on one of my
Windows
>2000(SP4) DC's in the same domain on the same network,
no firewalls,
>no routers they are even on the same switch.
>
>All of a sudden on Saturday I started getting "No
license server
>available" messages on the clients, on the server side
it is reporting
>1004 errors. So first I tried the client fix of
deleting the
>MSLicense key, rebooting no good. Plus no clients can
connect so it
>is definately the server.
>
>Second the server can see the license servers just
fine .. if I go to
>"Terminal Server LIcensing" on the TS it sees my LS just
fine, shows
>it as active with plenty of open lisences. For the heck
of it I added
>the ...\TermServices\Paramaters\LicenseServers\Apps2_Serv
er (netbios
>name of my TS Lic server) rebooted and same thing.
>
>To my knowledge and the searches I have done these are
all the fixes
>to do ? Why can not even windows clients connect when
it is obvious
>the TS can see the Lic Server just fine ? Any
suggestions ?
>.
>
|