• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3951
  • Last Modified:

Server 2008 stuck on "Please wait for the group policy client" when using itself as DNS

Hi,

During my migration from SBS 2003 to 2 new servers 2008 R2 i encounter the problem that one of the new servers 2008 R2 (X64) hangs on "Please wait for the group policy client"
The problem is when the server is using itself as the primary DNS server (local ip sepcified) in the tcp/ip settings.So when i add as secondary DNS the SBS2003 for example.there is no problem and the server logs on quickly.
on the server 2008 tcp/ip V4 and 6 are both enabled,and configured to registrate itself in DNS.
I specified a static entry in the tcp/ipV6 settings with help of the SixXS tool.
I believe that  DNS database was missing some records for the server but after the ipconfig /registerdns i see NS,A and AAA records now.
0
antwerp2007
Asked:
antwerp2007
  • 5
1 Solution
 
antwerp2007Author Commented:
the DNS server on the server 2008 with the problem listens  on both the ipV4 and ipV6 interfaces.
Is it a good idee to uncheck the ipV6 interface on the listen on interface tab from DNS server?
0
 
antwerp2007Author Commented:
Meanwhile i deselected the ipV6 interfrace from the DNS listener tab and the issue is still there
0
 
antwerp2007Author Commented:
some message in dcdiag ;

  The processing of Group Policy failed because of lack of network con
nectivity to a domain controller. This may be a transient condition. A success m
essage would be generated once the machine gets connected to the domain controll
er and Group Policy has succesfully processed. If you do not see a success messa
ge for several hours, then contact your administrator.
         An error event occurred.  EventID: 0xC000042B
0
 
antwerp2007Author Commented:
it is a dns problem on the server 2008 itself, ipV6 records are registered and seems to be the problem
I'll delete them or reinstall DNS withthe option to ipV6 not let itself registered in DNS
0
 
antwerp2007Author Commented:
reinstalling DNS was not the solution, i had to demote also the DC role.
After promoting again the server everything was working
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now