XP logon problem to a server 2003 domain.

janesssssy

janesssssy

janesssssy

Soldato
Joined
6 Feb 2004
Posts
3,450
Location
Wiltshire
I get this problem often on a dozen or so clients:

"Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found."

i take the client off the domain and delete the computer from AD and then rejion the domain and log on. This works for a couple of days then i have to start all over again. Its driving me potty, I think its to do with the SIDS but am unsure on how to fix the issue.

Any help would be appriaciated. :cool:
 
Last edited:
Im assuming when the machine was built using a system image, it was syspreped first? if not thats the easiest way to duplicate SIDs. also im assuming the DC is listed as the primary DNS on the machine if you log on locally?

Something else to try is take the machine off the domain and delete it's account from AD, then run new sid on it and then rejoin the domain.

http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx

PS: I take no responsibility for you running this and you do it at your own risk.
 
janesssssy said:
I get this problem often on a dozen or so clients:

"Windows cannot connect to the domain either because the domain controller is down or otherwise unavailable, or because your computer account was not found."

i take the client off the domain and delete the computer from AD and then rejion the domain and log on. This works for a couple of days then i have to start all over again. Its driving me potty, I think its to do with the SIDS but am unsure on how to fix the issue.

Any help would be appriaciated. :cool:
Click to expand...

Are you cloning these machines or something? This sounds like the sort of error you get when you have two or more machines on the network with the same computer name. Active directory does contain a user account for the computers to log in with, and these passwords are automatically changed regually. Therefore when one machine changes the pw, the others stop working.

if you are cloning these machines, then next time you are adding a clone, do the following;
a) UNPLUG the network cable and then remove it from the domain with the cable unplugged. This prevents the machine from removing itself from AD
b) Plug the network cable in, and add the machine to the domain with a unique name.
 
To fix the boxes without rebuilding, you can use newsid from sysinternals (now owned by MS) on each box, however, this is not supported by MS.
 
You must log in or register to reply here.
Back
Top Bottom