The issue: Need to get a WAN setup at the branch office.
Preparation: Built a w2k server as an AD member server with secondary DNS, DHCP, WINS configurations--replication completed successfully.
The main office DHCP is using 192.168.0 (255.255.255.0) subnet. Branch office DHCP is using 192.168.2 (255.255.255.0) subnet.
Main office has a functioning VPN configuration and static internet IP. Branch office has a dynamic internet IP.
The problem: new branch server will successfully connect to internet and main office VPN through a demand dial connection, but will not route client PC traffic to the internet or to the main office connection.
Branch server has the following static routes configured: (based on TechNet VPN example)
Interface: (internet facing connection)
IP: (Main office static internet IP)
netmask: 255.255.255.255
Gateway: 0.0.0.0
metric: 1
Interface: (demand dial interface)
IP: 192.168.0.0
netmask: 255.255.255.0
metric: 1
Technet examples:
http://technet.microsoft.com/en-us/library/bb742569.aspx
http://technet.microsoft.com/en-us/library/bb742572.aspx
note: both sides of the connection follow the connection pattern of (RRAS server) => (firewall) => (internet)
I need a sanity check here. I enabled NAT to solve the internet end of things, but the branch PCs still need to start a local VPN connection.