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

Forum Discussion

Gruncle1's avatar
Dec 13, 2016

Can't connect to new Windows 10 computer

I just switched to a new Wondows 10 computer.  My RN 202 was working fine under the old computer.  I can see it and work with it on my router just fine.

 

After many hours of searching and frustration, I have loaded all the newest versions of software that I can find and searched this Community for help.

 

Nothing has worked.

 

Why is such a simplething so difficult?????

 

All my other devices hooked up just fine.

 

Tired and frustrated 

5 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User

    What firmware are you running?

     

    First check that the Windows 10 machine and the ReadyNAS are configured to be in the same workgroup.  Also check that the Windows 10 Network Connection is set to "private".

     

    Then try entering \\nas-ip-address into the file explorer address bar (using the real NAS IP address).  Be careful on the direction of the \.  Does this show you the share list?

     

    Also, are the shares set up for anonymous access?

    • Gruncle1's avatar
      Gruncle1
      Guide
      Windows is the deafult workgrou " workgroup".  I don't know how to determine the NAS workgroup, but I have no knowledge of anything ddifferent.
       
      I can get to the RN 202 by entering the IP address and can see the shares and files.
       
      Everyone that has access has read/write privileges.
       
      What's next?
      • StephenB's avatar
        StephenB
        Guru - Experienced User

        Gruncle1 wrote:
         
         
        Everyone that has access has read/write privileges.
         

        Not quite what I asked - is anonymous access enabled?


        Gruncle1 wrote:
         
        I can get to the RN 202 by entering the IP address and can see the shares and files.
         
         

        In that case, I'd say you have a discovery issue, not a connection issue.  You can access the NAS shares, but it isn't showing up in the network list.   Is that correct?