Re: RRAS demand dial between two sites

See KB292822. Basically the same sort of problem that you had with a
multihomed DC in NT4 (ie two or more IP addresses associated with the
server's Netbios name). With dynamic dns you now can see a similar problem
with DNS names.

"Bry" <bryanhobson@xxxxxxxxx> wrote in message
news:1177915242.007859.258370@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 30 Apr, 01:02, "Bill Grant" <not.available@online> wrote:
This is theoretically possible, but I would not recommend it. Running
a
DC as a remote access server can cause all sorts of problems. You would
be
well advised to forget using the WIndows servers as VPN routers and
upgrading your ADSL routers to support VPN. The routing is simpler if the
VPN router is also the default gateway for the local LAN. If you make the
Windows servers the VPN routers you need extra routing on each LAN to get
the private traffic for the "other" LAN to the VPN router.

You certainly do not have two connections for a site to site VPN.
Here
is how it works with RRAS routers. Each site has a static route to the
"other" site linked to its demand-dial interface. These are stored in the
registry until the demand-dial interface becomes active. When the
connection
is established it must bind to the demand-dial interface on the answering
router. You do this by using the name of the demand-dial interface on the
answering router as the username. When the connection is up and both dd
interfaces bind to the VPN connection you have a route on each router to
the
"other" site through the VPN link. (Note that the two subnets will still
not
route if the VPN server is not the default gateway of the LAN).

"Bry" <bryanhob...@xxxxxxxxx> wrote in message

news:1177877487.804893.60230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I have two remote sites, both with ADSL connections.

Each site hosts a domain controller for the domain.
SiteA has subnet 192.168.0.0/24
SiteB has subnet 192.168.1.0/24
Each network has a DSL router with the address 192.168.x.1
The IP address of the servers is 192.168.x.2

e.g.

SiteA Server
192.168.0.2
|
SiteA Router
192.168.0.1
|
Internet
|
SiteB Router
192.168.1.1
|
SiteB Server
192.168.1.2

Port forwarding is enabled on each router to allow PPTP, and VPN
connections can be successfully established to either site.

What I'm trying to do is to enable seamless routing between the two
networks for all clients, without having to purchase any more
hardware.

I'd like to configure this using RRAS, but I'm not 100% sure how to do
it. I've attempted to do this using a demand dial interface to form a
VPN connection to the other site (and the same in the opposite
direction), but having two VPN connections (one from SiteA to SiteB
and another from SiteB to SiteA) doesn't seem right. Should I be doing
this with a single VPN connection, that can be used in both
directions? If so, how can I accomplish this?

For info, both servers are domain controllers for the same domain
(SiteA is SBS2003, SiteB is Server 2003 Std), each server is placed in
separate site, and the DCs can replicate, but this isn't very reliable
due to the link problems I'm seeing.

Kind regards,
Bryan

Many thanks for the info. Could I ask what kind of problems might
surface using a DC as a RRAS server?



.

Relevant Pages

  • RE: VPN Error 800
    ... On the Small Business Server 2003-based server, click To Do List in the ... Click Next, click Enable Remote Access, click to select the VPN Access ... go to the client and establish the VPN connection to the ... please help me gather the ISA info and ISA log: ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Advice...do I need a purchased static ip address on the external interface?
    ... >> Server then that server must have a been assigned a purchased static IP ... >> if I was to try and use Windows 2000 SBS as the server for the VPN, ... >> If I used a router instead then the router would have this purchased IP ... > supports dynamic dns, then users connect to the dynamic dns name and ...
    (comp.dcom.vpn)
  • RE: Enabling VPN Remote Access using SBS 2003 standard with ISA 2004
    ... SBS Server, the inbound VPN connection no longer worked. ... Configure the VPN connection on the client and do a VPN test. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN via Wireless Broadband
    ... I don't know how timing-sensitive VPN connections are. ... Browsing to the User shared folder from the client doesn't work. ... shares on the server and SYSVOL is there and one can use Windows ... How to configure a VPN connection to your corporate network in Windows XP ...
    (microsoft.public.windows.server.sbs)
  • Re: Certifcate reset error - Need for mobile device connect
    ... What I am trying to accopmlish is to have my SBS exchange server synch wireless with a Motorola Q phone. ... Manager packet from the SBS 2003 server to recreate the VPN connection. ...
    (microsoft.public.windows.server.sbs)
Loading