RT-AC66R "You failed to access to the web page that you want to view".

This is a very strange problem that I am having on trying to serf the internet with two of my laptops, sometimes 3. My wife and I have 5 laptops and two desktops. The desktops are connected to our Comcast router by one Ethernet RJ45 cable. That goes from the Comcast router downstairs and connects to my ASUS RT-AC66R in my den where two RJ45 cables connect with each desktop. They run fine. However it is the wireless laptops that sometimes have problems. First it was my wife's Lenovo laptop that had problems, then my Alienware 17 and now my Razer Blade. The problem is that when I boot up these laptops, they get connected to our Comcast wireless network. Office Outlook works fine, even Facebook works in google chrome but the problem is that all the rest of the tabs in either Internet Explorer or Chrome come up with an error that says "RT-ACC66R" and then it says "You failed to access to the web page that you want to view". The address is always http://192.168.1.1/error_page.htm?flag=1
The weird thing is that this address is for the ASUS wireless router which I am not even connected to!
Can anyone help me figure this out? I was thinking that if I could shut down the wireless part of the ASUS router down that this might solve the problem. I could use some sage advice here. Oh and I was able to get my wife's Lenovo working. Oh and my Alienware 18 works just fine on the Comcast wireless network as do all of our smart phones, Canary security camera and my iPad.
Thanks for any ideas that you may have.

 

So what is Asus actually doing in this setup? From the description you gave it seems to work a bit like a switch.
If that is the case cable from Comcast router should be connected to Asus' Ethernet port, not the WAN port, IP should be from outside DHCP range of Comcast one and NAT and DHCP on Asus should be disabled.
If no devices are connected via Wi-Fi to Asus router, you can indeed disable it and see if that helps.

 

How do I disable the wireless aspect of the ASUS router? I have looked it over and there is no off switch for it...
Thanks.

 

Try going to wireless tab (on the left) and once there click on "professional" (up top).
From there you should be able to choose each radio and switch them off (enable radio: no). You will have to switch them both off since these are two separate radios - one for 2.4GHz and one for 5GHz.

 

There may be address conflicts between the Comcast Router and the Asus router.

On the Comcast hardware is there a password for you to access the settings?

If you can,then try disabling wireless in the Comcast.

After saving the settings connect the Asus wan port to any of the the Comcast ethernet ports and use the Asus router's wireless SSIDs and password.

This should allow Access Point Mode.

The Asus then may/should automatically assign a series of non conflicting addresses?

If that works you may then connect all your wireless devices to the Asus using it's both band's SSIDs and password.

This works for me on ATT modem/router with my Netgear R7000 router attached 10.0.0.x addresses assigned to my 11 connect wireless devices by the Netgear R7000.

 

I did as you said and it is working! Thanks!

 

Well it looks like I spoke too soon as yesterday my Alienware 18 had the same error message when trying to connect to the wireless network. I eventually figured a work-around by disabling the wireless card and then renabling it. This morning however my wife's Aurora R-3 desktop had the same error (RT-AC66R) though it is on the ethernet (wired). I did get it working on the wireless network but why the heck would it have an error like this on ethernet?? It like my Triad desktop uses the ASUS hub to connect to the Comcast cable modem with the wireless disabled on the ASUS hub. Any idea why this problem continues to occur with the wireless disabled? Or on the wired side?

 

Is the cable coming from Comcast device connected to WAN port or one of the Ethernet (LAN) ports of the ASUS?

 

I noticed tonight that it was not connected to the WAN port. So I made the change and it seems to have cured the problem...for now, lol. Thanks.

 

Probably for now because it should really be connected to one of the LAN ports, not the WAN port