This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
My problem has the same error described in this thread but it is behaving defferent:
https://social.technet.microsoft.com/Forums/windows/en-US/ab9340b5-846f-4b75-921d-8442c8540bb6/problem-with-accessing-a-windows-share?forum=w7itprosecurity
I am using a laptop and a PC (both Windows 10). I think the problem is on the PC but I'm not entirely sure
I have shared a folder on the PC and when accessing it from the laptop it gives the following error:
"\\servername\sharename is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
A device attached to the system is not functioning"
It gives that error only once. Every subsequent time I try to access the share it asks for me to enter network credentials.
My credentials don't work... Both devices are of course signed into the same Microsoft account with administrator privileges. The folders being shared are owned by and shared with that Microsoft account in the Advanced Sharing/Advanced Security menus with full access. File Sharing/Network Discovery are turned on for both computers on private networks ect..
The only way to see the error again is to unshare and reshare the shared folder on the PC, again it will show the error only once, and then send me into the credential loop.
The PC is able to access the share on the laptop no problem.
The PC has been accessible from the laptop before, I am not sure what happened
The thread above recommended trying the access the shares using ip (\xxx.xxx.x.xx\share) so i tried that and had the same problem but again it worked fine accessing shares on the laptop from the PC
Things I have tried:
• Reinstalling network adapter drivers on the PC
run winver
Desktop:
Laptop:
I run a script that I found to enable gpedit.msc on the Home version. It also enables secpol.msc that is enabled by default on the Pro version. That's the difference. Don't worry about it.
can you link me to this script?
You can run it if you want.
https://www.itechtics.com/enable-secpol-msc/
Right now I'm thinking that problem is with the PIN. Have you changed your account's password at any time while either of these systems were up and running? I don't use a PIN so I'm not sure how network logons functions. I've always used a password.
You could also try launching credential manager in control panel and enter the pc name and your id+pswd and see if that can connect to the other pc. Click on "Add a Windows credential". (Not web credential)
You could also try launching credential manager and enter the pc name and your id+pswd and see if that can connect to the other pc
I have already verified that my correct Microsoft account information is stored in windows credential manager on both computers, although if that were the problem the incorrect information would be on //thinktank
screenshot from thinktank:
the ip above is the local ip for \glassbox
Instead of your email address try using the local account name. And then check the security eventlog on Glassbox if you can't connect. There has to be some authentication failure event.
I changed my MS password to something that is short enough that I can actually type it and removed the pin from both computers
I switched the username for \glassbox in windows credentials manager on \thinktank to Brodie and tried to connect from \thinktank. same error as before
am I looking in the right place?
every single event is called audit success
event viewer on \glassbox after attempting to connect
If it's not too much of a pain, I think that somewhat of a reset would be in order. I'd suggest removing those entries from credential manager. Then root both pc's. Logon using a password to both. See if you can connect.
You may need to run that script to enable failure logging for logon events.
In the Settings app, look for Additional Troubleshooters. Run both the Incoming Connections and Shared Folders troubleshooters. See if they detect anything.
