Hi,
I cannot find a good article to point you to, however the RRAS help files
are very good in this regard. Under RRAS and help, search on "deploying
demand dial routing". This will give you all the information you need to
set this up.
For PPTP connections you will need to open up TCP 1723 and Protocol 47
(GRE). For L2TP you will need UDP 500 (or 4500 for NAT-T) and protocol 50
and 51.
When you setup the dialup accounts for the Demand Dial connections, I would
suggest using local accounts instead of Domain accounts. This just
simplifies the connections (unless these are DCs. It is best not to use
DCs for RRAS servers if possible). Enable these accounts for Dial in.
The demand dial names and accounts also need to be the same. So if you
have a demand dial with the name CityVPN1 on server 1, you need to use the
account CityVPN1 to connect with on the demand dial connection from server
2 (so server1 will have an account for CityVPN1).. This allows the server
to make the connections so routing works correctly:
Server1
DOD name: CityVPN1 username: CityVPN2 (server1 has account named CityVPN1)
Server2
DOD name: CityVPN2 username: CityVPN1 (server2 has account named CityVPN2)
Also, you will need to setup Static routes on each side so that traffic
from one subnet can be passed across the VPN. If segment 1 is 192.168.1.x
then you need a route on the VPN server on segment 2 that says for traffic
bound to 192.168.1.x, use the demand dial interface. (both sides need
these routes)
This can be setup in RRAS under static routes. Just choose to add a new
static route.
Thank you,
Matthew Fresoli
Microsoft Network Support
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Similar Threads
Linear Mode
