From the symptoms, there\'s a FILTER blocking my IP prior to the forum software even seeing me.
I can come in through a proxy server. But if I do a tracert to gunloads.com, it fails as soon as it gets to hivelocity
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\\Users\\Orville>tracert gunloads.com
Tracing route to gunloads.com [199.193.118.95]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 11 ms 17 ms 10.96.128.1
3 9 ms 11 ms 13 ms rne-10g2-1-2.bxtnme01-rtr001.ne.northeast.rr.com
[24.31.156.238]
4 11 ms 10 ms 11 ms g10-4-2-0.ptldmehx-rtr001.ne.northeast.rr.com [2
04.210.69.242]
5 29 ms 31 ms 39 ms rdc-204-210-69-49.ne.northeast.rr.com [204.210.6
9.49]
6 30 ms 31 ms 31 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
7 29 ms 60 ms 28 ms 107.14.17.169
8 27 ms 29 ms 27 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 29 ms 29 ms 41 ms ae-32-52.ebr2.Newark1.Level3.net [4.69.156.62]
10 43 ms 34 ms 39 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101
]
11 37 ms 33 ms 40 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
12 37 ms 34 ms 34 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.1
41]
13 54 ms 47 ms 50 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
14 67 ms 49 ms 49 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]
15 68 ms 65 ms 74 ms ae-2-2.ebr2.Miami1.Level3.net [4.69.140.141]
16 71 ms 74 ms 74 ms ae-1-100.ebr1.Miami1.Level3.net [4.69.151.253]
17 71 ms 73 ms 74 ms ae-3-5.bar1.Tampa1.Level3.net [4.69.148.214]
18 73 ms 65 ms 62 ms HIVELOCITY.bar1.Tampa1.Level3.net [4.53.172.2]
19 67 ms 67 ms 65 ms ve226.ds01-r181.tpa.hivelocity.net [206.51.235.2
27]
20 * * * Request timed out.
21 * * * Request timed out.
22 * etc
So, not sure what the hardware is (router? switch?) but I\'m guessing that\'s where the filter is filtering me out.
The effect covers all of the gunloads.com domains.