Better late than never.
If you wish to balance the load on your domain controllers you should go to
DNS console and
change priority for appropriate SRV record. There is no point deleting SRV
records because Netlogon will re-register them.
More info:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/di...ib/dsbc
Toni
"JT" <JT.TakeThisOut@discussions.microsoft.com> wrote in message
news:3A71182F-8CB4-444D-91F5-ECBB193DE8E4@microsoft.com...
> Hi all,
>
> We have an issue where the only DC in a particular site is experiencing
> replication issues and needs to be demoted/promoted again. Unfortunately,
> this work cannot be undertaken for a few weeks, and in the meantime some
> users are experiencing logon issues - all users are pointed to DNS servers
> in
> a different site, but they experience intermittent logon failures due to
> the
> domain not being available.
>
> My first question is how do I ensure that no users look to the failing DC
> for authentication?
> My second is, can I remove all SRV records to the failing server, or will
> this open an almighty can of worms? (The DC is also a file server so it
> can't simply be switched off).
>
> Any help you can provide will be greatly appreciated.
>
> Cheers,
>
> John