What's new

[RT-AC87U] "The requested URL was rejected"

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

turbocycle

New Around Here
Looking for help on an interesting problem I encountered yesterday:

When I try try to access the website "amctheatres.com" from any device connected to my ASUS RT-AC87U, I am getting the following error:

The requested URL was rejected. Please consult with your administrator.
Your support ID is: xxxxxxxxxxxxxxxxxxxx

If I connect my PC directly to the cable modem, I can access the site and don't get any error.
I can access all other websites that I tried while connected to the router except amctheatres.com
Traceroute looks different from router compared to direct coneection. Could this be a clue? See below for traceroute outputs.

Something about the router seems to be affecting the error. Has anyone heard of this problem?

More details below:

Router has latest firmware version: (3.0.0.4.382_50010)
Router has been factory initialized
ISP is xfinity
Failure affects any device (laptop, phone, tablet) connected to Router

Setting in the router that I've tried to enable/disable:


Disabled AIProtection and parental controls
Disabled firewall & DDOS protection
Changed DNS (I've tried quad9)
Enabling and disabling IPv6

Other things I've tried:

Clear cookies and cache in Google Chrome on PC and phone
Tried different web browsers (Google Chrome; Microsoft Edge)

Traceroute:

traceroute to the site looks different when I connect directly compared to when I use the router.

Traceroute using cable modem direct connection: (connects to site)

Tracing route to amctheatres.com [169.224.240.210]
over a maximum of 30 hops:
1 8 ms 8 ms 7 ms 96.120.91.193
2 8 ms 7 ms 8 ms be-20021-rur02.sanjose.ca.sfba.comcast.net [68.87.198.177]
3 9 ms 9 ms 10 ms be-331-ar01.hayward.ca.sfba.comcast.net [162.151.79.153]
4 14 ms 10 ms 12 ms be-3651-cr01.9greatoaks.ca.ibone.comcast.net [68.86.91.65]
5 11 ms 11 ms 11 ms hu-0-16-0-1-pe03.11greatoaks.ca.ibone.comcast.net [68.86.88.6]
6 16 ms 15 ms 15 ms 192.205.32.213
7 56 ms 55 ms 55 ms cr2.sffca.ip.att.net [12.122.149.134]
8 61 ms 55 ms 64 ms 12.122.28.117
9 70 ms 57 ms 55 ms cr1.kc9mo.ip.att.net [12.122.3.46]
10 55 ms 54 ms 57 ms 12.122.150.9
11 55 ms 54 ms 55 ms 12.252.221.62

12 62 ms 61 ms 62 ms rtr-lx-1n1.arsalon.net [204.13.97.1]
13 62 ms 62 ms 64 ms 204-13-97-250.arsalon.net [204.13.97.250]
14 68 ms 61 ms 61 ms 169.224.240.210
Trace complete.


Traceroute using router (Request Rejected error):

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 14 ms 8 ms 10 ms 96.120.91.193
3 9 ms 7 ms 7 ms be-10021-rur01.sanjose.ca.sfba.comcast.net [68.87.198.169]
4 8 ms 7 ms 7 ms be-231-ar01.santaclara.ca.sfba.comcast.net [162.151.78.249]
5 9 ms 10 ms 10 ms be-3651-cr02.sunnyvale.ca.ibone.comcast.net [68.86.91.73]
6 8 ms 8 ms 9 ms be-11083-pe02.529bryant.ca.ibone.comcast.net [68.86.84.14]
7 32 ms 28 ms 28 ms 50.248.118.238
8 28 ms 30 ms 28 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.173]
9 39 ms 35 ms 34 ms be3109.ccr21.slc01.atlas.cogentco.com [154.54.44.138]
10 34 ms 34 ms 35 ms be3038.ccr22.den01.atlas.cogentco.com [154.54.42.98]
11 56 ms 52 ms 51 ms be3036.ccr22.mci01.atlas.cogentco.com [154.54.31.90]
12 51 ms 52 ms 52 ms te0-0-2-3.agr12.mci01.atlas.cogentco.com [154.54.27.126]
13 52 ms 52 ms 52 ms 154.24.56.222
14 51 ms 52 ms 52 ms 38.104.88.70
15 51 ms 53 ms 52 ms rtr-pr-1o1.arsalon.net [208.89.116.5]
16 58 ms 58 ms 58 ms rtr-lx-1n1.arsalon.net [204.13.97.1]
17 63 ms 58 ms 59 ms 204-13-97-250.arsalon.net [204.13.97.250]
18 60 ms 60 ms 59 ms 169.224.240.210
 
Something about the router seems to be affecting the error. Has anyone heard of this problem?

It's not your router, it's most likely the IP address your ISP gives you then, which is blacklisted by the remote site.
 
Thanks for the reply! I can access the site now. I always knew it wasn't the router causing the problem directly, but it's a good lesson that sometimes what appears to be the problem may not necessarily be the root cause of a network problem.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top