[SOLVED] Cannot connect to Router Login via Gateway IP ?

[EyyMunchian]

Hello everyone, I am kind of stumped on this one. For years I have been accessing my routers login via the default gateway and it has always worked. Last week for some reason I kept getting ERR_CONNECTION_REFUSED. At first, I thought maybe the router was blocking my system but using routerlogin.net I was able to log into my router again. Using a different device, I typed in the gateway and was able to access the system once again. I tried flushing my system dns and releasing and renewing my local ip, nothing. I pinged another system on the network and got a response. I have full internet access on the device with no restrictions I know of. I tried different browsers too. Anyone know why I cannot connect to my router from the default gateway? If you need any additional information I'll get back asap.

 

[Ralston18]

ISP, make and model modem, make and model router? (Or modem/router if combined.)

Do you own the equipment or rent from ISP?

If you have multiple devices, list all of them.

On your main PC run "ipconfig /all" (without quotes) via the Command Prompt.

Post the results. You should be able to copy and paste the results without needing to retype everything.

 

[EyyMunchian]

ISP, make and model modem, make and model router? (Or modem/router if combined.)

Do you own the equipment or rent from ISP?

If you have multiple devices, list all of them.

On your main PC run "ipconfig /all" (without quotes) via the Command Prompt.

Post the results. You should be able to copy and paste the results without needing to retype everything.

Sorry for the delayed Reply:
ISP: COX
Make + Model: Netgear R6300v2
I own this equipment
Up to 30 devices but the two I am using now are my personal Win10 system (which cannot access), and a debian 11 server (which can access). Other devices on my network can also access the routerlogin page via the default gateway IP but my system cannot.

IP Config /all:

