NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

MCDelaware's avatar
Sep 08, 2020

can no longer log in from Windows 10 (even with admin)

Sinc e I upgraded, I cannot access any user diresctories with Windows 10.

I can log on to the Admin page via ReadyNas web but no access with File Manager.

 

I've tried all users including admin but neazrly every time, I get the same error message telling me to caontact the admin person but that is me :(

 

The Windows 10 error message: "\\NAS\User is not accessible. You miught not have permissions to use the network resource......"

 

That is while Im looking at the highest directory tree for NAS in Windows 10.

 

Once in a while I have limited success using the cmd someone shared the other day!

net use * /delete /y

to clear the last attempted user (thanks for that nugget!) and I can get into the files but only with admin and only on some occassions. BUT I can NEVER get back into user folders with user credentials.

 

I have resat the NAS and reloaded the latest operating system at least twice.

 

I can get nowhere fairly consistently :(.

 

Maybe I screwed up the user credentials or maybe there is an easy tweek I can do?????

 

I fear the first and hope for the last.

 

 

11 Replies

  • Try opening up the Windows credential manager, and deleting all credentials for the NAS.

     

    Then add a windows credential using the IP address, and use the username/password of a NAS user account.

     

    After you've done that, try rebooting the PC, and accessing the NAS using it's IP address - and let us know how that goes. 

    • MCDelaware's avatar
      MCDelaware
      Tutor

      I think I did what you suggested.

       

      I received different results but not the desired solution (hopefully another clue to where I screwed up?).

       

      When I now type IP address/username for the NAS (http://192.168.1.175) it opens a web browser panel in Windows 10 as if I'm looking for an external device. That is a new oddity.

       

      - If I use the admin account, it opens the local web page for ReadyNas.

       

      - If I use a user account, it opens a web page with the 404 Not Found error.

         "The requested URL /usernamehere was not found on this server."

       

      - If I put in a garbage user name (no account established), I get a different 404 error.

          "The requested URL /safdg was not found on this server."

       

      If I click on the NAS icon in W10 File Manager, it displays a general directory tree and I can access photos and music files that are not in secured folders under a specific user.  That directory tree includes the one user folder which I typically use on this PC.  However, when I click on that username folder, I get this Win 10 (not browser) File Manager error 

        "Windows cannot access \\NAS\Me  You do not have permission to access \\NAS\Me.  Contact your network admin to request access"

       

       

       

      A few more, hopefully unrelated, details here in case they matter.

      - NAS is plugged into my Verizon router. ( I had also tried it physically in my offfice plugged into the POE wall deivce which has two ports and the other is where my PC is connected).

      - PC is plugged in to POE  as I have no cabling available and wireless is slower.

       

       

       

      • StephenB's avatar
        StephenB
        Guru

        MCDelaware wrote:

         

        When I now type IP address/username for the NAS (http://192.168.1.175) it opens a web browser panel in Windows 10 as if I'm looking for an external device. That is a new oddity.

        No, that has always worked that way.  If you are using file explorer, you need to use \\192.168.1.175 (note the different slash).

         

        As I said earlier, I suggest using the IP address instead of NAS for now.

  • There has been an issue with Windows10 and Linux Samba for a while now, and it looks to have finally struck you on this update.  I've had it on some of my computers for a while.  It's associated with device naming in some way, but not in any way I've been able to determine nor have found anyone who has.  It affects systems other than ReadyNAS, but not all equally.  The work-arounds are to use the IP address instead of the name and/or add the name and IP to the HOSTS file.  This, of course, requires that the NAS have a fixed IP address.  But that's always a good idea, and is best implemented by reserving an address in your router rather than using a static IP via the NAS settings.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More