Forum Discussion
Cannot log into my home router
DieHardBattery Reading the comments, I am wondering if the authentication issue is Netgear specific or OS specific.
I tested the routers I regularly interact with (two Cisco, five Linksys, one ATT/Pace, and one Frontier/Netgear 7550) this morning. The Cisco, Linksys and Pace routers snapped right in; I got the error with the Netgear 7750 and reported it.
Is anyone encountering the authentication issue with a router that is not a Netgear?
tomscharbach I believe it might be Netgear specific. When I inquired about this on the Netduma (Netgear) forum, it had been mentioned that the problem has occurred before on other Netgear routers. But this seems to only be affecting the latest Edge builds so it's hard to say.
- tomscharbachAug 17, 2019Bronze Contributor
DieHardBattery "I believe it might be Netgear specific. ... But this seems to only be affecting the latest Edge builds so it's hard to say."
I had the issue on the Netgear router with Edge Chromium, but not Firefox Quantum. That suggests that the issue is Edge Chromium specific.**
Based on what we think we know (Netgear specific, Edge Chromium specific, recent builds specific), my uniformed guess is that something in the coding of the latest builds of Edge Chromium is conflicting with the Netgear OS authentication process/protocols in some way or other. (Yeah, duh, right?)
The good news is that the bug seems to be recent, so the Edge Team can probably figure it out reasonably painlessly if enough people report it.
You might consider opening a ticket with https://microsoftedgesupport.microsoft.com/hc/en-us/requests/new on this issue. I have found them very helpful on other tricky issues.
===========================
**After Edge Chromium failed to authenticate on the router, I used Firefox Quantum to access the router.
- DieHardBatteryAug 17, 2019Copper Contributor
tomscharbach I have done so already. They said they are aware of the issue and are working on a solution.
- Esteban MongeAug 17, 2019Copper ContributorAh nice, good to know that the devs are aware of the issue. Thanks for the update!