NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NJRadioGuy
Jun 10, 2015Aspirant
Two ReadyNAS boxen not recognized by Windows 10 Preview
Hi all, I have two ReadyNAS boxen on my system, an old DUO and a newer 102. I have Windows 10 Preview running in a VM and it will not connect to either NAS. They do not show up under "Network", which...
glwrnsn
Jul 21, 2016Aspirant
I have a ReadyNAS NV+ that I cannot get recognized by Windows 10. I had managed to get it to be in FileExplorer but when I double click on it I get error 0x80004002 No Such interface Supported. I have tried a number of things, none which have worked. So I did as you recommend here. First, Administrative Tools and Local Security Policy were in a different location. It was listed under Apps. So I changed the setting, and now my NAS has disappeared from FileExlorer. I tried to change the setting back but it won't let me. I didn't do the second item because I am running Windows 10 Professional 64 bit.
You got any suggestions?
StephenB
Jul 21, 2016Guru - Experienced User
Try this test:
Open CMD and enter
net use * /delete
net use t: \\NASIPADDRESS\c /user:admin NASADMINPASSWORD
The first terminates any open network connections. It might prompt - if so, let it proceed. The second maps the NAS C data volume to driver letter t. Use the real nas ipaddress and nas admin passord of course.
Let us know what happens.
- glwrnsnJul 21, 2016Aspirant
I have already tried this numerous time, but I did it again. Same results, system error 67, the network name cannot be found
- glwrnsnJul 21, 2016Aspirant
You just asked me to do this....I am confused, what will change?
- StephenBJul 22, 2016Guru - Experienced User
glwrnsn wrote:
You just asked me to do this....I am confused, what will change?
Sorry - you jumped to a new thread, and I lost track of your situation.
System error 67 generally means that the network name can't be found. So it is unusual that you are seeing this with the IP address.
I'm not sure what to suggest other than checking that the workgroup names match, that the network type is private, and that SMB access is allowed. But I think you have done all those things.
Related Content
NETGEAR Academy

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