Beaker wrote:
... Wish I could fix the real problem. I don't remember correctly but I think if you use IP config in command mode using local IPS you will find the exact server where you are getting blocked. I cannot find a way to contact this server....
From the command prompt use
tracert You will see someting like the example below. The trace route will stop at the router blocking you. Often during a DDOS attack, like they had last week, the server will key on repeated attempts to access a site and add the ip address to the firewall.
Interesting that the last router in the chain fails to identify itself in this example.
tracert woodalls.com
8 417 ms 296 ms 296 ms 216.156.16.132.ptr.us.xo.net [216.156.16.132]
9 110 ms 104 ms 104 ms 207.88.12.168.ptr.us.xo.net [207.88.12.168]
10 105 ms 106 ms 104 ms 207.88.12.165.ptr.us.xo.net [207.88.12.165]
11 124 ms 104 ms 105 ms 207.88.12.188.ptr.us.xo.net [207.88.12.188]
12 110 ms 106 ms 104 ms 216.156.16.175.ptr.us.xo.net [216.156.16.175]
13 105 ms 105 ms 104 ms 67.106.55.46.ptr.us.xo.net [67.106.55.46]
14 * * * Request timed out.
15 116 ms 112 ms 113 ms 198.1.26.72
Trace complete.
If you want to know what your IP address is
Click Here