Connecting to NAS - "Windows cannot access"

Page 1 of 2 12 LastLast

  1. Posts : 248
    Windows 10 Pro
       #1

    Connecting to NAS - "Windows cannot access"


    I tried to connect to my NAS by entering \\Wintermute into my File Explorer address bar and was prompted to enter my credentials. I then got this error. I get this error every time I try to connect to \\Wintermute, without being asked for my credentials.

    Can anyone advise which of the following is most likely:

    a) my credentials were wrong and Windows doesn't have the sense to ask me to type them again - it gives me no opportunity to try a second time to enter my password correctly

    b) my credentials were right and Windows knows this but something else is preventing connection


    Connecting to NAS - "Windows cannot access"-delme.png

    Of course, the Diagnose button does nothing helpful. I presume it's there because Microsoft intends to make it functional at some point in the distant future.

    Edit: Hit Win + R and enter rundll32.exe keymgr.dll, KRShowKeyMgr

    Then edit the credentials for the relevant entry.

    Not the experience one expects from the world's leading OS.

    Edit: Now it's gone back to giving this error every time, regardless whether there are credentials saved even though it works fine from another Windows 10 machine and it worked one time (about an hour ago now) on this machine.
    Last edited by THX1138; 22 Apr 2019 at 03:25.
      My Computer


  2. Posts : 5,899
    Win 11 Pro (x64) 22H2
       #2

    What NAS (name and model) are you running?

    I'm running a WD NAS (PR4100) and Windows 10 is handling it just fine. I can also map drives, which means I have to input my credentials. That also works just fine under Windows 10.

    BTW your screenshot alludes a spelling error. Did you double check? Also, under Network, in Windows Explorer, do you see your NAS drive under Storage? If not, either the PC isn't on the same network, or there's a network problem.

    THX1138 said:
    Not the experience one expects from the world's leading OS.
    If the OS was really the problem, none of your Windows 10 machines would work. That doesn't seem to be the case as you stated here...."

    THX1138 said:
    even though it works fine from another Windows 10 machine and it worked one time (about an hour ago now) on this machine.
    With that, are all the machines on the same network?

    Regardless, the issue isn't an OS problem, but appears to be a network problem. You might also doublecheck the NAS drive isn't going offline.

    Let us know.
      My Computers


  3. Posts : 494
    Win 10 Pro x64 versions
       #3

    Change your NAS to use SMB 2.0 at a minimum and disable SMB 1.0 if you can. Windows 10 1809 will now throw the error you are getting when the device you are trying to connect to requires SMB 1.0
      My Computer


  4. Posts : 5,899
    Win 11 Pro (x64) 22H2
       #4

    Why? How? Reason?

    I certainly didn't have to do such a thing, even when I did get an access denied error.

    And under Windows 10 (1809) SMB 1.0 isn't enabled by default anyway.
      My Computers


  5. Posts : 494
    Win 10 Pro x64 versions
       #5

    It has nothing to do with Windows other than their security updates have caused the issue.

    Not knowing your make a model of NAS I cannot tell you how to change these settings on that device. You should have a user manual that can help or you can look for a manual online that may assist you.
      My Computer


  6. Posts : 248
    Windows 10 Pro
    Thread Starter
       #6

    The NAS in question is a Synology DS215j. I think it is to do with Windows because it works fine all the time on my mum's laptop running Windows 10 and sporadically on this machine running Windows 10. SMB 1.0 is already disabled on my machine (as it is by default).
      My Computer


  7. Posts : 494
    Win 10 Pro x64 versions
       #7

    Like I said it needs to be disabled on the NAS itself. You need to use the WEB GUI interface to the DS215j and verify the settings. Besides SMB1.0 needing to be disabled you need to determine that you are on the same Domain. The last Oct. update removed the HomeGroup from Windows networking so all that is left is Workgroup for a Domain name. NetBIOS and Wins Server are other factors that can play into this picture as well even though they are far less likely.
      My Computer


  8. Posts : 248
    Windows 10 Pro
    Thread Starter
       #8

    The UI doesn't differentiate between SMB versions.

    Connecting to NAS - "Windows cannot access"-untitled.png
      My Computer


  9. Posts : 494
    Win 10 Pro x64 versions
       #9

    Did you look in the Advanced Settings section of SMB to see way options may be available? Did you click on the Advanced tab of the File Services screen shown in your screenshot to check for available options? Other functions like NteBIOS and WINS might be found in the Network section.

    Since I do not own a Synology NAS I am not familiar with the interface.
      My Computer


  10. Posts : 248
    Windows 10 Pro
    Thread Starter
       #10

    You're right; they're in the Advanced Settings but changing these to Min = 2 or Min = 2 and large MTU and Max = 3 has not changed the error I get (0x80004005).

    Connecting to NAS - "Windows cannot access"-untitled.png
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:29.
Find Us




Windows 10 Forums