Re: Windows 2003 VPN Default Gateway Issues
- From: "Robert L [MVP - Networking]" <noreply@xxxxxxxxxxx>
- Date: Mon, 2 Oct 2006 09:27:04 -0500
make sure no firewall blocks the file sharing and make you have enable sharing. On the remote computer, do net share and net view \\localIP. Post back with the result.
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"tomger221" <tomger221@xxxxxxxxxxx> wrote in message news:1159780665.991137.196700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Also when I attempt the \\Net view ServerIP command on the server I'm
connected to I get
System error 53 has occurred.
The network path was not found.
I can ping the server by name and IP when connected.
Bill Grant wrote:
> As Bob said, the default gateway on the client is not the problem. The
> default gateway will always be the "received" IP address. What that really
> means is that the default gateway for the client is the VPN connection,
> which is what you want it to be.
> It will only change if you clear the "Use default gateway.." check box,
> which I wouldn't recommend. The default setting is what you need.
>
> The client and the server are not in different subnets. If you click on
> the connection icon on the client and look at the "details" tab, you will
> see that the client and server both have IP addresses from your address
> pool. If you can ping the server, your VPN connection is working. If you
> can't see shares, it is probably a permission issue.
>
> The credentials used by the remote client are the ones from its
> original logon, not the ones used to set up the VPN connection. To log in
> using the credentials you enter at connection time, you have to use the
> "login using a dialup connection" option in the login dialog box, not just
> set up a VPN connection from an already logged-in computer.
>
> "Robert L [MVP - Networking]" <noreply@xxxxxxxxxxx> wrote in message
> news:eWfZkUW5GHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
> If you can ping the server or remote resources, the route is not issue here.
> What do you receive if using net view \\serverIP?
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "tomger221" <tomger221@xxxxxxxxxxx> wrote in message
> news:1159704630.777039.310470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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: tomger221
- Re: Windows 2003 VPN Default Gateway Issues
- References:
- Windows 2003 VPN Default Gateway Issues
- From: tomger221
- Re: Windows 2003 VPN Default Gateway Issues
- From: Robert L [MVP - Networking]
- Re: Windows 2003 VPN Default Gateway Issues
- From: Bill Grant
- Re: Windows 2003 VPN Default Gateway Issues
- From: tomger221
- Windows 2003 VPN Default Gateway Issues
- Prev by Date: Re: Backup SYSVOL causing errors
- Next by Date: Re: Windows 2003 VPN Default Gateway Issues
- Previous by thread: Re: Windows 2003 VPN Default Gateway Issues
- Next by thread: Re: Windows 2003 VPN Default Gateway Issues
- Index(es):
Relevant Pages
|
Loading