Re: Remote Branch DC wont Replicate With Corporate DC



Jwolfer wrote:
> SITUATION
> -------------
> We have 2 sites. A corporate site, and a small branch site. Our
> corporate site is a Windows 2003 server (PDC) and a windows 2000
> server (BDC). At our branch site, I have a windows 2000 server (BDC)
> running, in case of a network down issue between the 2 offices. For
> the most part, it seems to work flawlessly. If the link goes down,
> the users there can still access that server, and keep working.
>
> I have noticed one problem though. If the link goes down, then the
> only system those clients can see is the server, they cannot access
> any shares on any of the client PC's... namely shared printers.
>
> It seems to me that this is a DNS issue, so upon further review, I
> found this on my Win2K3 server.
>
> Davinci is our win2k3 PDC
> CSServer is our backup DC at branch office
>
> =========================================================
<snipped>

Can you *please* provide:

1. An ipconfig /all of your DC in corporate and the DC in the remote site
2. The AD DNS Domain name
3. The zone name in DNS and if updates are set to allow updates
4. Any firewall rules blocking access between locations
5. Is traffic traversing a NAT device?
6. Does the _msdcs zone exist on all DNS servers?
7. Do you have Sites defined in AD?

That will greatly help diagnosing this.

btw- There the PDC and BDC reference is a legacy reference only related to
NT4. There is a "PDC Emulator Role that runs on a DC to emulate a PDC for
some of the NT4 PDC's functionality in backward level client support,
besides time sync and a couple other functions, but that has no bearing on
AD. All AD DCs are replicas and multi-masters. Data can be changed on any of
them and will get replicated to other DCs, unlike NT4, where the only place
anything can be changed was on the PDC.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Paramount: What's up with taking Enterprise off the air??
Infinite Diversities in Infinite Combinations.
=================================


.



Relevant Pages

  • Re: NT to 2003 domain upgrade - DNS related question
    ... running W2K3 on it as an upgrade, it will automatically assume the "PDC ... promo the new box to PDC, and THEN do the in-place upgrade. ... The problem is that you're going to lose your DNS server if you do plan B ...
    (microsoft.public.windows.server.migration)
  • RE: Changing Roles and DNS
    ... I would like to transfer the PDC role to one of the new domain ... In fact MS recommends to host as many FSMOs as possible on DCs with the ... Is it advisable to make the PDC the primary DNS server for the domain? ...
    (microsoft.public.windows.server.active_directory)
  • Re: duplication when setup.... ie: acme.acme.com
    ... > server 2 if you like and commented about siezing the ... > going to continue to call it PDC. ... > doing a DNS lookup from acme.acme.com? ...
    (microsoft.public.win2000.dns)
  • Re: Problems locating PDC on win2k3 server
    ... win2000 DNS server; ... I see SRV records for -_ldap under pdc; ... How to Configure OEx for Internet News ...
    (microsoft.public.windows.server.active_directory)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)