Quite a perplexing one.
I have a Windows 8.1 machine (completely up to date on patches from Windows update) that I want to join a Windows Server 2008 (R1) domain. When I log into the local administrator account and choose to join the domain (i.e. "WinDom"), it says "Welcome to WinDom" but then follows this up with a pause and then an error message "Changing the Primary Domain DNS name of this computer to "" failed."
Ignoring this, I reboot and am able to log in to WinDOM\User which then creates a local account on the Windows 8 computer and a computer object in Active Directory on Server 2008 (so it is seeing the domain initially). However after logging in, it stops seeing the domain properly and subsequent reboots results in "There are currently no logon servers available" locking me out of the account on the machine that was just created.
If I run "nltest /dsgetdc:WinDom" on the Win 8 machine when it's not on the domain, it reports it can see the domain controller fine. If I join the domain and then run the same command it cannot see the domain controller anymore.
Whether it is on the domain or not, I can use nslookup to find the domain controller server and ping it so I don't think it's a general DNS issue. The DNS/DHCP server is not the same as the Windows Domain Controller server and both the server and the Windows8 machine have the IP set as it's preferred DNS server.
We have another dozen Windows 7 machines all working happily on the domain, it's just the Windows 8.1 machine I'm having trouble with
Anyone have any ideas what's going wrong here?
Thanks in advance for any light anyone can shed on this.
I'm going to try patching the Windows Server 2008 this weekend to see if anything there adds support/fixes for Windows 8 machines joining the domain, but I'm going around in circles at the moment.