RE: hosts not using alternate DC's

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: John Reijnders (Reijnders_at_discussions.microsoft.com)
Date: 01/12/05 

Date: Wed, 12 Jan 2005 07:45:06 -0800

Hi Jack,

You should check your DNS whether or not "failover" records (ex.
_kerberos.tcp.SiteName. and _sites.dc._msdcs.DnsDomainName) are present.

These enable a client to locate a domain controller that is running the
Windows Server 2003 implementation of the Kerberos KDC service for the domain
that is named DnsDomainName and that is also in the site named SiteName. All
Windows Server 2003–based domain controllers that are running the KDC service
register this SRV record.

Cheers!
John Reijnders

"jay mack" wrote:

> i am running a 2003 native domain with 1 dc at each site and 4 sites. i am
> replicating from one main dc to the dc at each of the other sites. there is a
> gc on every server. last week the main dc went off the network due to a
> switch reboot. this was only down 5 minutes but the webservers at each site
> could not authenticate with the shopcart server causing our website to go
> down. the website runs under a domain account and sql server uses SSPI to
> check authentication. why would the loss of the main dc cause this outage. is
> it possible that the the dc's at each of the other sites would not accept
> authentications at this time? the shopcart is at the site that had the dc
> unavailable, wouldn't it have gone to a dc at another site if its dc was not
> available. i have since gone in and configured replication to auto discover
> the dc's yet the main dc that went down is the only dc to add automatic
> replication partners. i have a direct connection between all sites, i would
> think a connection would be auto generated. any help would be appreciated
> especially in configuring a domain that will not fail with the loss of a
> single dc. thanks

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... DNS server has updated its own host records. ... If this DNS server's Active Directory replication partners do not have the ...
    (microsoft.public.windows.server.active_directory)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... The attempt to establish a replication link for the following writable ... DNS server has updated its own host records. ...
    (microsoft.public.windows.server.active_directory)