Cannot connect to file server: "Access is Denied"

I have been using Ubiquiti's Unifi line of networking equipment for a few years. Our router went out and I had to put in a temporary (another brand) while I waited for a new one to come in. Since that time, all Windows 10 computers that I use (Microsoft login) can no longer connect to the server to map network drives. I always get an "Access Denied" message. However, if I connect via a Windows 7 computer, everything works fine. (Maybe all Windows 10 machines updated to a new patch at coincidentally the same time!?) I've since replaced the temporary router with a new USG and STILL have the connection issues! The username on the server is the same as the username on my Windows 10 PCs, but with a different password. I've tried deleting the saved credentials from the Windows machines, but the issue still happens.

Usually, the only way I can fix the issue is to unmap all of the network drives (10-12) and remap them! I've tried setting the server password to the same as the client login user password and it works as expected, which leads me to believe Windows 10 is having trouble storing separate passwords.

How can I solve this issue so that my network drives automatically connect as they always have in the past?

11

3 Answers

This Microsoft document describes the issue:

Guest access in SMB2 and SMB3 disabled by default in Windows

If you want to enable insecure guest access, you can configure the following Group Policy settings:

Open the Local Group Policy Editor (gpedit.msc). In the console tree, select Computer Configuration > Administrative Templates > Network > Lanman Workstation. For the setting, right-click Enable insecure guest logons and select Edit. Select Enabled and select OK.

To set the value without using group policy, set the following following DWORD registry value to 1 (insecure guest auth enabled) or 0 (insecure guest auth disabled):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters AllowInsecureGuestAuth

This helped me fix an issue where mapped drives would'nt reconnect after restarting Windows 10 machines.

4

If during the time that the replacement router was used, the Windows 10 computers have had some error in the credentials used, the first step should be to clean out the stored credentials.

Deleting Windows credentials is done inControl Panel > User Accounts > Credential Manager > Manage your credentials.

After the old credentials are cleaned out, you could again login to the network shares, to see if they now work as well as before.

If this doesn't help, then this is an error in Windows 10 that was introduced by some Microsoft update.

You could report the problem to Microsoft via the Feedback Hub, while for the present use the same password for server and clients. This is not an ideal situation, but it will work until a better solution is found.

  1. You can check by disabling win 10 Firewall as the it has more new features than the Windows 7 Firewall

  2. If it is a windows server you could install the file server role & share the folder from the server end by giving everyone access within the on-prem environment.(CAn control the permission via NTFS permission)

  3. Please let us know whether your computer is connected to the domain or just a stand alone user PC & a server

  4. Finally as a workaround create a logon script policy to map drive during every logon & create is as a .bat file & schedule it in windows task scheduler to run at the startup

net use [driveletter]: /delete

net use [driveletter]: \server\share /user:[username] password /persistent:yes

For more info fallow ms articles about how to map/delete drive via CMD

1

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like