NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK850 Not Connecting/Struggling to Connect to Microsoft Exchange Servers
Need some help figuring this one out - in the last week or so, my Outlook is often failing to connect (or trying to connect for upwards of 45 seconds) due to some blocking/connectivity issues. My PC ...
Doing even more digging...it possibly appears to be related to an "old" bug that Netgear was alerted to previously!
Seems to be related to IPv6 and "IPv6 Filtering" - Default setting is "secured" which research shows may cause issues (hence it was ticketed to support) ...I just switched it to "Open" and it appears to have resolved the issue.
Some testing here - https://test-ipv6.com/
- With Cloudflare Warp (IPv6 Filtering set to Secure) - 10/10 (and quickly)
- With Cloudflare Warp off (and IPv6 Filtering set to Secure) - fails tests (and I get the delays with connecting with the Exchange servers)
- IPv6 Filtering set to Open (and Cloudflare Warp off) - test gets 10/10 quickly and I don't see any delays on connecting with the Exchange servers.
I will clearly have to explore this more but this is promising so far!
What happens if you disable IPv6 altogether?
Well...more testing.
What I wrote previously about Open/Secured doesn't actually work or make a difference.
I took your suggestion, disabled IPv6 and things are working for now.
So by this logic, it is still a problem with the Orbi and how it handles IPv6!!!!
Again, what is really odd is that this problem is new, only happening in the last two or three weeks (I was away on vacation for a week).
How is IPv6 normally configured? Auto or DHCP?
Has been reports from a few users that uses IPv6 normally from the ISP that this version of FW breaks IPv6 so they reverted back to v.31 or v.21. We have already sent this over to NG. No idea when it will be fixed.
Right now I have re-enabled it on Auto (I had just previously tried DHCP and it wasn't working - well, kept failing the IPv6 Test, which it is passing right now on Auto).
Pretty sure it was on Auto previously but for now, I will keep testing this in the current state.
Ok.
Are you using ISP IPv6 DNS or custom DNS?
Sometimes ISP DNS can fail on there side and cause odd problems or failures. CC/XF known for this. If you see odd issues, try using Cloudfare or Quad9 for custom IPv6 DNS as a troubleshooting step.
Thanks, I'm on Verizon Fios (1 gig symmetrical)
Thing is, as I posted very early on (with screen shots), I am already using CloudFlare's DNS for both IPv4 and IPv6 (mostly without incident until a few weeks ago).
Ok, see how it goes, try Quad9 as well. If the issue still seems to appear, may need to revert back to prior working version.
- Doesn't setting IPv6 to AUTO Detect revert to another setting? Mine goes to DHCP...
My IPv6 would work for about 5 hours or so then fail to connect. I tried multiple times a month and a half ago to trouble shoot with no luck, definitely a flaw in the firmware. I was using DHCP... still waiting on Netgear to get this resolved. Completely agree. After a few days of testing, there is clearly a defect in/related to the Orbi.
I have been forced to disable IPv6 to ensure consistent access (and using CloudFlare WARP which gives me IPv6 via its VPN).
Very disappointing given that problems here only started a few weeks ago so it isn't clear to me if its is the firmware specifically or the actual hardware is failing (not yet ready to do a complete reset of the Orbi software).
Seems for those that had native IPv6 on prior FW versions that this newer FW version is broke and not a HW issue. You'll need to disable IPv6 to continue with this version of FW or downgrade back to prior working versions of FW where IPv6 is working. Please make contact with NG support about this as well.
MikeG1970 wrote:
Completely agree. After a few days of testing, there is clearly a defect in/related to the Orbi.
I have been forced to disable IPv6 to ensure consistent access (and using CloudFlare WARP which gives me IPv6 via its VPN).
Very disappointing given that problems here only started a few weeks ago so it isn't clear to me if its is the firmware specifically or the actual hardware is failing (not yet ready to do a complete reset of the Orbi software).
