Stump the Techies: NetLogon errorsFollow

Y'all are smart. Maybe someone can help me out here. Google has failed me, the dudes we pay for server support in India have failed me, my bosses are stumped, I'm stumped, and we've got a nasty problem on our hands.

Windows Server 2003 Active Directory Domain keeps kicking off random systems for no bloody good reason. It spits out errors 5722, 5723, and a few others in the domain controller's event logs. This means whoever is trying to log into the domain, can't - their system has been kicked out of it. The quick fix for this is to unjoin and rejoin the domain on the offending system, but we have almost 300 PCs in this network, some of them over an hour drive away, making this an extreme annoyance that crashes production to a halt when it happens.

It started out on just laptops, then the newest server started experiencing it, and today for the first time one of the desktops did.

Changes to the network made just before this started happening included adding about 30 new systems since our client sort of absorbed another company and we inherited their equipment (and oh god all their problems too aaaaaggggh.) These systems were previously on another domain, and we brought them onto ours. Funnily enough, none of the new systems are experiencing the issues.

My question is: I have no idea how many client licenses we got for Windows Server 2003, but I'm wondering if we're short on licenses if this is what starts happening? The domain just starts kicking off previously established trust relationships with machines because we're out of freaking licenses?

Or, is there some other more obvious thing?

Or is this all just a massive coincidence?

Really, we want to know what the root cause of these errors are so we can stop dropping everything and running to reboot the fax server a few times so people can fax stuff... We can't keep unjoining and rejoining laptops every morning.

Edited, Nov 28th 2011 4:18pm by catwho

Yeah if that's the case, I'm not sure what the next step is going to be. I know we're upgrading the whole place to virtual servers come Jan (*glee!*) but I'm not sure what the plan was for the actual OSes...

We plan to, and in the meantime we kept the old site's naming convention so that shouldn't be the problem.