Re: RRAS doesn't R
- From: "Briscobar" <youcant@xxxxxxxxxxxxxx>
- Date: Fri, 13 Oct 2006 11:26:56 -0400
"OT-MAN" <OTM> wrote in message
news:OHNPnjt7GHA.2384@xxxxxxxxxxxxxxxxxxxxxxx
What about
--servername(local)
---IP Routing:
----General -- Interfacename(192.168.0.29)
Properties -- Enable IP router manager
Yeah, that's set too.
try to dial in, from the same office, from cleint computer or testing pc.
Yeah, I did that, as I mentioned in my original post. I can dial in alright.
I'm authenticated, registered on the network, all that happy horsesh1t. But
I CAN see the entire network from here because, well, I'm ON that network.
This is not a good test of whether the VPN is working. It's only a test as
to whether RAS is working, not Routing. The routing from a client PC in the
office is done the way routing would be done if it weren't connected to the
VPN. Basically, what happens when you dial in from the same subnet is you
just get another IP address on a different subnet. Thus, I can see both
subnets.
Dialing in from off-site allows me to only see the 192.168.0.x subnet. The
problem is, there's nothing really there except VPN clients. I need them to
be able to see the 192.168.1.x subnet, which is where all our servers,
printers, etc live.
.
- References:
- OT: RRAS doesn't R
- From: Briscobar
- Re: RRAS doesn't R
- From: Briscobar
- Re: RRAS doesn't R
- From: Briscobar
- OT: RRAS doesn't R
- Prev by Date: Re: OT: Deer McBob
- 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
|
