asked on

Drive Mapping over VPN - System Error 53 and RPC error 1726

I am stumped. I have a Windows Server 2012 R2 machine communicating with a Windows 7 workstation over a VPN. There is one mapped drive referred to as "G" drive.

the PC can see the G drive if I change it's IP address, Net View command works perfectly, however within 1 to 3 days, the drive mapping still shows, but the drive cannot be accessed. Net View then returns an error 1726. Change the IP again and it works again.

I have tried changing the NIC, and have wiped and reloaded the system, same issue. Putting another PC in that spot seemed to resolve the issue, but I would like to repair this one if possible.

John

When this happens to me (not frequently), Persistence is often at the root of the issue. Try this:

Set up a script for the mapping:

NET USE G: /Delete
NET USE G: \\server\folder

Try this and see if the drive works properly now.

CEORACE

ASKER

Sorry John, I wish it was so easy. Once it decides not to work, no amount of mapping, whether GUI, scripted, FQDN, or IP address makes it work.

Yet, the moment you change the IP, it is up and running again for 24 to 72 hours approx.

SOLUTION

John

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

CEORACE

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial