"MSNews" <(E-Mail Removed)> wrote in message
news:%23E$(E-Mail Removed)...
>I have a VPN to my home office 2003 server(network 192.168.1.0/24) from main
>office(10.1.30.0/24). I can connect and login to my home VPN. but I am
>missing the routing setup. This part I will need a little help with. I know
>when I connect to my vpn I am still on the 10.1.30 net and cant see the
>192.168.1 net. Where do I set this routing up
You don't mess with routing at all.
Remote Access VPN, *by design*, causes the target network you dialed into to be
the only outbound path. The client is supposed to be "cut off" from any local
networks other than the subnet that the Client was originally part of. Remote
Access VPN is meant to be used in such a way that you connect, do what you need
to do, then disconnect,...you aren't supposed to stay connected.
You can, on the Client side, disable "use gateway on remote network" and will
then be able to operate on the local network normally with the VPN
connected,...however the "price to pay" is that you can only communicate over
the VPN with hosts on the remote network that are on the same subnet that you
connected into,...all other subnets on the remote network will be unreachable.
This however, is considered a security risk or security violation from the
remote LAN's perspective.
Site to Site VPN (aka Router to Router VPN) is a completely different type of
VPN.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
Similar Threads
Linear Mode
