6 replies
by jfalace Accepted solution
by cg it Accepted solution
the workstations have to VPN into the headquarters network,authenticate, then obtain a local network address. Once they do that, they can then enter the intranet web site address in a browser and connect.
AD replication, even though also accomplished via a VPN connection, isn't related to remote users making a VPN connection. AD Sites and Services handles DC replication traffic over WAN link subnets.
Users on the other hand don't use this method. RRAS controls Remote Access for users. RRAS needs to be setup granting domain users remote access [see user accounts in Active Directory]. Also a rule in RRAS needs to be created allowing the users remote access. The default rule in RRAS is to deny access.
by jfalace Accepted solution
by cg it Accepted solution
and everybody has their own way, however, you have to remember that a domain controller doesn't necessarily take workstation traffic and route it through itself to the internet. Internet Connection Sharing on the server would accomplish this but then your using up server resources when it acts as a router that could be used for other stuff.
If you create a VPN tunnel from the remote site domain controller to the HQ site for the purposes of replication, you don't really want workstations to utilize that tunnel. First, see above about using a server as a router and second, everyone using the tunnel just bogs down traffic.
If you need "assured" AD replication between DCs at specific times, you can create a point to point persistant VPN tunnel solely for AD replication.
Your configuration of setting up seperate VPN connections for each workstation to connect to the HQ office to access the intranet site is probably the best configuration. As long as your perimeter firewall/router will handle all the connections.
by jfalace Accepted solution
by cg it Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending