NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Logging in using the ReadyNas name doesn't work
After updating the system to v. 6.5 the IP address of my ReadyNas changes after each reboot. Not much, just the last 3 digits. This means that now I always have to check the IP adress first. ...
The IP address comes from your router. Usually there is a way to reserve an address there, so it doesn't keep changing.
Resolving by name should work, but finding it by name sometimes is tempermental. If you reserve an address it might be more consistent though.
Turns out the IP adress does NOT come from the router. The router merely defines a range of permitted IP addresses. But the NAS does have a setting for defining a fixed IP address:
Look under "Networking", select the active link -> Settings -> IPv4 -> Configure: static. Done.
As for resolving the name, this feature is not temperamental - it simply doesn't work, never has, even though it's discussed on the OS manual.
-Franco
ZxF wrote:
Turns out the IP adress does NOT come from the router. The router merely defines a range of permitted IP addresses. But the NAS does have a setting for defining a fixed IP address:
You perhaps have never heard of DHCP. By default, DHCP is enabled on the NAS, and it requests an address from the router. Home routers all have DHCP enabled by default, and they will reply with an address (which is within the range you set up in the router). Most home equipment (PCs, tablets, smartphones, media streamers, wifi printers, etc) use DHCP.
If the NAS weren't getting its IP address from the router, you wouldn't have been able to reach it.
ZxF wrote:
But the NAS does have a setting for defining a fixed IP address:
Look under "Networking", select the active link -> Settings -> IPv4 -> Configure: static. Done.
Yes it does. There was a reason I didn't suggest using it. If you don't know what you are doing, then you can create IP address conflicts on your network. You can also lose connectivity to the NAS when you change routers. If you never heard of DHCP, and didn't know that the IP addresses come from your router, then you are in the "don't know what you are doing" category.
Address reservation (as I recommended earlier) is a much better way to go. You can manage all your IP addresses from one place, and accidental address conflicts are easily avoided. And if you get a new router with a different default address range, everything connects.
ZxF wrote:
As for resolving the name, this feature is not temperamental - it simply doesn't work, never has, even though it's discussed on the OS manual.
It works for all five of my NAS on my home network. However, there have been times when it failed for a bit. And there are plenty of posters here that have said that it works for some PCs on their networks but not for others.
I call that "tempermental". I did not mean to imply that it is working for you - clearly it is not.
You perhaps have never heard of DHCP. By default, DHCP is enabled on the NAS, and it requests an address from the router. Home routers all have DHCP enabled by default, and they will reply with an address (which is within the range you set up in the router). Most home equipment (PCs, tablets, smartphones, media streamers, wifi printers, etc) use DHCP.
I have indeed heard of DCHP, but the point is that my hotspot does not allow me to set an IP address for a specific device on the LAN.
There was a reason I didn't suggest using it. If you don't know what you are doing, then you can create IP address conflicts on your network. You can also lose connectivity to the NAS when you change routers. If you never heard of DHCP, and didn't know that the IP addresses come from your router, then you are in the "don't know what you are doing" category.
I may or may not be in that category, but it seems to me you are in the category "uncapable/unwilling to listen" or alternatively "I am not the right person for tech support". Feel free to decide for yourself.
Address reservation (as I recommended earlier) is a much better way to go. You can manage all your IP addresses from one place, and accidental address conflicts are easily avoided. And if you get a new router with a different default address range, everything connects.
Wonderful: a solution I can't implement. That's the kind of suggestions that every customer really looks forward to receiving.
As for resolving the name:
It works for all five of my NAS on my home network. However, there have been times when it failed for a bit. And there are plenty of posters here that have said that it works for some PCs on their networks but not for others.
Again: your "solutions" are not of much help to me. Perhaps asking yourself why it doesn't work in my case might just be more helpful instead of suggesting that everything is fine with this feature. Alternatively you might simply reply that this feature doesn't work as advertised, that Netgear is aware/or not of this problem, that it will be fixed/or not in a future release shortly, etc. etc. If there is something that a user doesn't appreciate - and that is understatement - is not being taken seriously or suggesting that his problem doesn't exist.
Let me start by saying that I don't work for Netgear. This is a user/community forum, and most people who post here don't work for Netgear. Netgear employees all have "Netgear" as part of their user logo.
I can only work with the information you post. There was nothing about a hotspot in your original post. Almost all routers (and I think some hot spots that act as routers) do support address reservation, though some don't call it by that name. It is sometimes called ARP binding or ARP Table. You made a blanket statement that the address wasn't being assigned by the router/hotspot. Since the address was not static and you had connectivity, that clearly was incorrect. Since you didn't seem to realize that, I concluded (perhaps falsely) that you had little network knowledge. If that was the wrong conclusion, I apologize.
I have had to help many users here who have had problems with their static IP address configuration - many forget to set up DNS, many lose connectivity when they switch ISPs, some have IP address conflicts or incorrect subnet masks/gateway addresses. So I strongly recommend address reservation - because when that can be done, it works out better. Certainly if the router has no option for address reservation, then I would have moved on suggest a static IP. Other people do read posts/solutions here, and I didn't (and don't) want users to jump too quickly to the idea of assigning a static address w/o making sure they know enough to assign one correctly. For instance, it should be outside the DHCP range for the router, but still within the subnet.
On name resolution, you already have the needed workaround in place - a static IP address that you can always use. I wasn't trying to solve that problem for you, just trying to explain why I called it "tempermental" (e.g. not reliable). Since this is wifi, perhaps the hotspot isn't bridging the multicast traffic that is needed. Or if the PC is windows, perhaps the network is configured as public.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
