I have recenty upgraded our Windows 2000 domain to 2003 using the adprep commands (both forest prep and domain prep) on the 2000 server - this all went through correctly and everything is working as expected. Now however whenever I add a 2003R2 server and do a DCPromo the server is promoted to a DC correctly and then reboots as you would expect. The server then seems to be working correctly and no errors appear in the event logs, if however I then reboot the server again it just won't startup correctly and connecte to the network - this has now happened to 3 different 2003R2 boxes. When the server starts you can ping the server and get a response, but the server hangs on "preparing network connections" and will then stop responding to a ping and eventually get "a service failed to start". I think the error is realted to MSDTC as I get an error in the event log "MS DTC could not correctly process a DC Promotion/Demotion event. MSDTC will continue to function and will use the existing security settings. Any help would be grately appriciated. Huw

Please follow this KB article and keep us updated http://support.microsoft.com/kb/923977http://www.virmansec.com/blogs/skhairuddin

thanks for the prompt response. I've had a look at that article previously but the problem I have is when I goto the components services "My Computer" has a red downward pointing arrow on it and when looking at the properties screen I only have one tab "COM security".

see if you have a distributed transaction cordinator service started or right click on the computer and clisck start msdtchttp://www.virmansec.com/blogs/skhairuddin

the service started automatically, I have a variety of other services that are set to automatic that won't start: Background Intelligent, file Replication Service, Help and Support, IPSEC Service, System Event Notification, Task scheduler Other services which are set to manual ie Network connections won't start and when you try get an error re dependant services. If you try and look at what services it's depnedant on you get an "Win32: Access is denied" error

I have resolved this issue. The problem appears to have been connected to the RPC server which was being started by the Network Service user. Changing this to Local System has resolved the problem.