Re: AD Replication over SonicWall site-to-site VPN



Hi
Can you ping the server

By default, Active Directory replication over RPC (Remote Procedure Calls)
takes place dynamically over an available port via the RPC Endpoint Mapper
(RPCSS) using port 135;
Application protocol Protocol Ports
Global Catalog Server TCP 3269
Global Catalog Server TCP 3268
LDAP Server TCP 389
LDAP Server UDP 389
LDAP SSL TCP 636
LDAP SSL UDP 636
IPsec ISAKMP UDP 500
NAT-T UDP 4500
RPC TCP 135
RPC randomly allocated high TCP ports TCP 1024 - 65536
832017 Service overview and network port requirements for the Windows
Server system
http://support.microsoft.com/default.aspx?scid=kb;EN-US;832017
224196 Restricting Active Directory replication traffic to a specific port
http://support.microsoft.com/default.aspx?scid=kb;EN-US;224196

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Markb1118" <Markb1118@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FFC24485-6D01-405F-91FF-3C4A8A6CB3F9@xxxxxxxxxxxxxxxx
Boy did I get in a hurry. The most frequent reference is to the RPC
Server
being unavailable.

"Markb1118" wrote:

Had a working multi-site Windows 2003 domain. Replication was happening
cleanly and on schedule. In June, implemented a SonicWall 2040 at the
home
office and SonicWall TZ-170s at the remote offices and connected via
site-to-site VPN. Now, the domain controllers will not replicate. The
most
frequent reference is to I have been through all of the available
troubleshooting steps and nothing has resolved the problem.

I did not do the firewall configuration but it seems pretty straight
forward. I have seen for myself that there are no rules in place
restricting
any traffic on VPN to VPN connections.

Any advice, help, even the smallest tid-bit would be appreciated. Thanks
in
advance.


.



Relevant Pages

  • Re: Intersite Replication problem
    ... As for RPC The default value for the RPC Replication Timeout registry ... from Windows 2000 to Windows Server 2003, the value for the RPC Replication ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: Intersite Replication problem
    ... I followed Antony's DNS advise and I seens to be working. ... To perform the replication I've schedule a task on the W3K server to dial ... As for RPC The default value for the RPC Replication Timeout registry ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: ipfw and nmap
    ... > even be correct but I have a bsd box that is simply providing me SSH ... add allow tcp from any to me 22 setup in via fxp0 keep-state ... Note too that there is nothing to prevent port scanners simply setting ... the 'SYN' flag in the probe packets they send to your server. ...
    (freebsd-questions)
  • Re: SBS 2003 and Outlook RPC over HTTP issues
    ... Port 80 IS NOT NEEDED. ... Something else is still wrong with your server. ... I just remembered that I somehow hosed OWA about four years ago, ... that port 443 and port 80 must be open to use RPC over HTTP. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL 2008 Remoteverbindung
    ... Ich kann mich jetzt auf den Server verbinden & es funktioniert wirklich ... die Grundsätzliche Verbindung funktioniert jetzt. ... Bei IPALL bist du schon richtig, den Port must du aber bei 'TCP Port' ...
    (microsoft.public.de.sqlserver)