NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
routerlogin.net not working after disabling DHCP
Walked into a new account that was having internet troubles. Fixed the issue with their ISP. Found that there was a Netgear Nighthawk AX8, Model RAX75 "downstream" from the ISP modem. I also noticed ...
> [...] I will try connecting the cable from the Technicolor to the LAN
> port on the Netgear and see what happens. [...]I wouldn't do that. That was a possible explanation for what you
reported, not a suggested course of action.> [...] look in the User Manual for "Set up the router as a WiFi access
> point". [...]Still my advice.
So, the ISP router is a 'Technicolor' brand. Sorry, I don't have the model number. It does have DHCP and dispenses addresses in the 192.168.0.x range. When I turned off DHCP on the Netgear, all the wired and wifi clients connected to it received 192.168.0.xxx addresses. Everything is working as far as networking is concerned.
Finding the address of the Negear in the 192.168.0.xxx range is fairly trivial. I use a program called Advanced IP scanner, which I ran from an ethernet cable connected machine. I believe the address of the Netgear shows up 192.168.0.9. This is the IP address I put into the browser in an attempt to access the admin function.
I did not change the port the cable from the ISP router goes to from WAN to LAN. Maybe I got lucky that the clients are working? Does this fit into your scenario about the Netgear seeing this as a 'remote' access and therefore not allowing the connection?
Thanx for your responses
> [...] When I turned off DHCP on the Netgear, all the wired and wifi
> clients connected to it received 192.168.0.xxx addresses. Everything is
> working as far as networking is concerned.
I can't explain that. I'd expect DHCP problems.
> [...] I believe the address of the Netgear shows up 192.168.0.9. This
> is the IP address I put into the browser in an attempt to access the
> admin function.
I'd expect the ISP router to offer something like an "Attached
Devices" or "DHCP Clients" report, too, where the RAX75 (WAN/Internet
interface) should appear.
> I did not change the port the cable from the ISP router goes to from
> WAN to LAN. [...]
Ok. But that means that "192.168.0.9" is the WAN/Internet IP address
of the RAX75, with the "Remote Management" implications described above.
> [...] Does this fit into your scenario about the Netgear seeing this
> as a 'remote' access and therefore not allowing the connection?
Exactly.
> [...] Maybe I got lucky that the clients are working? [...]
Or there's some fine print someplace which I'm missing (or don't
understand). (It can happen.)
OK. It will be a week or more before I can get back there. I will try connecting the cable from the Technicolor to the LAN port on the Netgear and see what happens. I'll update then.
Again, Mahalo for your assitance.
> [...] I will try connecting the cable from the Technicolor to the LAN
> port on the Netgear and see what happens. [...]I wouldn't do that. That was a possible explanation for what you
reported, not a suggested course of action.> [...] look in the User Manual for "Set up the router as a WiFi access
> point". [...]Still my advice.
Note that if the RAX75 gets its IP address using DHCP, then it'd make
some sense to reserve an address (preferably memorable) for it in the
DHCP server on the main router. When it's configured as a WAP, those
"routerlogin" names might work from a system which is connected directly
to the RAX75, but not from other places on the LAN. Its (new) LAN IP
address should work from anyplace on the LAN.