NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System not recognized in Windows connection
Perfectly operational ReadyNAS 626 system as of one week ago. Installed and recognized for the past three years. Connected and operational on five different Windows workstations. RAIDar can...
You do need to re-boot for edits of the hosts file to take effect.
Also, your error message is The local device name is already in use not an indication that the name is wrong or misspelled? The first command StephenB listed should have cleared all names that were in use. So try this and post exactly what responses you get.
net use
net use * /delete
net use
net use z: \\nas-ip-address\data /u:admin nas-admin-password
net use
If the second command warns you that you are deleting an active connection, reply YES.
I am expecting you will get different responses to each of the net use commands with no arguments.
What I suspect is that you have something that is attempting to automatically mount the NAS that is failing (quite likely simply a persistent drive mapping), but Windows is unaware it failed. So any attempt to re-mount it will give that error message. Now the thing is to find why it failed.
Problem still exists but...
Fat fingering at is worst at the wrong time.
Firefox as the default browser. Recently we have been having some issues with Firefox -- switching to Chrome has exposed some fields in the browser display that Firefox does not display. Seems to be more prevalent on some banking applications and some Microsoft sites. That issue will be investigated separately.
Using Chrome login to the ReadyNAS is possible directly using the IP address (not fat fingered).
Using FileManager login to the ReadyNAS is possible from FileManager using the IP address which 'calls' on a browser to in turn direct to the IP address. Works.
This issue does not present with the Synology NAS on the same subnet.
My tentative conclusion is that ReadyNAS system is responding properly and connectivity is not an issue.
The issue is Windows based.
My next step is going to rename the ReadyNAS system since the Windows error messages indicate it is 'misspelled' or possibly the name is used. The Windows error messages vary between those two depending on the context of access attempts.
Will advise as to the result.
Digital999 wrote:
Using FileManager login to the ReadyNAS is possible from FileManager using the IP address which 'calls' on a browser to in turn direct to the IP address. Works.
This is not using SMB for access.
What happens if you use \\192.168.0.239 ?
Using \\192.168.0.239 works fine.
FileManager opens with the appropriate directories enumerated. Can look at files and other stuff using FM
Sorry, I did not understand difference between SMB and your approach.
Then this is behaving exactly as I suggested -- Windows is not properly determining the IP address from the NAS name. I urge you to type in the commands I listed and the exact responses you get from Windows. The only exact response I have seen you give thus far in no way suggests the name is misspelled. It implies that Windows has already attempted to log in, and actually thinks it has succeeded, and thus is preventing you from doing so again. That is a common symptom of the problem I believe you have.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
