Thanks GB!  That sped things up on my end alot.  
I was having a problem where I'd close a page...it'd go to the next...but leave the page I just closed still up, but all white/blank.  

Then I'd just get a "non-responsive program" message on my end.  
Seems to flow better now though.  Thanks

<buthead>Uhhhh huh huh huh

Ran Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\proxdom>tracert ar15.com

Tracing route to ar15.com [69.95.2.67]
over a maximum of 30 hops:

 1     7 ms     7 ms    11 ms  10.*.*.*
 2     8 ms     8 ms     9 ms  68.*.*.*
 3    20 ms    22 ms    19 ms  dllsdsrc02-pos0701.rd.dl.cox.net [68.1.206.21]
 4     *       20 ms    34 ms  dllsbbrj02-ge020.rd.dl.cox.net [68.1.0.148]
 5    19 ms    20 ms    19 ms  4.78.234.5
 6    19 ms    20 ms    19 ms  te-7-4.wch010.dllstx2.Level3.net [4.68.110.14]
 7    22 ms    18 ms    21 ms  64.200.249.129
 8    23 ms    23 ms    26 ms  hstntx1wcx3-pos1-0-oc192.wcg.net [64.200.210.66]
 9    29 ms    25 ms    24 ms  hstntx1wcx2-pos6-0.wcg.net [64.200.186.77]
10    51 ms    51 ms    52 ms  drvlga1wcx2-pos12-0.wcg.net [64.200.240.78]
11    52 ms    51 ms    50 ms  hrndva1wcx3-pos14-0-oc192.wcg.net [64.200.210.238]
12    63 ms    51 ms    50 ms  hrndva1wcx2-pos4-0-oc192.wcg.net [64.200.89.121]
13    56 ms    64 ms    57 ms  nycmny2wcx2-pos1-0-oc192.wcg.net [64.200.210.177]
14    60 ms    61 ms    57 ms  nycmny2wcx3-pos11-3.wcg.net [64.200.68.98]
15    59 ms    58 ms    57 ms  nycmny1wce2-pos3-0.wcg.net [64.200.68.102]
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19  ^C

C:\Documents and Settings\proxdom>pathping ar15.com

Tracing route to ar15.com [69.95.2.67]
over a maximum of 30 hops:
 0  *.dl.cox.net [68.*.*.*](hiding the last three octets for the first two hops and my IP)
 1  10.*.*.*
 2  68.*.*.*
 3  dllsdsrc02-pos0701.rd.dl.cox.net [68.1.206.21]
 4     *        *     dllsbbrj02-ge020.rd.dl.cox.net [68.1.0.148]
 5  4.78.234.5
 6  te-7-4.wch010.dllstx2.Level3.net [4.68.110.14]
 7  64.200.249.129
 8  hstntx1wcx3-pos1-0-oc192.wcg.net [64.200.210.66]
 9  hstntx1wcx2-pos6-0.wcg.net [64.200.186.77]
10  drvlga1wcx2-pos12-0.wcg.net [64.200.240.78]
11  hrndva1wcx3-pos14-0-oc192.wcg.net [64.200.210.238]
12  hrndva1wcx2-pos4-0-oc192.wcg.net [64.200.89.121]
13  nycmny2wcx2-pos1-0-oc192.wcg.net [64.200.210.177]
14  nycmny2wcx3-pos11-3.wcg.net [64.200.68.98]
15  nycmny1wce2-pos3-0.wcg.net [64.200.68.102]
16     *        *        *
Computing statistics for 400 seconds...
           Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
 0                                           *.dl.cox.net [68.*.*.*]
                               0/ 100 =  0%   |
 1    7ms     3/ 100 =  3%     3/ 100 =  3%  10.*.*.*
                               0/ 100 =  0%   |
 2    8ms     0/ 100 =  0%     0/ 100 =  0%  68.*.*.*
                               0/ 100 =  0%   |
 3   19ms     0/ 100 =  0%     0/ 100 =  0%  dllsdsrc02-pos0701.rd.dl.cox.net [68.1.206.21]
                               0/ 100 =  0%   |
 4   22ms     0/ 100 =  0%     0/ 100 =  0%  dllsbbrj02-ge020.rd.dl.cox.net [68.1.0.148]
                               0/ 100 =  0%   |
 5   24ms     0/ 100 =  0%     0/ 100 =  0%  4.78.234.5
                               0/ 100 =  0%   |
 6   27ms     0/ 100 =  0%     0/ 100 =  0%  te-7-4.wch010.dllstx2.Level3.net [4.68.110.14]
                               0/ 100 =  0%   |
 7   19ms     0/ 100 =  0%     0/ 100 =  0%  64.200.249.129
                               0/ 100 =  0%   |
 8   25ms     0/ 100 =  0%     0/ 100 =  0%  hstntx1wcx3-pos1-0-oc192.wcg.net [64.200.210.66]

                               0/ 100 =  0%   |
 9   24ms     1/ 100 =  1%     1/ 100 =  1%  hstntx1wcx2-pos6-0.wcg.net [64.200.186.77]
                               0/ 100 =  0%   |
