Slow when 1 dc down?!

[mike86]

Hi All,

 

I've been asked to investigate this issue & hoping you can shed some light on it if you've come across it before.

 

We had a server down for maintenance & have noticed that our clients became really slow even when opening up local software, testing this with paint, snipping tool etc. Only thing I can think of that is causing this is that their are hidden drives mapped to this server, is this something that could cause the issue? Once the server came back up everything was ok! The server is used to share drives to the students & as a secondary DC.

 

Any ideas?

 

Thanks

 

M

[ZeroHour]

DNS timeout possibly, was it your primary/first dns server in your list on clients?

[mike86]

thanks, it's set as secondary DNS

[ZeroHour]

What is set on your DC's network connections?

[mike86]

set the same across the board.

[ZeroHour]

set the same across the board.

 

If I recall I thought MS recommended each DC be set to their ip as primary ip and secondary as the alternative DC.

[Geoff]

That's never been true in a multi DC domain, in fact you could break W2k DCs (of which I hope you don't have any) if you did that.

 

DNS Server becomes an island when a domain controller points to itself for the _msdcs.ForestDnsName domain

 

If you have two or more operation AD integrated DNS servers you should set a DC to use another DCs DNS as the primary. Your DC will boot much faster and with less errors that way. Microsoft fixed the 'island' problem in W2k3.

Edited October 29, 2014 by Geoff