Main dc wont logon until dc 2 is on

[rogerpatel]

Hi, need some help after a migration.

Problem, The main DC (DNS, WINS, DHCP, ALL 5 FMSO, GC) Wont login unitl the second dc is on (this to is DNS, WINS, DHCP,GC ,no FMSO roles.


The domain was 2 Windows 2000 Domain controlers, as the hardware was around 4 years old we replaced both servers with new HP ML350g4 servers, now running Windows 2003r2sp1.

DC1
Windows 2003 r2 sp1
DNS, dhcp, wins gc, all fmso roles
ip = 192.168.10.10
dns 1 =192.168.10.10
dns 2 =192.168.10.11
wins 1 =192.168.10.10

DC2
Windows 2003 r2 sp1
DNS, dhcp, wins gc, No fmso roles
ip = 192.168.10.11
dns 1 =192.168.10.11
dns 2 =192.168.10.10
wins 1 =192.168.10.10

When we upgraded the domain from 2000 to 2003 our steps were as follows :

Add the two new servers to the 2000 Domain as members.
Run Domain and forestprep from cd2 on the R2 CD.
Run DCPromo from both servers and add them as additioanl DC's.
Install DNS on bot new Servers
Point all Servers and PC's to the new DC1
Move all roles to new DC1
Make both new DC's GC Servers
Remove GC from old DC's
Power off old DC's and leave domain working for 1 week, no problems reported.
Power back up old 2000 Dcs and demote both servers to standard member computers.

Now, the domain is fully working and no pc;s have any problems, however yesterday i was carrying out some server duties and needed to power off all Servers, so i shut down all servers and then after an hour i powered up the new DC1, the server booted and i entered my login details and it sat in the "Preparing Network Connections" for around 20 mins, i then powered up the DC2 and noticed that dc 1 logged in and all is now fine. I test this all again and it happens every time, dc2 must be on for dc1 to log in fully.

Hope somone can assist.

Thanks

 

[msworld]

any erros if using netdiag and dcdiag? Also any errors in the event viewer?

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

 

[markdmac]

I have seen this before.

First verify that you don't have APC software running on these machines. If so you may just need to update the APC software as there was a problem with an expired certificate that caused this kind of problem.

Refer to

http://support.microsoft.com/?kbid=905716&SD=tech

The other time I have seen this was with respect to some permissions being messed up. Though not specific for this problem the following KB lists the rights needed to resolve the issue I had.

http://support.microsoft.com/kb/888791/en-us

Specifically as I recall you may need to set the rights for
* Manage auditing and security log
* Take ownership of files or other objects

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript