W2K Terminal Server Licensing Issues

 I have a Win2k terminal server running in application mode as a member server of an AD domain.  The Domain is all W2k servers,all SP2, Native mode, AD integrated DNS.  No DNS or replication issues so far as I can tell.  Right now there are 2 sites and 10 different subnets.  I've bought and installed TermServ CAL's and installed the term serv licensing service on a DC on a different subnet in a different site although the actual term server
will eventually be moved over to that site.   The TS licensing server shows the CAL's as being installed and only 1 has been issued although it does show about 6 existing win2k pro clients as having connected.  I have an easy 20 some users who have connected at some point.  
I get the following error on the term server about 2 to 3 times a day.
Event ID: 1010  Source: TermService
The terminal services could not locate a license server. Confirm that all license servers on the network are registered in WINS\DNS, accepting network requests, and the Terminal Services Licensing Service is running.  

  Does the TS licensing server create a special record type in either DNS or WINS?  I haven't seen any mention of it in any documentation and  don't appear to have any name resolution issues,   all the A records are cool in my forward and reverse zone.  All the servers see all the other servers.  

 My fear is that once my 90 day grace period is up and the term server no longer grants temporary licenses, and it's approaching quickly,  that I'll have a mission critical application that will be unavailable. That would of course be bad. Need I be worried or is this another somewhat typical erroniuous windows error. Any help is greatly appreciated.  
Who is Participating?
igoreConnect With a Mentor Commented:
The Terminal Server locates the Terminal Server Licensing server through broadcast.  The likelies reason it can't find the TSLS is because the broadcast is blocked at some point.  The optimal configuration of TSLS is in the same site as the TS.  You can verify this by installing a TSLS in the same site as the TS to see if this resolves the issue.  You'll need to call Microsoft Clearinghouse to be able to reinstall the licenses on the new Terminal Server, state that you are moving the TSLS between servers and they should re-issue you the licenses.  Changing the License Activation method to 'Telephone' will give you the number to call.
Try looking up MS KB Article Q261110, or Q239107.  This may help you in the right direction.
Also, it doesn't seem like a lot of help, but you could try Q281258
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

sorry, and 232520
birdskiAuthor Commented:
   Good suggestions however I've previously seen the Q articles and tried those steps with no joy.  I'm still getting those errors but it hasn't yet shut down on me.
Maybe I'm really ok.
  No TermServ experts out there?
birdskiAuthor Commented:
This is as close as I've gotten to an answer, unfortunately I have not yet been able to move the server to the same subnet as the license server yet.   Will post follow up if the results are good.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.