I have a small network of around 10 workstations connected to a Windows 2008R2 Domain Controller (serves as AD, DNS and DHCP). The workstations are primarily Windows 7, but new Win10 workstations are being added. This network does not have access to internet nor am I allowed to screen cap error logs and send them out. So any error messages I am retyping in. Additionally, I don't have much trained experience with Windows Administration, so any help is appreciated.
I have a a problem with both Win7 and 10 workstations not being able to reconnect to the Domain Controller after a reboot. The workstations were a clean install of the OS and joined (sucessfully) to the domain. I reboot the machine after the initial joining and sucessfully re-login to the machine using a Domain Administrator account. If the computer is rebooted after this point (no matter how later) the machine will log in a local cached copy of the user (in this case the Domain Admin), display a message about the local cached login, but no connection to the domain server will happen. Using ping to attempt to reach the server or switch gives a "General Failure" message.
The local logs give several errors and warnings around that time:
Security->Audit Failure - Sensitive Priviledge Use
System->GPO Failures (ID 1129) - Lack of connectivity to DC
System->DNS Warning (8033) - Failed to register host resource records to network adapter
System->Distributed COM Error (10016) Permission do not grant Local Activation for COM server application (various GUID) User NT_AUTHORITY\LOCAL_SERVICE SID (S-1-5-19)
The only way I can reconnect the workstation back to the domain is to go into the Network Adapter Properties->IPv4 Properties and:
- Switch to Obtain IP Address Automatically
- Ok to apply and Close Adapter properties
- Reopen the adapter and IPv4 properties
- Re-enter the static IP for the workstation and apply
The network adapter will reconnect to the domain sucessfully and all logouts/logins after that are sucessful. However the issue will occur if the computer is rebooted for any reason.
I have tried:
- Unchecking the "Register this connections address in DNS" in the Network Adapter->IPv4 Properties->Advanced
- Adding the Server to the A record in DNS (https://www.experts-exchange.com/questions/29003228/DNS-Issue-The-system-failed-to-register-host-A-or-AAAA-resource-records-RRs-for-network-adapter-with-settings.html)
- ipconfig /flushdns (https://social.technet.microsoft.com/Forums/windows/en-US/0100acd8-b7c8-416a-bd62-af92c92b259f/dns-client-server-event-8027-and-8033?forum=w8itprogeneral)
- I have looked through Group Policies, as this seems to occur after domain policies are applied, but this has not been exhaustive