Re: SBS2003 Prem and branch office W2003 server: replication errors

Many thanks. I had already confirmed DNS registration for the Internal NIC
as I have been caught on this before. Problem still the same.

I suspect DNS. I can from the branch ping successfully the SB2003 server by
name and fqdn. I cannot ping branch from SBS2003.

question: Should I have only the internal address of each server in DNS?
I do have references to the VPN Site to site link IP addresses.

"Karl Middleton" <nospam@xxxxxxxxxx> wrote in message
news:ON$5xIyDGHA.740@xxxxxxxxxxxxxxxxxxxxxxx
> The usual reason for replication errors in the scenario you detailed is
> DNS problems. And these are usually caused by having ALL NICS (internal,
> external, and VPN) registering themselves with DNS. The first time you
> DCPromo does a replication but doesn't depend on DNS hence why your users
> etc transferred over OK. The subsequent replications are failing (take a
> look under Directory Service and File Replication Service in the event log
> and you will find the errors there).
>
> Only ONE interface (the internal network) on the SBS box and the branch
> office box should have the "register in DNS" box checked under network
> properties. All others (external NICS, VPN NICS) should not. If you leave
> them all ticked, you will find that your DNS server will have 3 IP
> addresses registered for your Windows servers. AD does not like multihomed
> systems.
>
> I find that once the system is messed up from a DNS point of view you
> often have to dcpromo demote the branch office server and start again.
>
> Traps and tips for young players:
> - over a VPN makes using the head office DNS server for both sites
> unreliable. Load DNS and DHCP on the branch office server as well as the
> head office server. Set the branch office scope to point at the branch
> office server for DNS resolution.
> - DCPromo will default the branch office server to be in the same AD site
> as the head office server. Unless you have beaucoup bandwidth on your
> internet connection, create a second AD site and put your branch office
> into it. Makes managing login scripts, GPO, etc much easier and limits the
> replication to once every 3 hours instead of every 15 minutes. If your
> internet link is flaky, consider using an SMTP transport instead of IP.
> - Once you have your AD replication working and the branch office reliably
> online, consider using DFS. It is great for ensuring that stuff like
> ClientApps is the same at both sites. I also use it to sync User Shared
> Folders so that travelling folk can log on at the alternative site and
> access a local copy of their files instead of dragging them across the
> VPN. Set the replication time at less than the time it takes for the plane
> ride home to ensure their files will be waiting for them on arrival back
> home.
> - Companyweb and cached Exchange come into their own on a branch office
> via VPN scenario. I set up my customers with the branch office getting a
> lot of corporate stuff off the Companyweb and their email uses the cache
> to cope with the low bandwidth.
>
> Good luck
> Karl from Oz
>
>
>
> "NetTransplant" <flbritton@xxxxxxx> wrote in message
> news:aGWtf.30$tl.11@xxxxxxxxxxx
>> So I have a new w2003 server at the branch office. Connection between the
>> two points are stable and seem perfect.
>>
>> I promoted w2003 to domain controller and integrated dns with active
>> directory over a vpn site to site link. All seemed well and I did have
>> all my users etc on the branch machine.
>>
>> Replication seems to have stopped working. I added a new computer using
>> active directory users and computers on branch server and it will not
>> appear on the sbs2003.
>>
>> both commands below done on sbs2003 server:
>>
>> repadmin /showrepl branch.my.local shows replications successful to first
>> site.
>>
>> repadmin /showrepl sbs.my.local shows failed with rpc unavailable error
>> 1722. (0x6ba)
>>
>> What should I next be looking for?
>>
>> The branch server is installed in the lab across the internet from the
>> sbs2003 and is over the internet. It moves Weds to remote site.
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Satellite Branch Office Woes
    ... point of a "satellite branch office" is to provide Directory and all other ... services from the central site, "eliminating the need for costly server ... DNS and DHCP. ... If no server at the site, can you get a T1 to the site instead of a DSL? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cannot connect to RWW from home PC
    ... DNS stuff says your mail server is responding with reply that is not MS ... When we setup this new SBS2003 setup we installed without ISA as it does ... not seeing any problems anywhere regards internet or email - we also run ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: resolve incorrect IP from RRA server.
    ... dynamic address, 10.5.101.123 from DHCP server. ... This is because the addtional DNS records that get registered cause major problems with AD functionality, especially the additional IPs registered by RRAS. ... However, if you choose to keep RRAS on the DC, then you have to force DNS to only register the internal static interface, and no others. ... If it is the internet gateway, it is recommended to purchase an inexpensive, or cable/DLS router, or even better, a Cisco or similar firewall to perform the task, which if it is compromised by an internet attacker remotely, can further compromise the rest of the internal network. ...
    (microsoft.public.windows.server.dns)