Windows 2003 Servers: Moving FSMO Roles and new DC problems

[demonic]

Hey,

Here is the sceanario:-

2 DC Controllers. One Primary and One Backup. Both running Windows 2003 Standard Edition R2.

Move the FSMO roles from the primary to the backup, as detailed here : http://www.petri.co.il/transferring_fsmo_roles.htm

Turn off the Primary.

Reboot the Backup.

On startup of the Backup, I get this message:-

Logon Message
--------------------

The System cannot log you on due to the following error :

The specified domain either does not exist or coult not be contacted.

Please try again or consult your system administrator.

--------------------

Some points to consider.

- Replication was working fine.
- Roles transferred successfully and running on the backup server. Checked using here : http://www.petri.co.il/determining_fsmo_role_holders.htm
- The DNS Server on the backup, is active directory enabled and also points to the backup server for the primary DNS and the secondary DNS points to the primary server.
- If I leave it 5 minutes, the server starts up fine. I have the LSASRV error, SPNEGO with Event ID 40960. The security system deteced an authentication error for the server LDAP/DC20. The failure code from authentication protocol Kerberos : "There are currently no logon servers available to service the logon request."

Lastly.

- If I have the Primary Server running, I get no such issues.

---------------

I know this is a DNS issue.

DNS is starting at 18:22

LsaSrv is starting at 18:17, which of course is looking for DNS entries of which to start.

Other than telling Netlogon.exe to depend on DNS to start, is there anything else I can do?

I am trying to simulate a complete failure with my Primary Server and I want to make sure, I am able to transfer roles successfully and have a Backup Server capable of servicing the network.

Thanks

 

[Maintank]

Did you transfer the roles while both boxes were up? Or did you seize control of the roles when the primary ad controller was down?

I believe there is more to it than simply siezing control of the roles in the even of a failed controller. You may have to dig through the DNS and make sure everything it pointing to the right controller. I'd search microsofts site about transferring roles.

One thing to make sure is the backup that has the new roles is a global catalog server.
http://technet2.microsoft.com/Windo...bf98-4a80-8718-dd80dc1071fd1033.mspx?mfr=true

If not you probably will have a hard time logging on.

Microsofts guide to transferring roles.
http://technet2.microsoft.com/Windo...5da4f9f2-7f90-417a-9d11-5ee1db75bfb61033.mspx

 

[demonic]

Thanks for answering, this is quite old now

I had to finish the step by removing the old server. Then there wasnt any issues.