Slow Logon if old server is offline

[Jorge Moutinho]

Hi everybody.
Here is the situation:
I had an AD domain with two servers: SEAFIRE and CORSAIR.
SEAFIRE was the only server in the domain for some time, and then i've
installed the brand new machine, promoted it to DC, and assigned it
all FSMO roles.
Later i've installed another server, HURRICANE.
Then I ran DCPROMO on SEAFIRE and demoted it from DC.
Later I set up CORSAIR and HURRICANE as DNS servers for the domain.
The problem is:
If SEAFIRE is online, logons on client machines are instantaneous, but
if I take it offline, client machines take about 30 sec. to logon.
What am I missing?

Any help is apreciated, and please ask if you need a more detailed
explanation of the problem.

Thanks in advance.

Jorge

P.S. - DNS is working weel, and so is replication, but if you think
that's the problem please tell me which tests should I run to see if
that's true.

 

[Rick Barker]

Hello Jorge,
I assume, at this point, that no one is pointing to SEAFIRE for DNS. All
domain members should be pointing to either Corsair or Hurricane as their
preferred DNS server...and the other as their secondary (i.e. no one is
pointing to Seafire for either primary or secondary DNS..including Corsair
or Hurricane).
And neither Corsair or Hurricane are Forwarding to Seafire.

Run 'set l' at command prompt on a client machine to see it's login server.
Do this under both scenarios (i.e. Seafire online and offline) to see
there's any difference that might clue us in.

Also, use Network Monitor to get a trace of the client booting up (while
Seafire is online and offline). You should be able to tell, from looking
at the trace, what's causing the delay.

Thanks....
Rick Barker
Microsoft Product Support