10   51ms     0/ 100 =  0%     0/ 100 =  0%  drvlga1wcx2-pos12-0.wcg.net [64.200.240.78]
                               0/ 100 =  0%   |
11   51ms     0/ 100 =  0%     0/ 100 =  0%  hrndva1wcx3-pos14-0-oc192.wcg.net [64.200.210.238
]
                               0/ 100 =  0%   |
12   51ms     2/ 100 =  2%     2/ 100 =  2%  hrndva1wcx2-pos4-0-oc192.wcg.net [64.200.89.121]

                               0/ 100 =  0%   |
13   56ms     4/ 100 =  4%     4/ 100 =  4%  nycmny2wcx2-pos1-0-oc192.wcg.net [64.200.210.177]

                               0/ 100 =  0%   |
14   57ms     0/ 100 =  0%     0/ 100 =  0%  nycmny2wcx3-pos11-3.wcg.net [64.200.68.98]
                               0/ 100 =  0%   |
15   57ms     0/ 100 =  0%     0/ 100 =  0%  nycmny1wce2-pos3-0.wcg.net [64.200.68.102]
                             100/ 100 =100%   |
16  ---     100/ 100 =100%     0/ 100 =  0%  * [0.0.0.0]

Trace complete.

C:\Documents and Settings\proxdom>

</buthead>

I don't think it's a dns issue... At least in my instance. Hope this helps.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\user>tracert ar15.com

Tracing route to ar15.com [69.95.2.67]
over a maximum of 30 hops:

 1    14 ms    15 ms    10 ms  10.116.*.*
 2    12 ms    14 ms    10 ms  74.128.*.*
 3    10 ms    13 ms    12 ms  74.128.*.*
 4    23 ms    30 ms    23 ms  so-7-1-0.gar2.Atlanta1.Level3.net [4.78.214.17]

 5    33 ms     *       39 ms  ae-31-55.ebr1.Atlanta2.Level3.net [4.68.103.158]

 6    59 ms     *        *     ae-1-100.ebr1.Atlanta2.Level3.net [4.69.132.33]

 7     *       38 ms    37 ms  ae-14-53.car4.Washington1.Level3.net [4.68.121.8
1]
 8    36 ms    41 ms    37 ms  te-7-4.ch010.HRNDVA1.Level3.net [4.68.110.6]
 9    41 ms    37 ms    39 ms  64.200.249.169
10    39 ms    42 ms    40 ms  64.200.249.169
11    43 ms    46 ms    44 ms  nycmny2wcx2-pos1-0-oc192.wcg.net [64.200.210.177
]
12    42 ms    45 ms    42 ms  nycmny2wcx3-pos11-3.wcg.net [64.200.68.98]
13    53 ms     *        *     nycmny1wce2-pos3-0.wcg.net [64.200.68.102]
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *

I think this needs more than a flush.

Bob

Someone on another site told me how to do this, and since I'm able to get into the site tonight, here's what I got;

I am constantly getting this:


