This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I have an RBRE950 router with two satellites, all working fine except that the check for firmware update fails. On Advanced/Administration/Firmware update it gives the Status as 'Service Unreachable'.
I'll try that next time I can power cycle without the family moaning. It's purely a web server issue, all devices are actually on the new subnet so its not causing any operational problems.
I'm still curious why it won't find the firmware service but my guess is it'll be cured by the next formware update anyway. No need to stress out on this, I'll just keep my eyes open for firmware updates for the 950 series.
Maybe however maybe a problem here that is inhibiting the RBR from checking with NGs update services. I had someone else check there 9 series since I'm at work and they told me there able to get thru on there system.
The suggestion of trying option #2 would be a trial test to see if that helps the RBR get thru to NG services.
Double NAT really isn't recommended as it can cause problems. Yes it may work for some and that fine if you want to run it like that. Just be aware that not everything may work seemlessly in this configuration. As this maybe one item that shows this.
Nope, it has NEVER come back with that message...always 'service unavailable'.
Well, that is indeed a puzzle. Could you do a small experiment and do a DNS lookup on http.fw.updates1.netgear.com ?
On Windows the easiest way is to open a command window (We old-timers called it a "DOS Window") and type in
nslookup http.fw.updates1.netgear.com
Could you also comment on which DNS servers are being used by this system:
Those provided by the ISP?
Specific DNS servers that you chose?
You are correct that thousands of internet users employ a "Double NAT" because so many of them unbox their new WiFi system (Asus, Google, Linksys, eero, TP-Link.... or Netgear), plug them into their ISP box, read the WiFi credentials off the product label, and "off they go". Many do not even rename the SSID or change the password. They never know.
Internet search will turn up specific situations which Double NAT impacts. Things like:
Forwarding ports to internal servers.
Running OpenVPN to reach the router when away from home.
Certain internet gaming.
People who run into a Double NAT issue generally discover it when something they are trying to do doesn't work and they do a search for probable causes.
I have a second Netgear Orbi that is 'behind' the primary Orbi. That is, definitely a Double NAT. Yet, when I open Firmware Update on that second router, it comes back with "no new firmware".
The DNS was set to 'Get Automatically from ISP' and so I tried using 68.105.28.11 and 68.105.29.11. This make no difference to the nslookup or to the Firmware Update status.
Interestingly, I can ping the updates link just fine:
C:\Users\markg>ping http.fw.updates1.netgear.com
Pinging e70.g.akamaiedge.net [104.119.67.89] with 32 bytes of data Reply from 104.119.67.89: bytes=32 time=18ms TTL=55 Reply from 104.119.67.89: bytes=32 time=20ms TTL=55 Reply from 104.119.67.89: bytes=32 time=19ms TTL=55 Reply from 104.119.67.89: bytes=32 time=20ms TTL=55
Ping statistics for 104.119.67.89: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 20ms, Average = 1
I tried a couple of other sites, and nslookup failed but ping succeeded.
Thanks for doing the DNS experiment. When the Orbi looks for new firmware (two times each day), it makes a sequence of connections to the Netgear firmware server and does a DNS lookup before every connection. (That is how some users block their routers from doing automatic updates. They sign up for an account with OpenDNS and use an OpenDNS feature to block that URL.)
In your case, it appears that the web site is reachable.
I neglected to ask if the system has been restarted. (Not factory reset, just powered off and back on.)
