Can't reach my router login using a gateway address?
Can't reach my router login using a gateway address?
Hi everyone, I am kind of stuck here. For years, I have been logging into my routers by using the default gateway and it has always worked fine. But last week, suddenly I was getting an ERR_CONNECTION_REFUSED error. At first, I thought maybe my router was blocking my system. But when I used a special tool called routerlogin.net to log in again, everything worked. When I used a different device, typed in the gateway address and tried to access the system, it worked once more too. I tried clearing my DNS settings and resetting my local IP address, but nothing helped. I even pinged another computer on the network and got a response back from them. I have full internet access on this device with no weird restrictions that I know of. I tried different browsers too. Anyone else know why I can't connect to my router from the default gateway? If you need more info, I will get back to you as soon as possible.
The hosts file shouldn't just be blank. It needs at least a few basic lines to look like the one from that link. If you added those lines, it was probably done by you or someone else somewhere. You can check online for other host files and see what's on your computer. Just do a quick comparison to make sure there are no mistakes. Even if two years have gone by without any trouble, we still need to keep an eye out: computers change things over time. Different hardware, different software, new firmware updates, and even changes in settings or user actions can cause problems. As for how many devices you have - yes, a /24 address range should work for up to 30 devices if each one has its own unique IP address and MAC address. No duplicates allowed. Now let's check the ipconfig command...
Does your ISP sell or provide modems and routers? Do you own them, or do you rent them from them? If you have more than one device on the network, tell me about all of them. On your main computer, run "ipconfig /all" (no quotes) using the Command Prompt. Post back those results. You should be able to copy and paste them here without rewriting everything again.
Sorry for the late reply: My internet provider is COX and my router model is a Netgear R6300v2. I own this gear, but only two devices are currently connected to it. The first one is my Windows 10 system; unfortunately, that part of my home cannot reach the router login page because Windows blocks it. The second device is a Debian server, and that part can still get in. All other devices on my network can see the default gateway IP but my Windows machine cannot. My current settings are set to: Wi-Fi 6 with an Intel chip running at 160MHz; this wireless card has MAC address 34-C9-3D-B0-0C-0C, and I have enabled DHCP and Autoconfiguration both for sure.
I also have two versions of IPv6 addresses on my router: a preferred one starting with 2600... (which is temporary) and another link-local version starting with fe80... (also temporary). My actual IP address is 192.168.1.29, which belongs to the same subnet as my gateway at 192.168.1.1. I have had this connection since Thursday, January 12, at 10:46 PM, and it will expire on Saturday, January 14, at 10:46 AM. The router acts like a DHCP server for me, sending out an IPv4 address every time I connect, along with some other details about the connection. Everything looks normal so far, except that my Windows system is still stuck behind this wall.
Do you connect them all through wifi or via ethernet? Some routers only let people use ethernet, but most of those are rare now because almost everyone gets their own wifi password and username from the factory. I'm not sure if this is how your web browser is acting up, though you've already tried a different one to make sure it wasn't that.
I do not use manufacturer login websites to manage my routers. That adds too many chances for mistakes. At least routerlogin.net works, so I believe it's about your local network connection. Why would there be a problem? "ipconfig /all" should have shown more details. Did you miss some parts of the results? Also, make sure on your Win 10 system that only one network adapter is turned on (either Wi-Fi or wired). Do not turn two at once. The command shows you are using Wi-Fi with a specific address: 34-C9-3D-B0-0C-0C (matches Intel). Another note says the description is "Intel® Wi-Fi 6 AX200 160MHz". Is that speed correct or what I expect? Let's try turning off IPv6. Sometimes IPv6 causes trouble for devices and networks. Look at the router settings on other computers if needed. Check how many devices are allowed. Make sure the DHCP range is big enough for 30 items. No conflicts with static IP addresses. Check if there are restrictions or reserved MAC/physical address rules in the router. Going back just to be clear: When I type 192.168.1.1 (the default gateway) on my Win 10 system, can't I access the router pages? But yes, I can and am able to directly access them by typing 192.168.1.1 into a browser from another computer. As an elimination check, look at the hosts file in my Win 10 system. By the way: https://www.howtogeek.com/27350/beginner...osts-file/ Very unlikely that the problem is here, but it's okay to just make sure...
I used to have IPv6 turned on when I accessed my router login, but even if I turned it off now, nothing happens. My /24 network is just right for about thirty devices, which is enough. Yes, you get Routerlogin.net if you use the default gateway at 192.168.1.1, but you can't reach that page from the IP address itself. I checked my hosts earlier and it was empty; should that be normal? Maybe I have a VPN as well. I always turn off the VPN before touching anything on my local network to do any config work, and I had this setup for two years with no issues. So why can't I get in when things seem fine?
The hosts file isn't supposed to be blank. It should have at least the basic text from the link shown here. If there are extra lines, you put them in or someone else did it. Just look for other host file examples online and compare them to what's on your computer now. Basically, just think about getting rid of everything until nothing is left that fits this description. Two years without a single problem isn't enough proof to say something isn't broken, especially with computers which change all the time. Different hardware, different software, different settings, updates, and even user choices will eventually cause some trouble. When it comes to how many devices we have, yes, /24 can handle about 30 things as long as every single one has its own unique IP address and MAC address. No two of them should share the same address or network card ID. The output from "ipconfig /all" makes some confusing points because IPv6 still seems to be turned on in this setup. I am not sure about the VPN settings (full disclosure), so I'm guessing there are both real hardware and virtual devices running, but I don't know which one is doing what for you right now. For instance, the IP for VMnet2 looks like 192.168.1.1, which isn't very standard. The same strange numbers happen with VMnet1 (192.168.132.1) and VMnet8 (192.168.81.1). Do we even need subnet masks? Someone who knows more about VPNs could explain that better if you want to ask them. Try connecting directly through the wired Ethernet cable and see if you can access your router's login page straight from there without using a VPN or Wi-Fi. Make sure only that one physical Ethernet adapter is active, turn off all of the wireless settings, and make sure neither are enabled at the same time. Look at "arp -a" in the Command Prompt to check for any weird matches, duplicates, or other strange things on your computers. Overall, I believe this problem is a bit confusing where one fix makes another thing worse, like: if we change Fix A but break Fix B, then fixing that breaks Fix C, and going back fixes everything else again...
Hi, Indirectly fixed my problem lol. I run a lot of virtual machines for different reasons. I forgot that I had 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 defaulted one of my VMs to 192.168.1.1 because the virtual network was running under virtual DHCP. I changed the virtual subnet and tried logging in to the router login via the default gateway, and it worked too. Also, the host file wasn't empty at all; that's just a misunderstanding on my part since I had the default text in there. I knew IPv6 couldn't be the issue because I have been running ipv6 along with ipv4. VMnet was the name of the virtual networks VMware makes and automatically assigns subnets to them unless you manually configure it. Thank you!