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...
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.
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.
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_NameDid 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).
I apologize for asking about the hosts entry format. You were correct -- a simple Google.
Added info to hosts and it did not respond.
Entry of \\192.168.0.239 in FileExplorer does not work --
Similar entry into browser of http:\\192.168.0.239 also fails
RAIDar works fine
This issue presented on five different workstations all within a couple of days. Easy to blame Windows but the common focal point is the ReadyNAS system.
Obviously we are puzzled.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
