11 replies
Hi,
Sounds like the TS licensing has gone awry.
Is it a "bad password" message you get or a terminal server busy message?
Cheers,
Tim.
Hi,
Hmmm... Not with that error message. Its too specific.
Do you have PDCs and BDCs? I wonder if one of your BDCs is not synchronising properly and is somehow out of date, but still servicing authentication requests?
Not really sure where to turn with this problem.... Authentication is kind of happening, but badly... wierd.
If you find anything else out, please post it back here for us too!
Cheers,
Tim.
Hi,
I think if it turned out to be a rogue BDC, then you should be able to fix it by fixing up the synchronisation.
But I've never seen anything like that or heard about it either... It was more an answer to fit the symptoms. I have not idea whether its likely or even possible.
I DO think it would be worth your while isolating it to one BDC (or the PDC) by temporarily disabling authentication, though. At least that will be more information for you to work with, even if disabling one ata time makes no difference. Thats information in itself.
Does it take a long time before authentication fails? The other possibility is that the actual message is a bit of a red herring and that something else is causing the problem.
If you have a quiet moment with your servers, like a scheduled outage, I would re-add the licensing information. I've seen licensing cause all sorts of problems but never a specific bad password.
Cheers,
Tim.
by machinetype
by machinetype
by machinetype
by machinetype
by machinetype
by machinetype
by machinetype
by machinetype
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending