NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't access the Router Login page
Small LAN with many Netgear devices. The Network gateway is a Netgear WNR2000v2 -- works great and just chugs along. Introduced a R6220 device and configured it with wireless setup. The dev...
When initially installed it was configured as a router with DHCP capability disabled and a fixed IP address. It was connected to the network via Cat5 cable to the WAN (yellow) port on the rear of the device.
In the same network is a Netgear WNR2000v2 Router used as a connection device to the Internet. That device has wireless capability disabled.
Access to the (new) R6220 device was supposedly via www.routerlogin.net URL in a browser.
What we found with experimentation was:
- User needed to be connected via the wireless network to the R6220 signal to do configuration
- After the R6220 router was configured and an IP address assigned a reboot occurs
- The initial authentication login challenge came from the (old) Netgear WNR2000v2 not the newer device.
- Configured as a router it would not respond to the assigned IP address.
The effect was that after configuration we were locked out of making more changes to the configuration since it was not accessible.
By some experimentation we determined that if the Cat5 connection was to our LAN backbone switch and not the actual (old) Netgear WNR2000v2 then the www.routerlogin.net URL would respond with the newer R6220 device.
By all standards this is a bug/flaw in the system design of Netgear router devices. Two devices that want to respond to the same www.routerlogin.net URL and inability to select the desired device coupled with the inability of the R6220 to respond to the hard IP address is definitely an issue.
The solution was to …
- Login to the desired device – wireless and making sure that the Cat5 cable was not connected directly to the old router itself but to a backbone switch.
- Once logged in
Advanced tab on login page
Expand Advanced Setup on left panel
Wireless Access Point >> Configure as desired.
Once configured as an Access Point the device will respond to the internal static IP address
Thanks for taking the time to resppopnd.
As currently configured the router is connected to the internal network via Cat5 cable from the backbone (dumb) switches.
Connection is to the WAN port on the router.
AP mode is not enabled.
This device is intended to provide wireless access for Guests -- something its predessor could not do.
AP mode could be enabled.
Do you have an opinion?
When initially installed it was configured as a router with DHCP capability disabled and a fixed IP address. It was connected to the network via Cat5 cable to the WAN (yellow) port on the rear of the device.
In the same network is a Netgear WNR2000v2 Router used as a connection device to the Internet. That device has wireless capability disabled.
Access to the (new) R6220 device was supposedly via www.routerlogin.net URL in a browser.
What we found with experimentation was:
- User needed to be connected via the wireless network to the R6220 signal to do configuration
- After the R6220 router was configured and an IP address assigned a reboot occurs
- The initial authentication login challenge came from the (old) Netgear WNR2000v2 not the newer device.
- Configured as a router it would not respond to the assigned IP address.
The effect was that after configuration we were locked out of making more changes to the configuration since it was not accessible.
By some experimentation we determined that if the Cat5 connection was to our LAN backbone switch and not the actual (old) Netgear WNR2000v2 then the www.routerlogin.net URL would respond with the newer R6220 device.
By all standards this is a bug/flaw in the system design of Netgear router devices. Two devices that want to respond to the same www.routerlogin.net URL and inability to select the desired device coupled with the inability of the R6220 to respond to the hard IP address is definitely an issue.
The solution was to …
- Login to the desired device – wireless and making sure that the Cat5 cable was not connected directly to the old router itself but to a backbone switch.
- Once logged in
Advanced tab on login page
Expand Advanced Setup on left panel
Wireless Access Point >> Configure as desired.
Once configured as an Access Point the device will respond to the internal static IP address
It's important to understand how the www.routerlogin.com URL works. Netgear routers intercept DNS queries for that URL and respond with their IP address. This enables users to log into their own router without knowing its IP address.
In order for this work, however, it is necessary to be connected to the router so that it is in a position to intercept the packets. When there are two Netgear routers present, then there can be some ambiguity as to which router will intercept the packets.
Things get trickier if you operate the R6220 in router mode. In router mode, the firewall is active. Therefore, login attempts coming into the WAN port will be rejected unless Remote Management is enabled. Switching to AP Mode will disable the firewall. Logging in by IP address should, then, work. Logging in with www.routerlogin.com will still be subject to the previous statement: the R6220 must intercept a DNS query to www.routerlogin.com before it can respond with its own address. So, I would not really call this a bug; it's a limitation of the technique.
Finally, one word about guest networks. You might have discovered that the guest network is not available in AP Mode. But there is another problem. Since your R6220 is connected to the backbone of your network, guests have full access to the backbone. The guest network is only isolated from the R6220's LAN. But your backbone is on the WAN side of the R6220. As far as the R6220 is concerned, the backbone is figuratively the "Internet".
There are ways to isolate a guest network. For example, if you had a managed switch, then you could set up a VLAN to isolate the R6220 from the rest of the network. Unfortunately, you have dumb switches so you are outta luck.
Thank you so much for taking the time to respond.
My complaint is that none of the documentation discusses this in any cogent way as you just did. Armed with this knowledge apparently the only way to effectively manage this device is via wireless interaction since it does not respond to the static IP assigned.
The only reason I wanted to install the R6220 is to have an isolated Guest network. I did not notice that in AP mode that capability was eliminated. I have switched back to Router Mode to get the guest netowrk capability back and have isolation.
I had turned off Remote Management previously. Does it need to be turned on?
So back to my original question -- how can I select the R6220 for administrative functions when it is in router mode? My quess is wireless but I would appreciate your notions.
Using your excellent advice and description of the issues we enabled Remote Management, changed the port assigned and then limited it to to a select number of internal IP addresses.
Login from a wireless device connected to the R6220 works as expected.
Logihn from the network with https protocols and the corrent port number works.
Guest networks are now available and operational.
What Netgear should do is have some type of FAQ discussing this aspect of connection to networks with multiple Netgear routers.
Thank you again for helping.
