New
#11
Thanks Berton for your input, but it shows up in neither for me
Thanks Berton for your input, but it shows up in neither for me
this question might sound crazy, but are you using password to login?
There's no such thing as a crazy question, but yeh I am using a password. Have deleted all users off my NAS, and shares, and added only the one user now (same username and password as my windows accound).
I seem to have boiled it down to only this error now: the local security authority contains an internal inconsistency
I was having the same problem as you, but was not using a password. I read somewhere that Windows 10 would restrict access to NAS if it deemed that the PC was itself insecure. I ended up creating a password (not an account) and I was able to access my NAS. Once I deleted the password to share files remained on and fully accessible. Go figure.
What on Earth is going on? I've just managed to map it.
For anyone else experiencing this problem, it was solved after rebooting the NAS drive. I believe that some of my users and shares on my NAS went a little crazy so I deleted, re-added and re-booted. Just took me a day to realise I should re-boot it (although I did this just the other day)!
Thanks all for your input anyways. I hope this lasts!
Joe
I should also add, the mount was successful using the following net use command, it still doesn't show up in the map network hard drive wizard:
net use z: \\Path\to\share\folder /user:USERNAME
Try forcing Windows to negotiate using legacy SMB 1.0. It corrected some issues I had with accessing QNAP NAS. To do this, type "gpedit.msc" (without quotes") in search, right click on the gpedit.msc search result and select Run As Administrator. Under Computer Configuration | Windows Settings | Security Settings | Local Policies | Security Options. Look for Network Security:LAN Manager Authentication Level. Double click on it and select "Send LM & NTLM - use NTLMv2 session security if negotiated" in the dropdown box. Exit gpedit.msc, reboot the computer to implement the policy and then try your NAs again.
Thanks sciencegeek for the response, but all is running now. I don't have a lot of confidence so I will try that if this problem reoccurs.