question

DavidC-8135 avatar image
0 Votes"
DavidC-8135 asked FanFan-MSFT commented

Domaing Servers - Client Machine Leaving and Rejoining issue

Domain is set up with two machines for redundancy but the Primary Machine failed (currently running on Redundant)

          Domain Machine - Windows Server 2008 R2 Standard

          Client Machine - Windows 7 Professional

Primary Domain Server crashed and tombstoned. Attempted to bring it back online but it caused issues with the Redundant Domain Server. Had to take it offline.

Client Machine used to be a part of the domain but our software had issues with the domain users. Attempted to leave and rejoin the domain but it would error and state "An Active Directory Domain Controller for the Domain xxxxx could not be contacted".

Domain name is "stratus.local"

Performed the following
1. Verified the DNS server address on network setting is correct.
2. Able to ping the Domain IP address
3. Performed cmd->ipconfig /flushdns
4. Able to remote into the Domain Server from the Client Machine.

Is there something I'm missing?



windows-dhcp-dns
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
Welcome to share your current situation if there are any updates.
Please feel free to let us know if you need further assistance.
 
Best Regards,

0 Votes 0 ·

Hi,
I am checking to see if the problem has been resolved.
If there's anything you'd like to know, don't hesitate to ask.
Best Regards,

0 Votes 0 ·
DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick converted comment to answer

Primary Domain Server crashed and tombstoned

The only solution here is to disjoin / rejoin domain, or better yet rebuild the broken one. May also involve seizing roles to a healthy domain controller as first step.
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

An Active Directory Domain Controller for the Domain xxxxx could not be contacted

I'd check the problematic one has the address of a healthy domain controller listed for DNS and no others such as router or public DNS

If you still need help then please run;

Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\problemworkstation.txt

then put unzipped text files up on OneDrive and share a link.


--please don't forget to Accept as answer if the reply is helpful--













5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FanFan-MSFT avatar image
0 Votes"
FanFan-MSFT answered

Hi,
Welcome to ask here!
It is suggested to fix the DC issues firstly.

If the PDC can't be brought to domain correctly, you can size the role to the good one. Following link for your reference:
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

Then you can consider demote it by make a metadata cleanup.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

Last, you can try to remove and rejoin the client.


Best Regards,

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

Any progress or updates?

--please don't forget to Accept as answer if the reply is helpful--




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.