Windows Server 2008 services fail after promote to domain controller
This has happend to me twice on different machines with clean installs now.. so I feel there is something going on with my domain. I have a Windows 2000 domain which I am adding a 2008 DC to. It's currently running native mode, so no pre 2000's are on the network, it also has an additional 2000 domain joined in a trust. Ran all the pre reqs.. adprep /domainprep,forestprep,gpolicy etc.. so the 2008 with SP1 promotes just fine to the domain. After promotion, i start to get services failing, such as DHCP, network location awareness, network listing service, and a few others. I have fixed these by adding system\local service back to the registry permissions, and it works fine untill the machine locks up and needs to be restart, thats when it unapplies the fix. Also, the machine after a day or two, will become unresponsive like its gone to sleep, but the hardware is on and has not shut down, it just does not respond to pings on keyboard/mouse. Need urgent help as this machine holds the file shares so we have to reboot it several times.. In the mean time, im going to move the file shares to a different server.
January 25th, 2011 2:10pm

Hello, please use the support tools and provide the following output files: ipconfig /all >c:\ipconfig.txt dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)] dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045) As the output will become large, DON'T post them into the thread, please use Windows Sky Drive(with open access!) and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 4:07pm

Here are the files http://cid-4cc5a413bb5e846e.office.live.com/browse.aspx/core?Bsrc=EMSHOO&Bpub=SN.Notifications Thanks!
January 25th, 2011 6:01pm

Hello, sorry that i was not that specific, the ipconfig /all belongs of course to the old and the new DC. 192.168.11.4 is shown in dnslint output as DNS server but the ipconfig from CORE shows 192.168.11.3 and 192.168.11.5? So what is true for the domain DNS server? CORE is in JRNL_WRAP_ERROR state. http://support.microsoft.com/kb/290762/Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 6:18pm

updated the skydrive with the central.txt which is the old dc..
January 27th, 2011 4:26pm

in the ipconfig for core, it should have been 127.0.0.1 and 192.168.11.5(old dc) i think i was playing around and made some quick changes before i had posted the files. 192.168.11.8 is another trust server but is running shared dns, so we can change core/central to point to anything we want
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2011 4:36pm

Hello, Central is multihomed which is not recommended as it result in multiple problems, more details in the great article from Ace Fekay: http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx So remove RRAS and cleanup DNS zones and server properties in the DNS management console, then run ipconfig /flushdns ipconfig /registerdns and restart the netlogon service or reboot. Please post again the corrected dnslint output.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
January 27th, 2011 4:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics