Originally Posted By RealFastV6: Try Network.Http.Proxy.Keep-Alive to false.

thanks! i have been having this problem since the last major IT patch rollouts at work...

i didn't even think it could be something local to the machine, thought it was a proxy update to filter guns... commie bastards...


the reason your traceroutes fail is b/c most gateway routers (firewalls) DO NOT pass ICMP packets, to help prevent network discovery and DoS (ping flood) attacks...

Originally Posted By GoGop: Now when I try to get it here's what I get; Network Error (dns_unresolved_hostname) Your requested host "Network.Http.Proxy.Keep-Alive" could not be resolved by DNS. For assistance, contact your network support team.

You went to the about:config page and changed the setting and now you get that?

Originally Posted By RealFastV6: Originally Posted By GoGop: Now when I try to get it here's what I get; Network Error (dns_unresolved_hostname) Your requested host "Network.Http.Proxy.Keep-Alive" could not be resolved by DNS. For assistance, contact your network support team. You went to the about:config page and changed the setting and now you get that?

[Head-hung-low] I tried going to that as a page, rather than the about page. I just went to the proper page and changed it. I'll report back on any changes.

Originally Posted By RealFastV6: Originally Posted By hellbound: Originally Posted By RealFastV6: Try Network.Http.Proxy.Keep-Alive to false. thanks! i have been having this problem since the last major IT patch rollouts at work... i didn't even think it could be something local to the machine, thought it was a proxy update to filter guns... commie bastards... the reason your traceroutes fail is b/c most gateway routers (firewalls) DO NOT pass ICMP packets, to help prevent network discovery and DoS (ping flood) attacks... If disabling fixed it, then we've isolated the problem. Now what you probably want to do is re-enable it, but try using a lower setting so that it'll keep the persistant connection open properly. Try re-enabling network.http.keep-alive, but drop network.http.keep-alive.timeout from 300 to 45 and see if you still have the problem.

i haven't changed it yet... i use IE at work, and it seems that this is a mozilla tunable.

I keep getting this message: "An error occurred on the server when processing the URL. Please contact the system administrator."
I'm on a mac so I can't go to the command prompt.
I've posted lots of things in the EE before without any problems.
thanks

Getting the same thing, despite trying all the fixes. It seems I can only get on about 5 minutes a day before I get the timeouts. My work computer won't get on at all, despite not being a blocked site.. It goes all the way to showing the bolt faced logo and then does the timeout.

Amusingly enough when I go to a COP out in the middle of BFA––-BumFuck Aghanistan, I can get on fine.


Very frustrating––WTF?

There has been a DoS attack working for the last few days. It has been hitting mx servers, mostly. Maybe it's making it's way deeper?

im getting horrible performance loading up ar15.com now.

frequently i have to click a link multiple times to get the page to load in the forums etc.

quite laggy feeling.

I thought it was my system but its just happening on ar15.com...

also the system im using i just reformatted due to this thinking there was malware or something...'

doubt its my net either i have 24mb down/ 9 up

still occurring.

Same problem here, although I can reach the site through a proxy server. I can read and reply, but nothing more complicated than text. Each time I try to get connected I get the whole "Internet Explorer cannot open the webpage" by typing in the address.

Click on Diagnose and I get a "Could not connect to www.ar15.com, the host may be down"

Any fixes? I've cleaned out the history and disabled the Google Toolbar and tried it through Crome as well. Nothing helps.

ETA: I can see my instant messages as well, but can't read them through the proxy server.

I can't access your website from my work

Here is a trace from home, 84.245.27.205:

Tracing route to ar15.com [69.95.2.67]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  172.30.81.254

  2    19 ms    18 ms    20 ms  gw1-bng2.rt-spk.tis.cambrium.net [84.245.26.1]

  3   141 ms    21 ms    21 ms  fo1-asd-ve420-tisgw1.tc1.cambrium.net [217.19.16.121]

  4    26 ms    21 ms    32 ms  Vlan505.icore1.AD1-Amsterdam.as6453.net [195.219.150.41]

  5    21 ms    21 ms    21 ms  if-1-0-0-83.core1.AD1-Amsterdam.as6453.net [80.231.80.5]

  6   107 ms   107 ms   112 ms  if-6-0-0-1733.mcore3.NJY-Newark.as6453.net [216.6.57.29]

  7   114 ms   113 ms   113 ms  if-13-0-0-866.core4.AEQ-Ashburn.as6453.net [216.6.57.82]

  8   113 ms   113 ms   113 ms  ix-9-1-0.core4.AEQ-Ashburn.as6453.net [216.6.42.14]

  9   128 ms   128 ms   131 ms  64-132-52-42.static.twtelecom.net [64.132.52.42]

 10   130 ms   128 ms   128 ms  64-132-52-42.static.twtelecom.net [64.132.52.42]

 11   222 ms   130 ms   181 ms  host-69-95-2-67.roc.choiceone.net [69.95.2.67]

