A
Aaron Seet
What would be the least administratively painful way to satisfy this
scenario?
First office has an existing AD domain and running servers in the LAN:
1. File/Print
2. IIS/SQL
3. DC (of course)
Connection is via ADSL, with an Aztech modem/router that supports static
IPoA.
A second office is coming up, and clients in the LAN there will need to
access resources in the first office LAN as seamlessly as possible, and
users all belong to this same domain (thus user authentication is same no
matter where).
The first thought was to setup a new DC (and new site) at the second office.
Actually that's all simple except how the 2 DCs + client machines on each
isolated LAN can ever bridge a connection through the Internet and act as
though they're on the same LAN.
What are your opinions on this?
scenario?
First office has an existing AD domain and running servers in the LAN:
1. File/Print
2. IIS/SQL
3. DC (of course)
Connection is via ADSL, with an Aztech modem/router that supports static
IPoA.
A second office is coming up, and clients in the LAN there will need to
access resources in the first office LAN as seamlessly as possible, and
users all belong to this same domain (thus user authentication is same no
matter where).
The first thought was to setup a new DC (and new site) at the second office.
Actually that's all simple except how the 2 DCs + client machines on each
isolated LAN can ever bridge a connection through the Internet and act as
though they're on the same LAN.
What are your opinions on this?