Wireless LAN adapter Wi-Fi 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz
Physical Address. . . . . . . . . : 34-C9-3D-B0-0C-0C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:8800:b540:29:4861:a605:c1ec:bfe0(Preferred)
Temporary IPv6 Address. . . . . . : 2600:8800:b540:29:e145:2e21:e989:9bfb(Deprecated)
Temporary IPv6 Address. . . . . . : 2600:8800:b540:29:e5e6:c081:c644:1963(Preferred)
Link-local IPv6 Address . . . . . : fe80::b1e6:1f21:a8f1:1992%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.29(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, January 12, 2023 10:46:19 PM
Lease Expires . . . . . . . . . . : Saturday, January 14, 2023 10:46:20 AM
Default Gateway . . . . . . . . . : fe80::a204:60ff:fe82:f6e6%19
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 607439165
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-87-5E-D3-24-4B-FE-05-32-A2
DNS Servers . . . . . . . . . . . : fe80::a204:60ff:fe82:f6e6%19
192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[bill001g]

Do you access them all via wifi or are the ones that work on ethernet. Some routers restrict admin access to ethernet...although that is not as common now that many routers come with unique ssid and passwords from the factory.

Not sure this is what a browser issue looks like but you have tried a different browser.

 

[Ralston18]

I avoid using the manufacturer's "login" websites to administer local routers. Just adds layers for more potential errors of omission or commission.

At least routerlogin.net works so my thought is that the being unable to directly login to the router is a local network issue.

There should have been more information provided by "ipconfig /all". Did you leave out part(s) of the results?

In any case, ensure that on your personal Win 10 system that only one network adapter either wireless or wired is enabled. Not both adapters and not two adapters at the same time.

"ipconfig /all" indicates you are using wireless via a wireless LAN with the Physical Address = 34-C9-3D-B0-0C-0C (Matches Intel)

Reference:

https://macvendors.com/

Another note:

"Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz"

Is 160 MHz correct or expected?

= = = =

Try disabling IPv6. IPv6 can and does create problems for some devices and host networks.

Take a closer look at the router's network configuration settings using other computers if and as necessary.

Check for some limit on the number of allowed connected devices.

Ensure that the DHCP IP address range is wide enough to accommodate 30 devices. Ensure that there are no conflicting Static IP addresses being used.

Look for any blocked, restricted,or reservations regarding the MAC/Physical address in the router.

= = = =

Going back a bit just to ensure that I understand correctly:

When you type 192.168.1.1 (Default Gateway IP) into the personal Win 10 system you are unable to access the router's admin pages - correct?

However, you can and are able to directly access the router's admin pages by typing 192.168.1.1 into the browser of other computers - likewise correct?

As a matter of elimination, take a look in the hosts file of your Win 10 system. FYI:

https://www.howtogeek.com/27350/beginner-geek-how-to-edit-your-hosts-file/

Unlikely that the problem is in the hosts file but no harm in checking just to be sure.....

 

[EyyMunchian]

Do you access them all via wifi or are the ones that work on ethernet. Some routers restrict admin access to ethernet...although that is not as common now that many routers come with unique ssid and passwords from the factory.

Not sure this is what a browser issue looks like but you have tried a different browser.

Wifi and yes I've tried Edge, Chrome, Firefox, and Opera

 

[EyyMunchian]

I avoid using the manufacturer's "login" websites to administer local routers. Just adds layers for more potential errors of omission or commission.

At least routerlogin.net works so my thought is that the being unable to directly login to the router is a local network issue.

There should have been more information provided by "ipconfig /all". Did you leave out part(s) of the results?

In any case, ensure that on your personal Win 10 system that only one network adapter either wireless or wired is enabled. Not both adapters and not two adapters at the same time.

"ipconfig /all" indicates you are using wireless via a wireless LAN with the Physical Address = 34-C9-3D-B0-0C-0C (Matches Intel)

Reference:

https://macvendors.com/

Another note:

"Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz"

Is 160 MHz correct or expected?

= = = =

Try disabling IPv6. IPv6 can and does create problems for some devices and host networks.

Take a closer look at the router's network configuration settings using other computers if and as necessary.

Check for some limit on the number of allowed connected devices.

Ensure that the DHCP IP address range is wide enough to accommodate 30 devices. Ensure that there are no conflicting Static IP addresses being used.

Look for any blocked, restricted,or reservations regarding the MAC/Physical address in the router.

= = = =

Going back a bit just to ensure that I understand correctly:

When you type 192.168.1.1 (Default Gateway IP) into the personal Win 10 system you are unable to access the router's admin pages - correct?

However, you can and are able to directly access the router's admin pages by typing 192.168.1.1 into the browser of other computers - likewise correct?

As a matter of elimination, take a look in the hosts file of your Win 10 system. FYI:

https://www.howtogeek.com/27350/beginner-geek-how-to-edit-your-hosts-file/

Unlikely that the problem is in the hosts file but no harm in checking just to be sure.....

Full IPCONFIG /ALL pastebin:
config - Pastebin.com
160 Mhz is correct yes.
I had IPv6 enabled when previously accessing my local routerlogin, I tried to disable it and still nothing.
Using a /24 network which means 30 devices isn't much and can handle a few more.
And yes, you do understand correctly I can access the login page via Routerlogin.net but I cannot via 192.168.1.1 (default gateway), I decided to check my hosts earlier doing my own troubleshooting, but it was empty, is it supposed to be like that? But I might add I do have a VPN as you can see from the Pastebin, but I make sure it is shut off before trying to access anything on my local network to do any config work. I'had it for around 2 years and has not given me problems so surely it cannot be that?

 

[Ralston18]

The hosts file should not be "empty". There should be at least the basic text in place as shown by the link. Any other entries would have been entered by you or perhaps some other source. Search online for some other host file examples and compare to the host file on the computer in question. Just as a matter of elimination.

Unfortunately two years without problems is not a fair basis for excluding anything: especially with computers. The mix of hardware, software, firmware, configuration settings, updates, etc., and user actions sooner or later will result in some issue.

As for the number of devices - yes /24 should handle 30 devices but only if each device is unique. No duplicate IP addresses or MACs.

The "ipconfig /all" results raise some questions. IPv6 still seems to be enabled.

I am not sure (full disclosure) about the VPN configuration: It appears that there are multiple hardware and virtual devices enabled. What is to be what I do not know.

For example, the IP address for VMnet2 is shown as 192.168.1.1 - not what I would expect. And likewise for VMnet1 and VMnet8 being 192.168.132.1 and 192.168.81.1 respectively. Subnet masks.....?

Someone much more well versed in VPN may choose to comment accordingly.

Try a direct wired/Ethernet connection to the router and determine if the router's admin pages can then be directly accessed. Ensure that only that one physical Ethernet adapter is enabled. No VPN, no wireless - ensure that both are completely disabled.

Take a look at "arp -a" via the Command Prompt. Check several of the computers to look for some mismatches, duplicates, etc..

Overall, I think the problem is some configuration mismatches that lead around in a circle. Fix A and B is off, fix B and C is off, fix C and A is again off......

 

[EyyMunchian]

The hosts file should not be "empty". There should be at least the basic text in place as shown by the link. Any other entries would have been entered by you or perhaps some other source. Search online for some other host file examples and compare to the host file on the computer in question. Just as a matter of elimination.

Unfortunately two years without problems is not a fair basis for excluding anything: especially with computers. The mix of hardware, software, firmware, configuration settings, updates, etc., and user actions sooner or later will result in some issue.

As for the number of devices - yes /24 should handle 30 devices but only if each device is unique. No duplicate IP addresses or MACs.

The "ipconfig /all" results raise some questions. IPv6 still seems to be enabled.

I am not sure (full disclosure) about the VPN configuration: It appears that there are multiple hardware and virtual devices enabled. What is to be what I do not know.

For example, the IP address for VMnet2 is shown as 192.168.1.1 - not what I would expect. And likewise for VMnet1 and VMnet8 being 192.168.132.1 and 192.168.81.1 respectively. Subnet masks.....?

Someone much more well versed in VPN may choose to comment accordingly.

Try a direct wired/Ethernet connection to the router and determine if the router's admin pages can then be directly accessed. Ensure that only that one physical Ethernet adapter is enabled. No VPN, no wireless - ensure that both are completely disabled.

Take a look at "arp -a" via the Command Prompt. Check several of the computers to look for some mismatches, duplicates, etc..

Overall, I think the problem is some configuration mismatches that lead around in a circle. Fix A and B is off, fix B and C is off, fix C and A is again off......

Hi
Indirectly solved my issue lol. I run virtual machines due to a wide variety of reasons. I had forgotten that I made a custom virtual network using the 192.168.1.x subnet instead of the 192.168.2.x subnet. So, the VMware virtual network had defaulted one of my VMs to 192.168.1.1 because the virtual network was operating under virtual DHCP. I changed the virtual subnet and tried to login to the router login via the default gateway and it worked. Also the host file wasn't completely empty, which is a miscommunication on my end, it had the default host text in there. I knew IPv6 couldn't be the issue since I have been running ipv6 along ipv4. VMnet was the name of the virtual networks VMware makes and auto assigns subnets to them unless manually configured.
Thank you!