ReadyNAS NV+ 4450 error 0x80070035 Network Path Wasn't Found

Hello,

You would want to access the admin interface at https://NAS_IP_address/admin. If the box is new to you, you may want to factory default the unit, this will erase any data on the unit and put it in a factory default state.

- http://www.readynas.com/kb/faq/boot/how ... ry_default

I also recommend reading the user manual for the NV+ just to get a better idea of the capabilities. Remember you can also open a case with support for questions as well.

- http://www.readynas.com/download/docume ... 9Nov07.pdf

Support Resources -

Forums:

Prosafe: http://forum1.netgear.com
ReadyNAS: http://www.readynas.com/forum
Prosecure: http://prosecure.netgear.com/community/forum.php

Contact support or register a device

1-888-NETGEAR (638 - 4327) Option 4 for technical support
http://my.netgear.com

Knowledge base

http://support.netgear.com

I had this same problem. The only way I could get Windows 7 or Server 2008 R2 to be able to access the shares on the Readnas, was to to change the security mode of the Readynas to "Share". This is not what we want to use, but we have no choice as this is the only thing that works.

In researching this issue, I think I've determined that this issue is with the Readynas's implementation of CIFS. They are not following industry best practices and some newer OS's have trouble authenticating. Time to get with the program Netgear!

To change the security mode, navigate to http://<ReadnasIP>/Admin
Then go to: Security | Security Mode
Select "Share" and then click "Apply"

Share security mode is not recommended. It is EOL.

Have you installed available software updates on your Windows 7 and 2008 R2 machines?

What version of RAIDiator are you using?

I would suggest you contact NetGear tech support (http://www.readynas.com/support) for assistance.

mdgm wrote:
I would suggest you contact NetGear tech support (http://www.readynas.com/support) for assistance.

It's getting kinda boring, isn't it?

Isn't it time for Netgear to hire someone who has a clue about building and maintaining linux distro and give that person free hand to set up his team (devs, QA, writers etc)...?

szlevi wrote:
It's getting kinda boring, isn't it? Isn't it time for Netgear to hire someone who has a clue about building and maintaining linux distro and give that person free hand to set up his team (devs, QA, writers etc)...?

NetGear's dev team for the ReadyNAS is highly skilled and knows what they are doing. They have found that updating samba from the version currently on Sparc ReadyNAS doesn't work well. For some users a few tweaks on their systems may be needed but it works fine.

Have you tried connecting both by hostname and by IP address? You may find that one works and the other doesn't.

mdgm wrote:

szlevi wrote: It's getting kinda boring, isn't it? Isn't it time for Netgear to hire someone who has a clue about building and maintaining linux distro and give that person free hand to set up his team (devs, QA, writers etc)...? NetGear's dev team for the ReadyNAS is highly skilled and knows what they are doing. They have found that updating samba from the version currently on Sparc ReadyNAS doesn't work well. For some users a few tweaks on their systems may be needed but it works fine.

"Does not work well"...? Excuse me? :)
And this is the "highly skilled" team who "know what they are doing"? Seriously, you really need to put down those pink glasses.

You are posting in a thread on Sparc ReadyNAS and yet you have another thread dealing with issues with a x86 ReadyNAS (e.g. Pro). Your issue is very different to the one in this thread. Different hardware, different OS/firmware.

All I am saying is that the current CIFS stack is a buggy PoS in all curernt firmware - and you're really fooling yourself if you think they are not using the same codebase for all firmwares.

szlevi wrote:
All I am saying is that the current CIFS stack is a buggy PoS in all curernt firmware - and you're really fooling yourself if you think they are not using the same codebase for all firmwares.

The versions of samba in sparc and x86 are very different. Just because the Sparc and x86 UIs look the same it doesn't mean they're the same underneath. If you look at the GPL (http://www.readynas.com/gpl) you'll find they're very different.