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

Forum Discussion

swejens's avatar
swejens
Aspirant
Aug 28, 2019
Solved

ReadyNAS Ultra II visible but not usable from Win7

Hi, have a weird problem with my NAS. I can ping it within my network, I can surf to it within my network but I can't use it as a storage. (My network = 192.168.3.xxx). I could use it as storage but now when I try to set up a drive letter that uses the NAS all I get from Win7 is "Can't reach //NAS2TB/private" and "Network path not found, error code 0x80070035" (This is not the exact wording since I'm running Swedish Win7).

 

Three days ago all was well. My wifes computer still sees the NAS and can use it for storage. She is using the same wireless network, and win10. What I find really weird is that Win7 says it can't find it but still sees it (se attached picture).

 

I've googled a lot and found information on MS about what services must be started and all is as should be. I did find something about SMB (?) which was really cryptical. Didn't understand what it meant I should do.

 

My knowledge level is power user+ but I'm not a wizard.

 

Any tips?

 

This is my ReadyNAS

Värdnamn: NAS2TB

Modell: ReadyNAS Ultra 2

Serie: 2EH2150W011A9

Fast programvara: RAIDiator 4.2.17 

Minne: 1024 MB [DDR3]

IPv4-adress: 1: 192.168.3.10

 


  • swejens wrote:

     "Can't reach //NAS2TB/private" and "Network path not found, error code 0x80070035" (This is not the exact wording since I'm running Swedish Win7).

     


    Either you mistyped this in the forum, or you are using the wrong slash direction with windows (it should be \\NAS2TB\private)

     

    What happens if you run CMD from windows and enter

    net use * /delete
    net use t: \\192.168.3.10\C /user:admin nas-admin-password

    using the real admin password of course.

     

    The first command terminates any open SMB sessions (so it will dismount any other network drives you have mapped).

    The second command attempts to mount the full NAS data volume as drive letter t.  Note it is using the NAS admin credentials to do that.

     

    Be careful on the typing (particularly the two different slash directions and the spaces).  Also, please do use the NAS IP address for this test (not it's hostname).

     

9 Replies

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

    swejens wrote:

     "Can't reach //NAS2TB/private" and "Network path not found, error code 0x80070035" (This is not the exact wording since I'm running Swedish Win7).

     


    Either you mistyped this in the forum, or you are using the wrong slash direction with windows (it should be \\NAS2TB\private)

     

    What happens if you run CMD from windows and enter

    net use * /delete
    net use t: \\192.168.3.10\C /user:admin nas-admin-password

    using the real admin password of course.

     

    The first command terminates any open SMB sessions (so it will dismount any other network drives you have mapped).

    The second command attempts to mount the full NAS data volume as drive letter t.  Note it is using the NAS admin credentials to do that.

     

    Be careful on the typing (particularly the two different slash directions and the spaces).  Also, please do use the NAS IP address for this test (not it's hostname).

     

    • swejens's avatar
      swejens
      Aspirant

      Thank you!! 

       

      The "//NAS2TB/private" was a typo, it was actually "\\NAS2TB...".

       

      Great, thanks, it worked using the IP adress, great. Still wonder why but that's a different question. Again thanks!

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        swejens wrote:

        Still wonder why but that's a different question. 


        Sometimes Windows has trouble discovering the NAS - in those cases it will work ok with IP addresses, but not the hostname.

         

        Another factor is that Windows can only connect to a device using one set of credentials at a time.  That can sometimes get in the way, and the error messages can be rather misleading.  The "net use * /delete" covers that possibility.

         

        I suspect discovery might have been the problem in your case.

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