Re: RRAS doesn't R
- From: "LRM" <Fskspam@xxxxxxxxxxxxx>
- Date: Fri, 13 Oct 2006 12:50:01 -0500
"Briscobar" <youcant@xxxxxxxxxxxxxx> wrote in message
news:exm$4Ju7GHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
OK, breakthrough. After messing around with gateways and whatnot, I'm ableWhat flavor OS is this and are you using pptp/l2tp?
to dial in, get an IP on the 192.168.0.x subnet, and ping the VPN server
at 192.168.0.29. What's new is that I can now ping 192.168.1.254, which is
the IP address of the same server's other NIC.
Of course, to do this, I had to use the default gateway of the remote
network, which I really wanted to avoid so that my users could keep their
internet connection alive while they VPN'ed in, but that's a minor detail
that I'll work out later.
Now, as for moving beyond Dataman (the VPN server)....it's like the server
is set to not allow clients to access the entire network. I've been
through the whole thing (or so I think, but I'm obviously missing
something), and can't find any setting that might do this.
Anyone care to list for me where I'd go about changing this?
Thanks everyone, especially OT-MAN. Never thought I'd say that. Wow!
Ken
.
- Follow-Ups:
- Re: RRAS doesn't R
- From: Briscobar
- Re: RRAS doesn't R
- References:
- OT: RRAS doesn't R
- From: Briscobar
- Re: RRAS doesn't R
- From: Briscobar
- OT: RRAS doesn't R
- Prev by Date: Re: RRAS doesn't R
- Next by Date: Re: RRAS doesn't R
- Previous by thread: Re: RRAS doesn't R
- Next by thread: Re: RRAS doesn't R
- Index(es):
Relevant Pages
|