XP client not connecting to domain
I have an XP client machine that would not connect to the domain this morning. The domain has a single DC. I tried removing it from the domain by assigning it to a workgroup & re-joining the domain. I then tried renaming the computer & then re-joining the domain. I then tried removing the computer account from Active Directory & re-joining the domain. The computer shows up in Active Directory, but the account is disabled. Enabling the account in Active Directory does not get the computer joined to the domain.
Using the network wizard on the client computer gets me the following error message "the specified server cannot perform the requested operation". I am not finding any error in Active Directory on the corresponding server.
Using the network wizard on the client computer gets me the following error message "the specified server cannot perform the requested operation". I am not finding any error in Active Directory on the corresponding server.
motnahp00
Delete the computer account in ADUC. Verify the DNS settings are correct and try rejoining.
From the XP machine, open a command prompt > Start>run>cmd
Type
netsh int ip reset c:\resetlog.txt
Then reboot and try again
Type
netsh int ip reset c:\resetlog.txt
Then reboot and try again
ASKER
I had already tried deleting the computer account in Active Directory, I used removing instead of deleting. DNS is set up to connect automatically, I manually set the IP of the DHCP server & still had no luck.
ASKER
ran the netsh int ip reset c:\resetlog.txt, didn't fix the problem. I'm going to try removing the antivirus & firewall software to see if that is the culprit.
ASKER
Tried setting a static ip on the client, now i'm getting the following error "network path not found".
It seems like it cannot find your DC. Have you tied to ping your DC?
ASKER
I can ping the IP, but not the FQDN.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Logon to the client locally and go to START>>Run>>type in "Services.MSC" and press enter.
Scroll down to the Netlogon Service applet and set that to STARTED and Automatic.
Also, look at this policy setting:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/580.mspx?mfr=true
Scroll down to the Netlogon Service applet and set that to STARTED and Automatic.
Also, look at this policy setting:
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/580.mspx?mfr=true
ASKER
I went into the hosts file, adding the IP & FQDN did the trick. Thanks for the help!
Hi curtis424...
Thanks for letting us know what helped you resolve the issue. ..!!
Thanks for letting us know what helped you resolve the issue. ..!!
Your issues are not over.. You just applied a bandaid to an open wound. The problems you are having with DNS need to be fixed or you will suffer a problem with domain services.
I have never really cared about points. So, Let's just fix the issue correctly.. Take one machine and make it accept a dynamic IP and DNS. Go to the command prompt and type IPconfig /release, then IPconfig /renew. Then, post an IPconfig /all of that client. You probably have an outside server somewhere in the DHCP scope options that's being passed down to the client, or your DHCP scope options isn't configured with your internal DNS servers that host the SRV records for Domain services. That will point your DHCP clients to the wrong place for domain services, like Active Directory. That doesn't work.
I have never really cared about points. So, Let's just fix the issue correctly.. Take one machine and make it accept a dynamic IP and DNS. Go to the command prompt and type IPconfig /release, then IPconfig /renew. Then, post an IPconfig /all of that client. You probably have an outside server somewhere in the DHCP scope options that's being passed down to the client, or your DHCP scope options isn't configured with your internal DNS servers that host the SRV records for Domain services. That will point your DHCP clients to the wrong place for domain services, like Active Directory. That doesn't work.