Windows 2003 VPN Default Gateway Issues
- From: "tomger221" <tomger221@xxxxxxxxxxx>
- Date: 1 Oct 2006 05:10:30 -0700
To All:
Iv'e recently set up a Windows 2003 VPN server, client connecting are
XP.
I can connect with no problem but when I attempt to map or access any
other network resources it is no good. I cant even map to a share on
the Server I connect to, I get "Network not found". I can ping this
server by name and IP once connected. I have configured the VPN server
to assign an IP address based on a pool of 10 private addresses. Server
is multi-homed with cards pointing to 2 different subnets, one public,
one private.
What I did notice is that when I run an IPCONFIG /all the Ip and DNS
are good but the Gateway is the static IP that is assigned to the VPN
client by the Server. Since the server and the clients are on different
IP ranges do I need to create a static route for the clients? If not
what determines the how the gateway is assigned to the connecting
clients? As an aside, I also played with the "Use default gateway on
remote network", didnt make a difference if it was on or off as far as
connecting to shares.
Any help is appreciated.
Thanks,
Tom
.
- Follow-Ups:
- Re: Windows 2003 VPN Default Gateway Issues
- From: Robert L [MVP - Networking]
- Re: Windows 2003 VPN Default Gateway Issues
- Prev by Date: Re: How do I connect my PC and laptop using a crossover cable?
- Next by Date: Re: DHCP issue when changing subnets
- Previous by thread: Re: How do I connect my PC and laptop using a crossover cable?
- Next by thread: Re: Windows 2003 VPN Default Gateway Issues
- Index(es):
Relevant Pages
|