Network Error (tcp_error)


A communication error occurred: ""  
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.  

Here's mine;

Network Error (tcp_error)

A communication error occurred: ""
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

For assistance, contact your network support team.


It's the reason I don't post too much on here, simply because I can't. The other six or seven sites I visit every day don't have this problem. It's only here.

Looks like this "mysteriously" become untacked.
Wonder why....

I'd guess because nobody can figure it out anyway.

Try doing a trace through here. http://centralops.net/co/DomainDossier.aspx

I get all kinds of timeouts. I have DSL trough Embarq (Sprint)I have not been receiving emails from AR15.com. Here is what i got....
GlenR

DNS records
name class type data time to live
ar15.com IN SOA server: park11.secureserver.net
email: dns.jomax.net
serial: 2006050200
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s (1.00:00:00)
ar15.com IN A 69.95.2.67 3600s (01:00:00)
ar15.com IN MX preference: 10
exchange: mailfilter.ar15.com
3600s (01:00:00)
ar15.com IN NS park11.secureserver.net 3600s (01:00:00)
ar15.com IN NS park12.secureserver.net 3600s (01:00:00)
67.2.95.69.in-addr.arpa IN PTR host-69-95-2-67.roc.choiceone.net 14400s (04:00:00)

Traceroute
Tracing route to ar15.com [69.95.2.67]...

hop rtt rtt rtt   ip address fully qualified domain name
1 0 0 0   70.84.211.97 61.d3.5446.static.theplanet.com
2 1 0 0   70.84.160.162 vl2.dsr02.dllstx5.theplanet.com
3 0 0 0   70.85.127.109 po52.dsr02.dllstx3.theplanet.com
4 0 0 0   70.87.253.21 et3-1.ibr03.dllstx3.theplanet.com
5 0 0 0   157.238.225.5 xe-4-4.r03.dllstx09.us.bb.gin.ntt.net
6 0 0 0   129.250.3.225 xe-2-0-0.r21.dllstx09.us.bb.gin.ntt.net
7 0 0 0   4.68.110.61 te-3-1.car3.dallas1.level3.net
8 0 1 1   4.68.122.78 ae-12-53.car2.dallas1.level3.net
9 1 0 0   4.68.110.14 te-7-4-72.dllstx2wch010.wcg.level3.net
10 1 1 1   64.200.249.129  
11 6 5 6   64.200.210.66 hstntx1wcx3-pos1-0-oc192.wcg.net
12 5 6 5   64.200.186.77 hstntx1wcx2-pos6-0.wcg.net
13 33 33 33   64.200.240.78 drvlga1wcx2-pos12-0.wcg.net
14 33 34 33   64.200.123.50 drvlga1wct1-teledvance-12-0-0-4.wcg.net
15 67 210 35   64.200.89.121 hrndva1wcx2-pos4-0-oc192.wcg.net
16 38 38 38   64.200.210.177 nycmny2wcx2-pos1-0-oc192.wcg.net
17 38 38 38   64.200.68.53 nycmny2wcx1-pos6-0.wcg.net
18 46 46 46   65.77.98.82 nycmny1wce2-choiceone-5-0.wcg.net
19 * * *    
20 * * *    
21 * * *    
22 * * *    

Trace aborted

Service scan
FTP - 21 Error: TimedOut

SMTP - 25 220 mail.ar15.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at  Mon, 16 Apr 2007 09:29:47 -0400

HTTP - 80 HTTP/1.1 200 OK
Connection: close
Date: Mon, 16 Apr 2007 13:29:04 GMT
Server: Microsoft-IIS/6.0
Content-Length: 114985
Content-Type: text/html
Set-Cookie: ar15=SkipSplash=true&cookieTest=pass&loginName=&loginKey=&sessionID=%7BCD03794C%2D1BB8%2D45D0%2DB4F6%2D2968F308478F%7D; expires=Sun, 15-Jul-2007 04:00:00 GMT; domain=.ar15.com; path=/
Cache-control: private

POP3 - 110 Error: TimedOut

