Mapping Drives on VPN - Access denied

Hi I have been using a VPN to access my Home Server for 2 / 3 years without thinking of technical issues; it just worked!

On this visit when I initiate a connection I can see the mapped drives and can open them but I can no longer have full control of a folder (ie copy to/from create a new document) - I keep on getting "Access Denied" or similar reports. I tried taking ownership of the folder but that is not permitted.

My Local (overseas) computer is in the same Workgroup and obviously when connected it has an IP to match the remote sub-net. I have the same user name on both the local and the remote machine but when I try to add \\local_machine\user_name to list in the Security tab I can't (obviously enough).

The mystery is why it has worked seamlessly for 2 / 3 years and why now (there has been no change on the Home Server - I know everyone says this) it has this behaviour.

Anyone who has experienced the same issue and has a solution please let me know! Thanks Jean

What folders are you connecting to are they new ones not used before? If you try and connect to folders in user profile you will get access denied even as admin on local PC. It will be down to NTFS permissions on folders and it needs setting from local PC

Hi Samuria Thanks for reply. They are exactly the same folders as before the scheme is straightforward the HP Home Server back at base has a number of shares one being "Data" under which there are several folders, Accounts, Documents, Excel, and so on... At base we have a home group with defined permissions for each share and normally when overseas I log in locally as Jean (Administrator on local machine) with exactly the same password as I have when back at base. I start the VPN, Map a drive, Enter my credentials "Jean" "Password" and that's that but this time I can list files and I can copy files locally (ie to my local machine) but if I want to save a file back on the remote server I can't.

You need to check ntfs permissions if you create a new folder or file or alter one it can then become the property of that user a access denied to others are they all win7 pcs as windows 10 on last updat has removed homegroup and reverted back to workgroup. One problem with homegroup is it needs ipv6 which may not be passed by some routers as its not generally used yet

HP Home Server runs Home Server 2011 - all the logs are clear no incidents logged. The local machine runs Win 7 Ultimate. No new folders have been created. WorkGroup was so much more elegant... My router is IPV6 ready but I continue to use IPV4 which is straightforward and simple. But anyway why should this have changed since the last time I was remote (in Nov 2017)? Then I could copy to/from the folders as if I were on the local network.

Samuria: the answer has been to RDP into the HP Home server and restart it. All now works without any other changes having been made. Sometimes the simple answer - often overlooked - is the answer.