<div>
Set up a site &amp;&nbsp;subnet for each 'office' and then AD will get on with the replication.<br />
<br />
See:<br />
<br />
Managing Sites <br />
<a href="http://technet.microsoft.com/en-us/library/bb727051.aspx" rel="ugc">http://technet.microsoft.com/en-us/library/bb727051.aspx</a>
</div>


Set up a site & subnet for each 'office' and then AD will get on with the replication.

See:

Managing Sites
http://technet.microsoft.com/en-us/library/bb727051.aspx [http://technet.microsoft.com/en-us/library/bb727051.aspx]

<div>
AD sites and services will NOT help with replication. &nbsp;Replication is not dependent on AD sites and services. &nbsp;<br />
AD sites and services is used so each site that is defined has a domain controller there - the local clients will use this local DC instead of crossing the WAN for AD requests.<br />
Again replication is not dependent on this.<br />

</div>


AD sites and services will NOT help with replication.  Replication is not dependent on AD sites and services.  
AD sites and services is used so each site that is defined has a domain controller there - the local clients will use this local DC instead of crossing the WAN for AD requests.
Again replication is not dependent on this.


<div>
<div class="content wysiwyg-content">
I would like to implement replication between Windows 2003 servers in different subnets. Server A is in head office with ip range 192.168.1.0, and server B is in the branch office with ip range 192.168.2.0. I would like server B to handle DNS and DHCP requests for it's ip range, while replicating data to server A. We currently do have a VPN connection between branches which is handled at the firewall level. What would be the best practice to follow ? 
</div>
</div>


I would like to implement replication between Windows 2003 servers in different subnets. Server A is in head office with ip range 192.168.1.0, and server B is in the branch office with ip range 192.168.2.0. I would like server B to handle DNS and DHCP requests for it's ip range, while replicating data to server A. We currently do have a VPN connection between branches which is handled at the firewall level. What would be the best practice to follow ? 

Windows 2003 Servers in different subnets

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.