IMAP - 143 Error: TimedOut

Are you guys talking about intermitent network timeouts while surfing around the board?  Especially behind a proxy server?

If so I think I've got a fix.

Quoted: Are you guys talking about intermitent network timeouts while surfing around the board?  Especially behind a proxy server? If so I think I've got a fix.

Here's what I get on almost every click on this site;




To open this thread I got that three times, which is about normal, but I've gotten it up to around twenty times before I got a page to open. (That's why I don't post much on here). I visit six to seven sites per day, and all the other ones together I get that error maybe twice per month.

What are your HTTP Persistant Connection\Keepalive Settings currently set at?

Dropping mine from 60sec to 30sec solved it for me, although I was getting it maybe once a minute, and then I'd have to refresh a number of times to get the page.

This also was only affecting my work machine, which is behind a proxy. It seems to me that it has something to do with the persistant connection getting dropped on the other side of the proxy and the inside connection staying open, so when the client goes to use the socket it's dead.

Are you behind a proxy?

Quoted: What are your HTTP Persistant Connection\Keepalive Settings currently set at? Dropping mine from 60sec to 30sec solved it for me, although I was getting it maybe once a minute, and then I'd have to refresh a number of times to get the page. This also was only affecting my work machine, which is behind a proxy. It seems to me that it has something to do with the persistant connection getting dropped on the other side of the proxy and the inside connection staying open, so when the client goes to use the socket it's dead. Are you behind a proxy?

Ummmmm, I know what seconds are, but beyond that you've lost me.

Goto about:config, search for "keep", then set to false to disable.

See if that fixes it.

I can't figure out how I "Go to" that. I tried Search and Run, but got nothing.

Just type "about:config" in the address bar, without the quotes.

I've found three "keep"s so far.

Damn!

I'm posting from the other side of the world, and I don't have any of these problems.


Do I win anything?  


A cookie maybe?

Quoted: I've found three "keep"s so far.

Set network.http.keep-alive to false

Quoted: Quoted: I've found three "keep"s so far. Set network.http.keep-alive to false

OK, I did it. I'll post up again tonight or tomorrow on whether it made any difference.

Thank you for being patient.

No change; still the same problem.

Try Network.Http.Proxy.Keep-Alive to false.

Quoted: 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...

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.

Quoted: 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?

Quoted: Quoted: 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.

Quoted: Quoted: 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.

Still the same problem.

Quoted: Quoted: Quoted: 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.

Quoted: Quoted: Quoted: Quoted: 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.

Go to...

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\InternetSettings

Create a new key called "KeepAliveTimeout", as a DWORD, with a decimal value of  30000.

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

I've even tried posting the same ad on a different computer at a friends house.
the ad has a lot of pics in it (9 total) would this cause any problems?
I really need help on this guys, I gotta sell this rifle.
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?

Frequent 500.13 Web Server too busy errors this morning.

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?

Works fine from work, but I get time outs at home. I had thought that an IP filter had been put in place, like a few blogs I go to.
(My home IP resolves to a Japanese address, and some web sites block IPs from certain countries)

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.



 

I have the same problem . Reformatted and first stop was here , same result.

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 log in on my home PC.  It just goes right back to the forum page when I attempt to log in.  I tried the forgot password, but the authentication box is fubar.  It's just a box with rectangle missing from the bottom edge and a "2" in the bottom left corner.  Any ideas?

Thanks

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'm in the middle of switching from AT&T to Clear 4G. On my new service I can get to every other website on the net, but not AR15.com. My connection times out "The server at www.ar15.com is taking too long to respond."

I can (obviously) get to the site through my DSL that is still hooked up. I talked to Clear and they think that AR15.com is blocking my new ip address. 50.9.197.53

Can you look into this for me?

Thanks,
Darren

Update: Fixed; it was the Bogon list.

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

test

No more rabbititus.

Try this.

Open up a command window ("DOS" window):

telnet <ip> 80


You should get a server connection.    I suspect that the traceroute is failing because a router at the end of the 'tw' ring won't allow responses.

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