Windows cannot connect to domain... etc

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I ordered 3 PCs and I reinstall one of the PC with Windows XP Professional
and I cloned it to the rest of the PCs. I don't have any problem connecting
the source and clone #1 PCs to the domain but when I tried to connect the
clone #2 and it gave me a message "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 already renamed the computer,
so I don't know what's going on. These 3 PCs are idential the same, so I
don't understand why clone #2 wasn't able to connect to the domain. Please
help!. Thanks.

BTW, mine is a Windows 2000 domain.

Billy
 
billy said:
I ordered 3 PCs and I reinstall one of the PC with Windows XP Professional
and I cloned it to the rest of the PCs. I don't have any problem connecting
the source and clone #1 PCs to the domain but when I tried to connect the
clone #2 and it gave me a message "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 already renamed the computer,
so I don't know what's going on. These 3 PCs are idential the same, so I
don't understand why clone #2 wasn't able to connect to the domain. Please
help!. Thanks.

BTW, mine is a Windows 2000 domain.

Billy
try moving the PC to a workgroup and then rejoin it to the domain.
 
By cloning, all machines are identical down to the UUID and SID. This is
where the problem lies as the uniqueness is no longer there to distinguish
between entities.

If you are using Symantec Ghost for example, run the ghostwalker utility
to provide a different machine name. The UUID / SID will be randomly
regenerated,
after which your problem should go away.
 
Desmond Lee said:
By cloning, all machines are identical down to the UUID and SID. This is
where the problem lies as the uniqueness is no longer there to distinguish
between entities.

If you are using Symantec Ghost for example, run the ghostwalker utility
to provide a different machine name. The UUID / SID will be randomly
regenerated,
after which your problem should go away.

Desmon probably provides the answer but
you might also wish to ensure the machine
names are DIFFERENT.
 
Back
Top