Re: Windows 2003 VPN Default Gateway Issues

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

.

Relevant Pages

  • RE: SBS2003 Std | No ISA | XP Client Cisco VPN connection problems
    ... I understand that one internal client behind ... SBS can not establish VPN to external VPN server. ... On the Connection Type page, click Broadband, and then click Next. ... Internet access and the local network check box, ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with Permissions
    ... And SBS server is only take ... the role of an internal server. ... they are all configured to connected to internal network. ... g. Run the Configure Email and Internet Connection Wizard on SBS server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot ping network clients
    ... configured so the server is happy. ... I want to clarify the network setup. ... by using "Set Up Client Computer". ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
Loading