VPN can ping, but can't access shares

  • Thread starter Thread starter Scott Balmos
  • Start date Start date
S

Scott Balmos

Hi all,

I'm setting up VPN access on a Win2k3 box for a customer. The server has a
192.168.x IP that is 1:1 NAT/firewall mapped to a 216.68.x address. It is
configured to give out 10.x addresses to VPN clients, and routing is
*disabled* (e.g. the customer should only be able to access their box. Other
boxes on the 192.168.x range are other customers).

A PPTP allow rule has been added to the firewall, and connecting to the VPN
succeeds. The customer computer (WinXP Pro) is given a 10.x address, and can
ping the server (at 10.0.0.1). The customer computer has the default gateway
checkbox unchecked, so that they can still connect to the outside Net via
their existing link. However, all attempts to browse shares of the server,
using either net view \\servername *or* net view \\10.0.0.1 both fail with
the infamous System Error 53 (network cannot be found).

Any ideas/suggestions here? I am at a loss. There is no firewall running on
the server itself, no blocking IP filters, etc. Thanks!

--Scott
 
Assuming you can ping 10.0.0.1 and new view \\10.0.0.1 gets system error 53, make sure the file and printer enabled.

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
Hi all,

I'm setting up VPN access on a Win2k3 box for a customer. The server has a
192.168.x IP that is 1:1 NAT/firewall mapped to a 216.68.x address. It is
configured to give out 10.x addresses to VPN clients, and routing is
*disabled* (e.g. the customer should only be able to access their box. Other
boxes on the 192.168.x range are other customers).

A PPTP allow rule has been added to the firewall, and connecting to the VPN
succeeds. The customer computer (WinXP Pro) is given a 10.x address, and can
ping the server (at 10.0.0.1). The customer computer has the default gateway
checkbox unchecked, so that they can still connect to the outside Net via
their existing link. However, all attempts to browse shares of the server,
using either net view \\servername *or* net view \\10.0.0.1 both fail with
the infamous System Error 53 (network cannot be found).

Any ideas/suggestions here? I am at a loss. There is no firewall running on
the server itself, no blocking IP filters, etc. Thanks!

--Scott
 
And now it seems that the client connection is dropped roughly 5 or so
minutes into the session. The VPN connection remains up, the route over the
tunnel is still in the routing table, etc. But there are ping timeouts
occuring. The only fix is to reconnect the VPN tunnel. I don't know if this
helps, or is another issue.

--Scott
 
It could be the MTU issue. These links may help,

VPN slow issues In a case you may need to modify the MTU size and wonder how to determine the optimal MTU for your system. ... www.howtonetworking.com/VPN/mtu4.htm ...
www.chicagotech.net/vpnslow.htm


VPN connection is disconnected after serveral minutes VPN drops the connection. VPN is very slow. To change the MTU Settings, ... Resolution: Set my VPN client MTU to 1400. To modify MTU, please refer to this ...
www.chicagotech.net/VPN/vpn3minutes.htm

How to change mtu However, you may experience a VPN or Internet drop or slow issues with these default MTU settings, especially if you are using DSL line. ...
www.howtonetworking.com/VPN/mtu1.htm


VPN connection issues after Windows 2003 SP1 Resolution: Set my VPN client MTU to 1400. To modify MTU, please refer to this page, How to change MTU settings for PPP or VPN. Related Topics ...
www.howtonetworking.com/casestudy/2003sp1&mtu.htm


Black screen when rdp over vpn Resolution: Use the ping to test and lower MTU. Finally, We reduce MTU from 1500 to 1400 in the SonicWall. Then he can use RDC over VPN. Related Topics ...
www.howtonetworking.com/casestudy/mtu1.htm





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
And now it seems that the client connection is dropped roughly 5 or so
minutes into the session. The VPN connection remains up, the route over the
tunnel is still in the routing table, etc. But there are ping timeouts
occuring. The only fix is to reconnect the VPN tunnel. I don't know if this
helps, or is another issue.

--Scott
 
Back
Top