[pptp-server] IP Question.

[Tim Brody]

Hi,

Unless you change the routing on the mobile computer, they'll be trying to
access your network through the NIC card, rather than the PPTP interface
(which is entirely logical ...). By changing the IP addy of the NIC you're
changing the routing table so the machine no longer associates your internal
network with the NIC, but with PPTP.

I *think* the easiest solution for you would be to set up a DHCP server,
which would give you a distinction between when your VPN users are connected
directly and indirectly to your network.

Set up a DHCP on your network with your proper internal IP addresses
(10.1.1.x && 10.1.1.1), with a short TTL (say 10 minutes). When your users
are out-and-about their lease will expire, stopping them routing through
their NIC, and will start routing through the PPTP instead.

All the best,
Tim.

----- Original Message -----
From: "Matthew Gavin" <mattgav at tempo.com.au>
To: "PPTPD User Group (E-mail)" <pptp-server at lists.schulte.org>
Sent: Thursday, October 18, 2001 8:42 AM
Subject: [pptp-server] IP Question.


> Hi all,
>
> I have a small problem with Windows clients (Laptops) who connect to both
> our Corporate LAN and our VPN (Not at the same time).
>
> For VPN access, ie: when they are remote to the LAN... There is no
problems
> authenticating and then connecting, but IP Traffic does not occur to or
from
> the internal network unless the user changes the Static IP Address
assigned
> to their NIC to anything but the LAN subnet (10.1.1.0)...
>
> ie: 10.1.1.234 to 10.0.0.234. Same for the gateway 10.1.1.1 to 10.0.0.1.
All
> is fine once they do this!
>
> I have senior managers who get the shits with this every time they need to
> VPN in, and some have given up all together. Has anyone experienced this
or
> do the majority of "your" VPN users always remain as VPN users?
>
> Matt. :)
>
>
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> --- To unsubscribe, go to the url just above this line. --