NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 ...
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 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).
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!
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.
Yes, discovery is the problem as I now understand it.
As mentioned, my wifes PC sees the NAS as a NAS and sees my computer ánd uses the "\\NAS2TB\Private" while mine doesn't see hers and can not use the name.
Any suggestions where to learn a little, from a beginners perspective, about discovery and how to make it work? (mslldp.dll isn't in my win\system32\drivers directory and I don't have the protocol "Microsoft LLDP protocol driver" in my network card properties, (and I seem unable to add it)).
But my main problem is solved, thank you so much! :-)
swejens wrote:
Any suggestions where to learn a little, from a beginners perspective, about discovery and how to make it work?
Not really (other than googling).
From a practical perpective there are two workarounds
- Just use the IP address
- create a hosts file on the PC
https://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/
Either way, you want a persistent IP address for the NAS. While using a static IP address configuration will work, you are better off using address reservation in your router (most have that feature).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
