NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Digital999
Jan 29, 2025Luminary
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 access without issues
A windows browse enumerates/finds the device and lists it in browse window
Attempts to access device fail -- error message indicating name might have been misspelled.
It finds the system on the browse and lists it's name -- the same name as the past three years.
Worked fine until most recent Windows automatic update.
Any hint what might have gone wrong?
Anybody else having these problems?
35 Replies
- StephenBGuru - Experienced User
Digital999 wrote:
A windows browse enumerates/finds the device and lists it in browse window
Attempts to access device fail -- error message indicating name might have been misspelled.
It finds the system on the browse and lists it's name -- the same name as the past three years.
Worked fine until most recent Windows automatic update.
What happens if you run CMD and enter
net use * /d /u net use z: \\nas-ip-address\data /u:admin nas-admin-password
Of course use the real IP address and admin password.
- Digital999Luminary
The results mirror the Windows complaint...
"The local device name is already in use."
- StephenBGuru - Experienced User
Digital999 wrote:
The results mirror the Windows complaint...
"The local device name is already in use."
Did you try rebooting both the PC and the NAS? (likely you did, but just in case...)
Is this just the SMB/File Explorer access, or are you also unable to access the admin web ui?
- SandsharkSensei - Experienced User
I've had that problem for several versions, and it's not a unique thing to the ReadyNAS, as I have seen similar complaints in forums for other Linux-based NAS. Basically, there is something amiss with Windows resolving the names of Linux systems to an IP address. I have never seen a real solution, but there is a work-around, which is putting the NAS name and IP address in the Windows hosts file. You can only edit the hosts file in an editor with admin privileges, so it's best to simply Google modify windows hosts file for the particulars.
- Digital999Luminary
The format of the addition to the hosts file is not known.
ReadyNAS_Name //192.168.0.239 is what I tried but it balked.
- StephenBGuru - Experienced User
Digital999 wrote:
The format of the addition to the hosts file is not known.
Easily found if you google for it.
192.168.0.239 ReadyNAS_Name
Did you confirm that you can access the NAS by putting \\192.168.0.239 into the file explorer address bar? (make sure you use the correct slash).
Related Content
NETGEAR Academy

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