Just updated to firmware V3.2.15.25_1.3.15 last night, and now I can't just type https://192.168.1.xxx to access my NAS. The laptop is wired and the NAS is wired, but the Orbi is my DHCP router.
Just updated to firmware V3.2.15.25_1.3.15 last night, and now I can't just type https://192.168.1.xxx to access my NAS. The laptop is wired and the NAS is wired, but the Orbi is my DHCP router.
V3.2.15.25_1.3.15 is not a firmware release for the Orbi RBR50. What exactly was updated?
Is the NAS the only device that does not accept https?
There are a couple of people on this forum who actually have both the WiFi5 and WuFi6 Orbis. My guess is that you find many more people who know about the RBR850 if you post on the "AX" forum:
We're in the 21st century, and e.g. Windows 10 can easily use the WS-Discovery based name resolution (and even NetBIOS name resolution if enabled for legacy NAS systems) to find the NAS based on it's name on the network, so eg. https://nasname/ does the job.
Is that NAS set to a static IP? If not, you might want to consider that.
Alternate, or in addition, the OP might consider adding an Address Reservation so the same NAS interface does get (based on it's MAC address) the same IP address assigned from the Orbi AX router.
Port forwarding is only required for access from the Internet/WAN side.
We're in the 21st century, and e.g. Windows 10 can easily use the WS-Discovery based name resolution (and even NetBIOS name resolution if enabled for legacy NAS systems) to find the NAS based on it's name on the network, so eg. https://nasname/ does the job.
Thanks for the calendar check & reminder (</sarcasm>).... responses like this keep people from collaborating and/or offering suggestions -- even if you dont think they are as up to speed as you on the century.
@Chuck_M There was and is nothing wrong with your original answer, so whats the noise about?
We might need some more insight on the OP's effective problem, e.g. what happens after typing the https URL ... like is the NAS IP correct and still the same, or is the problem restricted to https and does not happen on the NAS access using http, ...
Vaguely (no, very clear) remebring similar posts where Orbi and Orbi AX really did block https, thanks to Netgear Armor (Orbi), or thanks to marvelous firmware quality letting the Orbi UI capture any https connction attempts.
The idea was clearly challenging the OP for using the alternate (sigh ... primarily commodity user related) click-here (Windows Explorer, MacOS Finder, or whatever Linux desktop environment network browser) ... or why not using the undefined NAS vendor discovery utilities [Syno, QNAP, and Netgear does have em...]. Nedless to say, this does add another layer of complexity (sigh, yes!) requiring a healthy and correctly working network (ref. broadcast [the leagcy NetBIOS discovery and name resolution], Multicast [anyhting around mDNS/WD-Discovery/Bonjour]).
Note to myself: I should stop wasting my time on Netgear's consumer ****.
As suggested, make sre the NAS is using a static IP address set ON the NAS or you can set a IP address reservation for the NAS ON the router. I use static IP addresses on my two NAS so the know the IP address doesn't change. HTTP works fine for my needs.
Disable any amror features temporarily to check this.
Just updated to firmware V3.2.15.25_1.3.15 last night, and now I can't just type https://192.168.1.xxx to access my NAS. The laptop is wired and the NAS is wired, but the Orbi is my DHCP router.
