I'm the one person here that is not supposed to have issues like this. Windows Cannot Access Network Share You Do Not Have Permission I thought for sure I had changed something with my super power GPO. after that i compared the two folders (properties - sharing, security) and found out that it was a "security" issue.

Map network share dialog has a way to enter new credentials.

The fastest way to access the Network and Sharing Center is to right-click the network symbol in the systray. Now I can see all of the six drives I've shared out on S4 (my desktop). I had to see DomainName\UserName as the fully-qualified user name to get what was going on. Windows 10 Cannot Access Error Code 0x80004005 the "LanmanWorkstation" entry had been chopped in half.

Maybe a month from now you try and again and stuff just falls into place. This behavior can be changed through a Local Security Policy. This all worked but it had to be the same as the account you are currently logged in on 10 (I was switching from a local account and a MS account click site I have tried without success to find where Win 7 is getting the notion that I, the administrator, don't have the credentials to access one of my PCs.

Accessing a share on an XP desktop "suddenly" stopped working. Thanks! My System Specs You need to have JavaScript enabled so that you can use this ... Typing share location in address bar would time out in 90 seconds.

Thank you very much!! One did but has started not working this week...no updates have been run. One computer (let's call it PC-A) is a winxp professional SP2... It was indeed my router.

Also can the the Win 8 access any Win 10 shared folders? This is not just a file sharing/computer to computer access problem, I am not able to access anything on my NAS (Network Attached Storage Device) either. My hobby is blogging about computer problems solutions and I'm also doing some social work by helping my website's guest users to fix their problem by deskdecode's technical support page. Thank you very much!

I changed these both to RDPNP,LanmanWorkstation and I was then able to connect without a problem. Could this be a bug in Windows 7? This is not it. the solution was to add back clients for microsoft network which for some reason was not there in the wireless adapter properties.

OK possible workaround - On my sister's laptop I map one of the drives on my deskpop (S4) and now I can create a folder on that drive. So i tried different things, even recreating the machine in an other virtual network at windows azure and even downloaded the .vhd and created a vm on the local hyper-v-host. They are both using Windows 7 and on the Homegroup.I thought I had everything set correctly, but I can't seem to get that user to have access.