From my work, 90.145.48.134:

Tracing route to ar15.com [69.95.2.67]

over a maximum of 30 hops:



  1     1 ms    <1 ms    <1 ms  10.0.4.33

  2    <1 ms    <1 ms    <1 ms  fw01.dataman.int [10.10.33.33]

  3     9 ms     2 ms     5 ms  90-145-48-129.dataman.nl [90.145.48.129]

  4     2 ms     2 ms     1 ms  90-145-28-253-ams-unet-nik-cx02.network.unet.nl[90.145.28.253]

  5     1 ms     1 ms     1 ms  90-145-29-178-ams-unet-nik-br01.network.unet.nl[90.145.29.178]

  6     2 ms     1 ms     1 ms  asd2-rou-1002.nl.eurorings.net [134.222.96.30]

  7     3 ms     3 ms     3 ms  134.222.224.25

  8    84 ms    84 ms    84 ms  nyk-s1-rou-1021.us.eurorings.net [134.222.226.174]

  9    89 ms    89 ms    89 ms  ahbn-s1-rou-1041.us.eurorings.net [134.222.228.10]

 10    89 ms    89 ms    89 ms  ahbn-s1-rou-1001.us.eurorings.net [134.222.226.57]

 11    90 ms    90 ms    90 ms  eqix.asbn.twtelecom.net [206.223.115.36]

 12    95 ms   102 ms    95 ms  64-132-52-42.static.twtelecom.net [64.132.52.42]

 13    95 ms    95 ms    95 ms  64-132-52-42.static.twtelecom.net [64.132.52.42]

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

etc...

Seems to me like 69.95.2.67 doesn't know the way back to 90.145.48.134
We have no special firewall filters or anything.

i go to many forums everyday . and only 1 has the waiting for ar15.com problem. this has been 4 different ISP's and 3 browsers and 2 operating systems. . I call BS on 85-95 percent on users end.
to this day i have to hit reload on 50-75% of threads I click on. I REPEAT the only forum of Hundreds I have been to that wont most of the time load thread pages on the first try is this one.
and I guess this forum is using software that no other does.
edit.. and it has been this way for the last 3 years or so .maybe longer but my remember ere is broke

No more rabbititus.

Need some help... recently (past week) I noticed when executing various searches within the EE, and then trying to access the result threads, I get the following error:

Server Error in Application "LIVE"

Internet Information Services 7.5
Error Summary
HTTP Error 404.11 - Not Found
The request filtering module is configured to deny a request that contains a double escape sequence.
Detailed Error Information
ModuleRequestFilteringModule
NotificationBeginRequest
HandlerStaticFile
Error Code0x00000000
Requested URLhttp://www.ar15.com:80/forums/t_7_159/894388_WTS__Vltor_EMOD__KAC_RAS__Tango_Down_Stubby.html&light=tango+down
Physical PathD:\wwwroot\2009-ar15\forums\t_7_159\894388_WTS__Vltor_EMOD__KAC_RAS__Tango_Down_Stubby.html&light=tango+down
Logon MethodNot yet determined
Logon UserNot yet determined
Most likely causes:

* The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.

Things you can try:

* Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.

Links and More Information This is a security feature. Do not change this feature unless the scope of the change is fully understood. You should take a network trace before changing this value to confirm that the request is not malicious. If double escape sequences are allowed by the server, modify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting. This could be caused by a malformed URL sent to the server by a malicious user.

View more information »
***** END*****

Criteria using for search:
1) Yesterday was keywords via "Daniel Defense" in titles within 24 or less (threads, not posts), EE forum selected...
2) Today was keywords "Tango Down", same criteria and then error again. Even my own WTS thread failed when trying to access within search results.

Suggestions?????

Thx in advance,
Paul