Unsolved

This post is more than 5 years old

Closed

6 Posts

1685

October 27th, 2018 07:00

Can't connect to router admin page

I have a new Alienware 17 R5 with all updated drivers etc., and for some reason I can't access my router's admin page. Other computers and devices on the network connect just fine. I can ping it and the network works fine otherwise. When the page fails to load, I clock the diagnose link and the message I get is that there was no response received from the site. Any suggestions?

This conversation is no longer open for comments or replies and is no longer visible to community members.

6 Operator

 • 

20.1K Posts

October 27th, 2018 07:00

Is that computer connected by ethernet cable? The browser cannot connect to the router wirelessly.

1 Rookie

 • 

105 Posts

October 27th, 2018 13:00

Try adding the router's IP address to the Hosts file as described here.

11 Legend

 • 

14K Posts

 • 

79.9K Points

October 27th, 2018 15:00

Have you tried another browser?  Have you tried explicitly specifying HTTP vs HTTPS when entering the URL?  Have you made sure you're on the "main" WiFi network rather than guest WiFi?  What router are you using?

11 Legend

 • 

14K Posts

 • 

79.9K Points

October 27th, 2018 15:00


@Mary G wrote:

Is that computer connected by ethernet cable? The browser cannot connect to the router wirelessly.


This is not accurate, at least not for any modern consumer router, or any consumer router I've ever seen.  Routers absolutely allow connections to their admin page over WiFi.  The only exception would be guest WiFi networks where connectivity to LAN IPs is explicitly not meant to be allowed.  If routers didn't allow connections to their management interfaces over WiFi, then a sizable chunk of customers today would be unable to manage their routers at all given that average consumers increasingly do not have any devices with wired Ethernet anymore.

11 Legend

 • 

14K Posts

 • 

79.9K Points

October 27th, 2018 15:00


@ibmarc wrote:

Try adding the router's IP address to the Hosts file as described here.


The hosts file is sort of a "poor man's DNS" in that you can program a name like "myrouter" to map to a certain IP, and then you can use that name to connect to that IP, even if there's no DNS/WINS/NetBIOS entity on the network with that name you chose.  If he's already trying to connect by specifying an actual IP, then the hosts file does nothing.

6 Posts

October 27th, 2018 21:00

Like @jphughan said, I have had no issues connecting to the router admin page through wireless with any of my other devices.

6 Posts

October 27th, 2018 21:00

I have tried with IE and Chrome, and tried https and http. I don't have guest network enabled so it's just the main wifi network. And I only have one band enabled so i'm connecting to the same wifi as all my other devices for certain. Router is an Asus RT3200 running the latest Merlin.

One thing I have not checked is the log file of the router, to see if there are any entries on the connection attempts. Will do that later when I am back home and post back here.

Thanks guys for all the responses so far. And gals, as the case may be.

6 Posts

October 27th, 2018 21:00

I'm using the IP address so the host file wouldn't do anything.... also, when I ping the address, I get the name resolved correctly to asus.router.com .... or is it router.asus.com... whatever, it resolves correctly :)
No Events found!

Top