migration to AD2003 affected TS's

We have 3 TS's. 1 license and 2 that serve out Published Desktop.
Everything with access was perfect before NT to 2003 migration on domain.
Once the domain was migrated we changed our TS per device to per user.
TS1 is the initial TS and is always accessible.
TS2 is NOW not accepting connections unless we reboot TS1, which it will
then only allow connections for 24 hours or so. At some point users start
getting an error message on TS2 that they must be in the Remote Desktop Users
group.
If we reboot TS1 then TS2 users can access for another 24 hours or so.
group membership has not changed. Ideas? why does a reboot of the other
server allow access temporarily?

"TommyKnight" <TommyKnight.TakeThisOut@discussions.microsoft.com> wrote
> We have 3 TS's. 1 license and 2 that serve out Published Desktop.

Why have one dedicated to being a license server? Why not have the license
service installed on your DC? Is the Licencse server a DC, and if not, is it
setup as the prefered license server on the 2 TSs?

> Everything with access was perfect before NT to 2003 migration on domain.
> Once the domain was migrated we changed our TS per device to per user.

Why go from "per device" to "per user"?

> TS1 is the initial TS and is always accessible.

Am I right in assuming you have some form of load balancing in place? What
is it?

> TS2 is NOW not accepting connections unless we reboot TS1, which it will
> then only allow connections for 24 hours or so.

Are you able to connect to each server explicitly from an RDP client?
When you fail to connect, there should be an entry in the event log of the
server that refused the connection. What is it / what does it tell us?

> At some point users start
> getting an error message on TS2 that they must be in the Remote Desktop
> Users
> group.
> If we reboot TS1 then TS2 users can access for another 24 hours or so.
> group membership has not changed. Ideas? why does a reboot of the other
> server allow access temporarily?

Check licensing, check load balancing, check event logs and see what's
happening. Troubleshoot that and see if the problems go away. If not, ask
the question again.