Two DC's but when main goes down no one can log on.

[dany2010]

Hi,

 

We just installed and promoted a second server to a DC replica using the standard dcpromo.

 

We were hoping that we could take down the original server with everyone still being able to log on but we get the message saying no login servers available when we do.

 

Is this normal without seizing the FsMO roles?

 

Thanks.

[SYNACK]

You need to make sure it is a global catalogue server in AD sites and services so that it also holds a replica of the directory, it also needs to be running DNS if it is not and may need to be running DHCP if that is only handled by the other server so that stations can still get addresses.

[dany2010]

Thanks for the quick reply.

 

Yep, its a global catalogue and DNS but i have just thought.

The workstations will only have the original server in there DNS network settings. Does the login process use DNS only? Could this be the problem?

 

Cant try it out until Wed but would like to go in with hopefully a answer.

[SYNACK]

Yes the clients need both as DNS servers, you can push this out in DHCP by having both. Login like many other things is very deeply tied into DNS, it is the core of any AD network.

[bart21]

Yes the clients will use DNs to find a dc to log into.

 

Without DNs working the machine will use the login server cached in its DNS cache.

[dany2010]

That may have solved it then.

 

We run static IP's so will create a script that i can roll out. WOuld like DHCP but the manager says no,

 

Will give it a go tommorow.

 

Many thanks

Edited June 5, 2012 by dany2010

[DarrenM]

Hey Dany, It may be cleaner to use group policy for that. There are settings for it, quick web search will show.