Question Locked

DNS Problems in Branch Office Desktops

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have two sites set up for a single Windows 2003 domain. They are connected via Microsoft RAS vpn. I was able to replicate active directory changes sucessfully between the two domain controllers. If I attempt to connect to the intranet website located in the main site from the server on the branch site, it is sucessful, however from member machines on the branch site, I am not able to connect. DNS is set up on the branch site and ip addresses are assigned by the branch office DC, with appropriate DNS address scope option. The network of the main site is 10.0.0.0 and the branch is 192.168.255.0. Forwarders are set up on the branch office DC using the DNS addresses from the ISP. Is there something that I'm missing? Any suggestions are appreciated and thanks in advance.

6 replies

by cg it

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

Dns on the branch office DC will not forward traffic requested by the workstations through the vpn. I have to set up vpn connections on all the workstations in order for them to get to the intranet on the main site. Not sure this makes a difference, but the workstations are domain members. I also read somewhere that you could put a static route in your firewall to forward traffic bound for the main site subnet to the vpn router/dc. I seem to be seeing different schools of thought all over the web. That's why I joined this forum, so that I could get it straight. Thanks for your reply.

by cg it

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

I believe that I would have had to multihome the server on the branch office dc and configure RRAS to forward traffic that way. Instead I decided to configure a tunnel gateway between the two firewalls. This works extremely well as the dc's are replicating and the branch office machines are able to access main site resources. Thanks CG IT for your input. It's greatly appreciated.

by cg it

glad the info helped in whatever way.

This discussion is closed to new replies.