Cannot Connect to CIFS / SMB / Samba Network Shares & Shared Folders in Windows 10

»»»Cannot Connect to CIFS / SMB / Samba Network Shares & Shared Folders in Windows 10
In Windows 10, especially after upgrading to Windows 10 build 9926 released on January 2015 or later, you may encounter the following error when attempting to access remote shared folders or network locations on a file server or NAS through CIFS, SMB or Samba protocol. The remote network locations or shared folders have been working all along, and continue to work and accessible for workstations running Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows XP and older Windows versions.

\\Remote-Server\Path 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.

The account is not authorized to log in from this station.

The Account Is Not Authorized to Log In from This Station Windows 10

Note: The error message may change as Microsoft finalized Windows 10, but the symptom is the same.

Cause

The issue happens because Microsoft decided to “help” you to be more secure, by disabled guest access to remote file access without an account (i.e. user name and password). Microsoft explained:

The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server. A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.

Resolution

Microsoft recommended to add an explicit user account and password on your NAS device or remote server which hosts the shared folders or remote file access, and use that account for the connections. Or you can use HomeGroup if everything is running Windows 7 or newer. As Windows 10 can remember the user name and password credentials, so it’s a one-time inconvenience to help secure your data and connections.

But thanks Microsoft. Remote file access has always included a way of authenticating with user name and password before the access is granted to connect to a file server. The fact that users are still setting up the file sharing with guest access, where everyone can connect without a user accounts shows there is a need for accessing remote files and folders without worrying about user accounts authenticating.

To re-enable the guest access to remote shared folders and network locations in Windows 10:

  1. Run Registry Editor (REGEDIT).
  2. Navigate to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

  3. Right click on the Parameters key name, and select New -> DWORD (32-bit) Value.

    New DWORD (32-bit) Value

  4. Name the new value as AllowInsecureGuestAuth and set its value data to 1.

    AllowInsecureGuestAuth

  5. You should be able to access CIFS / SMB / Samba network shares instantly without login.

Update: If you’re using a Microsoft Account (MSA) to sign into Windows 10, you may also need to create a domain user account with proper access permissions configured in Samba or Windows Shared Folders on the remote server for authentication purpose, as Windows 10 may assume those logging in with MSA as domain users and requires higher trust level for security.

The solution is to create a local user that had the same username with Microsoft Account (the emailaddress@outlook.com or emailaddress@hotmail.com email address) used to sign onto Windows 10. In Windows, you can use Control Panel or PC Settings app to create a new local user account, while in Linux, uses useradd, passwd, and usermod to create the local user account, set its password and add it to the user groups which has the access rights in Samba.

Once you added the user account in remote server to connect to, time to add the user credentials for the network share to your system. To do so:

  1. Open Power Users Quick Access menu and select Control Panel.
  2. Go to User Accounts.
  3. Click or tap on Manage Windows Credentials. Or, go to Credentials Manager then Windows Credentials tab.
  4. Click or tap on Add a Windows credential.

    Add a Windows Credential

  5. Enter the remote server computer name as the Internet or network address, and then enter the user name and password similar to MSA created on the remote server.

    Add Windows Credential

  6. Hit OK when done.

You can now try to connect to network shared folders.

By | 2016-12-09T08:39:11+00:00 December 9th, 2016|Categories: Windows|Tags: , , , |30 Comments

About the Author:

LK is a technology writer for Tech Journey with background of system and network administrator. He has be documenting his experiences in digital and technology world for over 15 years.

Connect with LK through Tech Journey on Facebook, Twitter or Google+.

  • R063R

    tx, saved me some hours!

  • terion

    Yay! Saved my life.

  • user

    Thx, it helps me!

  • yves

    Merci beaucoup, beaucoup et encore beaucoup !

  • Thank you man!!!

  • angelito

    it doesnt work

  • Jake

    This didn’t work for me.

  • Kempy

    Doesn’t work for me with build 10074

  • josue

    Thanks, It helped me alot!

  • jimmyfi
  • And you should unlink the Microsoft account and use the local account. Then a reboot is needed.

  • Matthew Kent

    I wish this worked for me. I am not sure which update, but I can no longer access a Win 2012 storage server via file explorer. Ping resolves DNS, remote access resolves dns… everything can access the storage server except file explorer via DNS or IP, which gives me a generic undefined network error problem. I played with credential manager and no luck there either. I am kind of amazed at how many major bugs I am finding in Windows 10 this close to RC. All my Win 7/8 and OS systems do not have this issue.

    • Marcos Ferreira

      Me too. The only way to get this working, that i found, is logout my Microsoft account and login with local account, everything Works fine like this. So, when i login again with Microsoft account, all my machines/share from Linux, SMB/CIFS, i can’t see.

      • Matthew Kent

        That seems to work, but is kind of annoying with how much stuff is now linked to your MS account. I hoped that the final update would fix this, but this still seems to be true. I’m in Redmond and was just talking to some “people”… apparently this is not an unknown problem.

        • Marcos Ferreira

          I hope! Unfortunately, in build 10240 this still not working. Everything that i read around the foruns, seems to be a feature to provide some “security”, i don’t know, maybe like you say in Final version, someone or Microsoft will fix this, i hope.

  • Tom

    For me this worked: http://huto.ddns.net/?p=255

  • brycenesbittt

    The worst part is that Windows 10 does this silently. Better would be to show the guest network as an unclickable ghosted icon, thus explaining the problem without the need to resort to a Google (TM) brand search engine.

  • HeidiHoNeighbor

    Going to install Linux Mint instead. No point to Windows anymore.

  • INFINUM

    Not working for me

  • Lee Elson

    Didn’t work for me

  • VecH

    add:
    server signing = auto
    to smb.conf in GLOBAL section

  • Michał Wodzicki

    not working after anniversary update :/

  • Jeroen van Omme

    Thanks, this worked strait-away!

  • Arccas

    A second part of guide has woked for me. You just add Windows Credentials with remote server address or just local machine \192.168.0.1 for examle, and set your name but without password if you have not any. Thank you.

  • Max le Fou

    THANK YOU! You can’t imagine how many hours i wasted struggling into this problem!

  • Veronique Dupre

    Woah! Thank you very much! For me, after modifying the registry, I have added my linux username and password in the Windows Credentials with remote server name and… Tadam!

  • Solution no longer works as of the Anniversary Update.

    • Admin

      Is there any other kind of error message?

      • Aakash Nandode

        Again same error 0xC0000205 (After RS2: Not worked ;again all tweaking properly into regedit still SMB/CIFS/SAMBA Shares problem remains the issue,Going to switch mint as Primary )

  • Rahul

    Thanks for sharing this!

Pin It on Pinterest

Share This

Share This

Share this post with your friends!