paddygreenhood
asked on
Cannot rejoin domain
Whilst dealing with a situation where a Windows Server running 2008 standard lost power and subsequently some workstations could not rejoin the domain, I took the step with a particular workstation (XPSP3) of leaving domain and joining a workgroup, rebooting as local administrator and rejoining the domain.
Upon attempting to rejoin the domain the user and password comes up immediately, but credentials fail with the following message: "the following error occurred attempting to join the domain domainname. Cannot complete the function.
Ethernet adapter on WS is set to dynamic, have completed a winsock/tcp repair to flush out any issues on the workstation side.
I have been able to rejoin another client to the domain and have been able to get that WS back on exchange (although I had to set up a new outlook profile and found that data flow from the exchange store to the workstation quite slow) and have had issues with behavior of shares ( I have another question listed regarding this), so I know I can join another device to the domain.
Can anyone with experience in this please advise...
thanks in advance...
Upon attempting to rejoin the domain the user and password comes up immediately, but credentials fail with the following message: "the following error occurred attempting to join the domain domainname. Cannot complete the function.
Ethernet adapter on WS is set to dynamic, have completed a winsock/tcp repair to flush out any issues on the workstation side.
I have been able to rejoin another client to the domain and have been able to get that WS back on exchange (although I had to set up a new outlook profile and found that data flow from the exchange store to the workstation quite slow) and have had issues with behavior of shares ( I have another question listed regarding this), so I know I can join another device to the domain.
Can anyone with experience in this please advise...
thanks in advance...
Are there any clues in the clients event log other than the error message you have posted ?
Instead of using the netbios or simple domain name, use the FQDN.
e.g. instead of "domainname", use "domainname.co.uk".
Can you ping the DC's from the client? If DNS is incorrect and it can't reach a DC, that could also be a cause of failure.
You don't specifically state if the Server that lost power was one of your DC's?
Ensure that your DHCP settings are not still issuing that server's address as a DNS server.
e.g. instead of "domainname", use "domainname.co.uk".
Can you ping the DC's from the client? If DNS is incorrect and it can't reach a DC, that could also be a cause of failure.
You don't specifically state if the Server that lost power was one of your DC's?
Ensure that your DHCP settings are not still issuing that server's address as a DNS server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for prompting me to run dcdiag, got me on the path to discovering that dhcp service, although up, was frozen in some way. Restarting that got me under way.