NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
2 netgear routers(1 as a AP) unable to connect to disired router through IP, resolves to URL
I have 2 netgear routers(1 as a AP) unable to connect administrtively to disired router through IP, resolves to URL routerlogin.net.
I have a RAX48 and a R7000(set up as a AP)
I just purchased a new RAX router and will be reciving it today. I'm thinking of not deploying it and perhaps ever returning it. I have been a Netgear support for 15 years upgrading equipment with netgear every time. I would really hate to migrate my network to another manufacter that doesnt do this, like TP-Link that doesnt resolve the IP to anything.
The problem is causing is that having two devices telling the network that they both are routerlogin.net, I'm unable to connect to the desired device to IP if two IP's resolve to the same URL. routerlogin.net logs me into the device i didnt put the IP address for.
I noticed that logging in to the RAX routers, the router IP address resolves to the URL, but because I have the R7000 it wasnt an issue. the R7000 doesnt resolve to the the URL.
in the latest firmware update for the R7000 V1.0.11.126 it new forces the resolution to the URL. I noticed that Netgear has been pushing out the Netgear App integration to the R7000 in the V1.0.11.11. But that version doesnt force the resolve to the URL routerlogin.net.
This was never an issue with the previous generations of routers and seeing that i was running two generations of routers, it wasnt an issue until the R7000 126 firmware update. in the previous generations you connected to the IP you inputted and it stayed there.
I get why Netgear wants to make things easy for the consumer that isnt a networking professional using a URL is great, for those that run multiple Netgear devices on their network, this is not an acceptable issue.
This could be retified if Netgear added a button to disable resolving to the URL giving the consumer the control to how they access the router and it gives those with multiple netgear devices from causing conflict like this one.
3 Replies
I've always used the IP address of the device I'm trying to connect to and not the routerlogin info.
never had an issue.
And I usually use address reservation so I can setup my other AP's on the IP address I want assigned to them (so I remember which it is)
I'm not sure exactly what issue you're having as your description rambles around a little.
Are you not able to access the R7000 using its ip address?
Thanks for the responseYou are correct.
I have IP reservation for the other router. RAX(XX.XX.XX.1) R7000(XX.XX.XX.2)
Since updating the firmware to V1.0.11.126, When attemptting to access the R7000 via IP, the URL auto resolves to the URL routerlogin.net.
I since downgraded the firmware of tthe R7000 to V1.0.11.11 and it no longer autorevolves to the URL routerlogin.net.
I hypothsis that this is due to the new added features netgear are pushing out to the R7000's for the netgear app integration and improve customer experiance. The V1.0.11.11 is the first firmware where I see a banner on the top saying "Speed up your experience by using the Netgear App. Learn more[button]"
V1.0.11.126 came out shortly after V1.0.11.11.
This sets up a secondary issue, I have a new RAX router(intended to replace the R7000), I wanted to have a uniform wifi 6 solution thoughout my network, and the RAX(set up as a router) I do have have always resolved to the URL routerlogin.net. A URL can't have two IP's address with the expectation that you are intention is to target one specific IP address.
In a network two's IP's can't both be saying that they are both the same URL when you are trying to target one source.
I've got several devices from RAX, CAX, to the SXK series on my network right now (testing). I've been able to use the IP address on them to access them without issues.
Have you tried a different browser?
i don't have the specific R7000 to try but the others I have are newer and should have the auto-redirect if it truly is an issue.What modem/gateway do you have?
