New Win8 client cannot log on to WinServer2008 domain

Question

I have a server running Windows Server 2008 hosting a domain with a small number of client PCs running various versions of Windows up to Windows 7. A router provides access to the internet as well as DNS and pseudo-static IP address assignment by DHCP (based
on MAC address). This setup has been working perfectly for several years and still does work on all existing PCs.
However, I have just bought a laptop running Windows 8.1 Professional (Update 1). I installed the
Windows 8 update on the server. When I first logged into the new Win8 laptop as a domain user, it took the expected long time to load the roaming profile but then gave the error:
The Group Policy Client service failed the sign-in.
The universal unique identifier (UUID) type is not supported
Despite that, everything seemed OK including a full local copy of the roaming profile, until I logged out and then tried to log back in.
If I log back in as the same domain user, the roaming profile doesn't load and I eventually see "User Profile Service: There was a problem with your roaming profile. You've been signed in with your previously saved local profile. Please see the
event log for details or contact your administrator".
If I try to log in as another domain user, I immediately see "There are currently no logon servers available to service the logon request" and I can't log in.
I've tried pinging between the machines and everything is OK, including DNS. The server does have a working DNS server but it is redundant since DNS is handled by the router. I've read elsewhere that DNS could be the cause but everything seems OK with DNS.
Any suggestions would be greatly appreciated.

Answer 1

Active Directory uses DNS as its domain controller location mechanism and leverages the namespace design of DNS in the design of Active Directory domain names. As a result, DNS is positioned within the discoverability and logical structure components of
Active Directory technology components.
And if you are using the routers DNS, then your computers won't find Active Directory easily and they will take long time.
Read the following link to know more how DNS support for Active Directory works:
http://technet.microsoft.com/en-us/library/cc759550(v=ws.10).aspx
So make sure that your client is directed to use your internal DNS server in order to let your computers function well.
If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer". This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY
suggestion in a test environment before implementing!