"System Error 53 has occured, The network path was not found"
I connect to my office through a soft VPN which connects just fine. When I connect using the VPN I then run a batch file that connects my mapped drives which has worked great for over a month until now. When I run the batch file I get "System Error 53 has occurred, The network path was not found". It seems as if when i wait a long period of time or restart my computer / the server a few times the batch file run just fine
When the VPN is connected I can ping my office router and servers just fine. I can not get to any files or folders through using \\ip address or \\server name.
Office Servers are running Server 2003 and I am running Vista at my home.
Thanks
When the VPN is connected I can ping my office router and servers just fine. I can not get to any files or folders through using \\ip address or \\server name.
Office Servers are running Server 2003 and I am running Vista at my home.
Thanks
ASKER
No changes in software, I think changes were made with one servers DNS but I am almost sure it was fixed. With the VPN enabled I can pull up my router page in the office from home so I know things are working I just can not get to any network dives.
A few thoughts:
1) (most likely) Flaky VPN connections can often be caused by too high an MTU (Maximum Transmission Unit) size, especially if it is a lower than normal performance connection. In correct MTU value symptoms usually include an ability to connect but either not access shares, or unable to download larger files. It is recommended you change this on the connecting/client computer and when possible, it's local router. The easiest way to change the MTU on the client is using the DrTCP tool:
http://www.dslreports.com/drtcp
As for where to set it, if not using automatic, it has to be 1430 or less for a Windows VPN which uses PPTP if using the basic client (1460 for L2TP). There are ways to test for the optimum size of the MTU such as:
http://www.dslreports.com/faq/5793
However, this is not accurate over a VPN due to additional overhead. The best bet is to set it to 1300, and if it improves the situation, gradually increase it.
A couple of related links:
http://www.dslreports.com/faq/7752
http://www.chicagotech.net/vpnissues/vpndorp1.htm
2) Any chance the local or server end local subnet has changed? They must be different, if not you can usually only connect to the VPN server device (if at all), but no other.
3) Might there be a software firewall enabled on the device to which you are connecting and the file and print sharing exception not enabled?
1) (most likely) Flaky VPN connections can often be caused by too high an MTU (Maximum Transmission Unit) size, especially if it is a lower than normal performance connection. In correct MTU value symptoms usually include an ability to connect but either not access shares, or unable to download larger files. It is recommended you change this on the connecting/client computer and when possible, it's local router. The easiest way to change the MTU on the client is using the DrTCP tool:
http://www.dslreports.com/drtcp
As for where to set it, if not using automatic, it has to be 1430 or less for a Windows VPN which uses PPTP if using the basic client (1460 for L2TP). There are ways to test for the optimum size of the MTU such as:
http://www.dslreports.com/faq/5793
However, this is not accurate over a VPN due to additional overhead. The best bet is to set it to 1300, and if it improves the situation, gradually increase it.
A couple of related links:
http://www.dslreports.com/faq/7752
http://www.chicagotech.net/vpnissues/vpndorp1.htm
2) Any chance the local or server end local subnet has changed? They must be different, if not you can usually only connect to the VPN server device (if at all), but no other.
3) Might there be a software firewall enabled on the device to which you are connecting and the file and print sharing exception not enabled?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Has you OS alwasy been the same, before and after you noticed it was no longer working?