Link to home
Start Free TrialLog in
Avatar of wilfrieds
wilfrieds

asked on

Windows XP Professional clients cannot log on to Windows 2000 server after Restore of Server

I am running a windows 2000 server with WIndows XP professional clients.
I just had to restore the Server from a backup for various reasons.  I used Norton Ghost 2003 latest update to do that.
The server works fine, BUT my clients are unable to logon.  I can ping all the machines so it is not a connectivity issue.
The message I get on the clients varies a bit, but mainly is that the domain controller for the domain cannot be found.
I have already tried to log on locally to one of the clients, then tried to rejoin the domain.  However, when I do that (using the Aministrator account), first the system tells me there already is a computer account for that computer and do I wish to use that; when I say yes the system tells me it is impossible to execute that command as more than one user with the same name are logged on at that moment.  Obviously, that is not the case.
The server directory lists all computer accounts.
I think that if I delete the computer accounts manually from my server database, I will probably be able to rejoin the domain, but for obvious reasons do not like to do that (and it is not a very elegant solution either).
I wonder if this happens as well when you break a mirror and want to use the second disk to reboot.
Avatar of Fatal_Exception
Fatal_Exception
Flag of United States of America image

For any other experts who want to read the previous post that got us to this point:

https://www.experts-exchange.com/questions/20934946/Change-drive-letter-of-windows-2000-boot-system-disk.html#10702949

Will ck back after I get to work..

FE
BTW:  first experiment and verify that by deleting a computer account that you can now rejoin the domain..  could be that the SIDs are what is causing the problem...  

Breaking the mirror should not cause this to happen de facto..
Avatar of sirbounty
Try this:

Start->Run->CMD <enter>

NLTEST /Server:[YourServer] /sc_reset:[YourDomain]

NLTest may be from the resource kit though...hopefully you already have it...
Avatar of wilfrieds
wilfrieds

ASKER

I used the NLTest as suggested, but it gave me an error_nosuchdomain, which was weird because there definitely is a domain.  I did notice the NLTest belongs to the NT4 resource kit and not the W2K resource kit (which I had installed already, I had to download and install the NT4 one for this too).  Maybe that was the reason for the error.
Anyway, I was critically running out of time and decided to manually delete the computer accounts and create them again on the clients.  Took me a couple of hours to run from one computer to the next, but it worked.
After PC number 6 or so I started to wonder that there must be an easier way to create computer accounts, without having to implement SMS.  Any idea for that one?
This is straight from the MS Technet:

http://www.microsoft.com/technet/community/scriptcenter/compmgmt/scrcm06.mspx

Create a Computer Account

Description

Creates and enables a computer account in Active Directory, which must be used by an Administrator when adding a workstation to the domain.

Script Code

=============

strComputer = "atl-pro-001"
Const ADS_UF_PASSWD_NOTREQD            = &h0020
Const ADS_UF_WORKSTATION_TRUST_ACCOUNT = &h1000
Set objRootDSE = GetObject("LDAP://rootDSE")
Set objContainer = GetObject("LDAP://cn=Computers," & _
                             objRootDSE.Get("defaultNamingContext"))
Set objComputer = objContainer.Create("Computer", "cn=" & strComputer)
objComputer.Put "sAMAccountName", strComputer & "$"
objComputer.Put "userAccountControl", _
                ADS_UF_PASSWD_NOTREQD Or ADS_UF_WORKSTATION_TRUST_ACCOUNT
objComputer.SetInfo

===============

Sorry we did not get this to you earlier..

FE
ASKER CERTIFIED SOLUTION
Avatar of Fatal_Exception
Fatal_Exception
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks.
I can use that one for later.
The funny thing is all this happened because I wanted to implement system disk mirrorring to avoid having to do this kind of thing again!  ; - (
Mirrorring works fine now, so now I am waiting until the mirror breaks and I will have to start asking questions again .... ; - )
In that case, we will be hanging around, ready and willing to help..  

G'luck..!!

FE
And thank..!!

FE