Terminal Application server connection refused

[SWarrior]

We have 2 license servers, one is being phased out. They are in two different locations (same network, different building) When I test each thin client, it grabs a license from the old server, then when I put it out into production, it grabs another license from the new server. We have 17 licenses, but only need 13 right now. These are device licenses. All was working FINE on Friday, but today, 3 of our thin clients can NOT log in. they connect, and then POOF they're gone. I really really need a fast fix for this please.

In addition....

one of the mac addresses has been issued 5 licenses on the one servers temporary licenses, and also one license from the licensing server. ALL licenses are not to expire for about 3 months. two of these 3 licenses (totalling 8 cals) are brand new by less than a month. Total legitimate licenses are 17, and again, there should only be 13 being utilized at this time. I am double cheching and cross referencing ALL the mac addresses that have licenses associated with them, but I don't think that I will be over my 17.

HELP !!!! I need to get all my clients back online! I now have 6 of the 13 that can not connect!!! AARrrrrrrggghhh !!!!!!

-SWarrior

NOTE: the server being phased out has 4 licenses on it, and the new server has a total of 26, 13 of which have been re-installed by microsoft clearing house, but none are being used (have no clue why)

 

[kmcferrin]

Are there any error messages in event viewer? With TS issues I have found that the terminal server or licensing server usually has an error that explains why the connection fails. From there you can usually look up the error message to see what is causing the failure.