Replication isse with SBS 2003 and additional W2K3 server on remote site

HELP!

I am puzzled since I cannot solve the following situation:

I have two sites. Site A has subnet 192.168.27.0/24 and a SBS2003 SP1 server
(BASE) and current WindowsUpdate patch level. No additional patches after
SP1 have been installed. The server has one network card. (used to have two)

Site B has subnet 192.168.1.0/24 and a Windows 2003 SP1 server (HOME) again
with the most current security patch level, which is an additional domain
controller in the SBS domain.

The two sites used to be connected via a VPN tunnel from a VPN router in
Site B, that connected to the SBS server in Site A, which used to be the VPN
endpoint.
Replication was working without any know issues.

The router in site B died and I bought two DLINK 824VUP devices that are
capable of creating a VPN tunnel, which is up and running. Unfortunately I
have now problems with replication and other services now.

My eventlog is now filling with NTDS KCC 1311, 1865, 1566 events on the SBS
server. After rebooting I also had a couple of NTDS replication 2092 events
(among others). On Site B is get "AutoEnrollment" errors with event ID 13
and cannot even register a certificate manually. DCDIAG will complain about
the KnowsOfRoleHolders (even before the 2092 event).

PortQry.exe \\base -e 135 show that the RPC mapper is working. What
absolutely strikes me is the fact that changes are replicated from the SBS
DC to the W2K3 DC - but not vice versa.

Another strange effect is that I can use RDP to connect to the server on
Site B (from Site A), if I use a NON domain member. Terminal Services will
start if you do the same on a domain member, but no login screen will show
up and after about a minutes the connection resets from the blank screen....

Outlook from Site B to SBS2003 Exchange is no longer working. I have the
feeling that something blocks proper RPC communication to the SBS 2003
server. When I switch to the DLink routers, I removed a network card from
the SBS server and had the WizChain thing run again. Although I cannot rule
out the Dlink routers completely yet, I have the feeling that this is a SBS
2003 issue.

Any ideas or hints are highly appriciated.

Thanks in advance.

Tim Bosinius









.

Relevant Pages

  • 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: W2K3 to SBS2K3 Giving Problems..?
    ... we need to make the SBS ... DNS pointing to the Windows server 2003. ... Microsoft CSS Online Newsgroup Support ... I started the replication ...
    (microsoft.public.windows.server.sbs)
  • Re: Setting up SBS 2003 and Windows Server 2003, same domain, 2 sites..
    ... Generally speaking, when checking the replication status for a specifiedDC, ... 327644 How to configure licensing on an additional Windows server in an SBS ...
    (microsoft.public.windows.server.sbs)
  • RE: server/connectcomputer from remote offices
    ... I have a replica w2k3 std server config'd as a dc in location B ... I have a number of client workstations in Location B ... We can connect the workstations in Location B to the sbs domain with no ... I have enabled replication of the clients share ...
    (microsoft.public.windows.server.sbs)
  • Re: Replication and DFS on SBS2003 R2 network
    ... You mention a Terminal Server, so I really don't understand why you would want to open files "over the WAN". ... I can't give you a lot more light on whether DFS-R will be a part of the next version of SBS ... that participates in a replication group with the remote site file server. ...
    (microsoft.public.windows.server.sbs)