I have a D-Link router. I want to connect to the settings menu (using 192.168.1.1) in order to do things like port forwarding. I am unable to connect to this address while using Ethernet (Chrome just tries to load the page forever and nothing happens), but when connecting through WiFi I can load the page. Why might this be happening? I'm using Windows 10.
Update: Tried again with Edge and IE. Same result, page just hangs and doesn't load; I don't even get the sign-in prompt.
Update 2: Used the commands ipconfig /release, ipconfig /renew and ipconfig /flushdns. Page now doesn't load at all; Chrome just says
The 192.168.1.1 page isn't working.
192.168.1.1didn't send any data.ERR_EMPTY_RESPONSE
Update 3: Doesn't even work with WiFi now. I changed nothing.
Update 4: After reading some stuff about Java and how Chrome no longer supports Java plugins (or something) I decided to try updating to the latest version of Java. Internet Explorer now says
This page can't be displayed
and Chrome says
The 192.168.1.1 page isn't working. 192.168.1.1 didn't send any data.
Update 5: Talked to a TalkTalk agent about the problem, no change unfortunately. My router is a D-Link DSL-3680
176 Answers
If you don't get anything back, and you've already tried resetting the router, then try booting a linux liveCD on the PC and accessing your router via browser on the linux environment over ethernet. If that works then we can assume the issues lies with your network configuration on the Windows 10 machine - something like a proxy setting, protocol setting, or driver is causing issues. Troubleshoot those manually or reset to factory defaults.
If linux can't access the router, we can assume the problem is hardware-based. Test as many of the following as possible:
- Use a different ethernet port on the PC (might have to add a NIC if you have an old one laying around)
- Use a different ethernet port on the router
- Use a different ethernet cable
- Try a different router
- Try a shorter cable
This process should step you through the remaining possibilities. With every part of the chain tested, there is no possibility of the problem remaining after proper implementation of this process, unless you happen to be operating in an unusually high radiation or electromagnetic field.
Double check the IP address of the router (type Cmd from the start button and then type IPCONFIG)
It should be under "Ethernet Adapter Local Area Connection" (wired Connection) The default Gateway should read 192.168.1.1 - The same as your "Wireless LAN Adapter Wireless Connection" setting. That is the address of the router.
If your wired connection reads Media Disconnected, Check or replace the cable.
4There are 3 possibilities for losing access to your router:
The most likely reason:
- You've accidentally set the IP obtained from Wi-Fi, as the only Management IP. So, if after
ipconfig /releaseipconfig /renewyou obtained IP192.168.1.9and you lost access to management service, then probably you can access it again by setting your IP manually to one of the addresses in the range192.168.1.2 - 192.168.1.8with the last one being the most likely address to solve your problem (last address before renewing your IP). Try to do that from Wi-Fi, since it was the last accessible workstation. If it doesn't help, a factory-reset is the only possible way IMO.
Just for your consideration, Not related to your problem since you had access to WEB panel using default port:
You've disabled Management over HTTP for LAN zone. There's a chance that other management options like
telnetare still accessible. Try to enable Telnet Client feature in your windows (if not already enabled) by going toappwiz.cpl> Turn windows features on or off> Telnet Clientand opencmdthen runtelnet 192.168.1.1if it asks for username and password, then you are able to manage your router and even enable HTTP web panel.There's also a chance that you changed default port for Management services, it's
HTTP:80andTelnet:23by default. If you changed both, then there's no way to recover access than remembering the port, or reset to factory defaults.
I had a similar problem with my linksys router and even a factory reset wouldn't work. Weirdly, a factory reset followed by plugging the router into my network (LAN) but not plugging it in to the power outlet brought it back:
1.With the unit powered on, press and hold the reset button on back of unit for 30 seconds
2.Without releasing the reset button, unplug the unit and hold reset for another 30 seconds
3.Plug the unit into your computer with an ethernet cable STILL holding the reset button a final 30 seconds
4.Wait for a full minute before plugging your router back in.
Hope this helps.
1) Be completely sure you have only "one" DHCP server in your net; your Dlink router. (Wireshark traffic captures can give you an idea if your router is the ONLY DHCP service available and if it is assigning the right IPs or not)
2) Factory reset usually set Dlink routers management port to 192.168.0.1
3) Be sure yo do not have any MAC filter preventing WEB management.
Windows ran a network diagnostics for me and found the DHCP had been switched off on my laptop. I pressed the option to allow diagnostics to fix the problem and it did.
1
