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.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
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.
CEORACEAuthor Commented:
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.
JohnBusiness Consultant (Owner)Commented:
Try the following:

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the computer

See if the DNS Flush helps.
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

CEORACEAuthor Commented:
John, In resetting the DHCP, DNS the IP changed and everything is working.  I know it will fail again in a few days if it follows its usual course and will try your solution then.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
JohnBusiness Consultant (Owner)Commented:
I suggested a solution in http:#a40820881  and CEORACE accepted my solution in http:#a40821036 . Accordingly my solution should be accepted.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.