| reply to Robotics
Re: [DNS] Comcast blocking site? Hi.
Site torrenty.org had some issues with "hackers" so now there are some firewall rules which blocks lots of IP that are outside of Poland. If You are having problem with connecting to torrenty.org you should get a polish proxy or polish vpn.
»www.mydevil.net/oferta,irc1.html - this should work. |
|
 JohnInSJPremium
join:2003-09-22
San Jose, CA
 ·PHONE POWER
 ·Comcast
| reply to Kommie
said by Kommie:Then is it Comcast or them ?
"Them"
Traceroute gets well out of comcast's network, but the packets die at the provider in the Ukraine. That's where (one would guess) their firewall is, and where (one would guess) the bad (or fantastic) firewall rule is that's dropping packets from a large but not complete swath of the US, based on ip address.
Once your packet leaves comcast's network and enters the wider internet, there isn't anything comcast can do.
--
My place : »www.schettino.us |
|
 RandyPremium
join:2006-04-25
Springfield, IL | reply to Kommie
Loads right up tethered on ATT Wireless.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\owner>ping torrenty.org
Pinging torrenty.org [62.149.27.204] with 32 bytes of data:
Reply from 62.149.27.204: bytes=32 time=257ms TTL=46
Reply from 62.149.27.204: bytes=32 time=260ms TTL=46
Reply from 62.149.27.204: bytes=32 time=262ms TTL=46
Reply from 62.149.27.204: bytes=32 time=235ms TTL=46
Ping statistics for 62.149.27.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 235ms, Maximum = 262ms, Average = 253ms
C:\Users\owner>tracert torrenty.org
Tracing route to torrenty.org [62.149.27.204]
over a maximum of 30 hops:
1 347 ms 388 ms 437 ms martin1.cc.colocall.com [62.149.27.204]
Trace complete.
--
"In this business, by the time you realize you're in trouble, it's too late to save yourself. Unless you're running scared all the time, you're gone."
-Bill Gates |
|
KearnstdElf WizardPremium
join:2002-01-22
Mullica Hill, NJ | reply to Kommie
Loads right up on VZW 3G, times out on Comcast.
pretty clear there is a loss somewhere but not in comcast.
--
[65 Arcanist]Filan(High Elf) Zone: Broadband Reports |
|
 NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro
·Comcast Business..
·Vonage
 ·Cingular Wireless
·Comcast
2 edits | reply to Randy
said by Randy:Loads right up tethered on ATT Wireless...
Apparently that depends upon from where you make your AT&T Wireless connection. From my location, I am still blocked whether I use AT&T DSL, Comcast HSI, or AT&T Mobility.
C:\>use-comcast.cmd
Pinging 192.168.9.10 with 32 bytes of data:
Reply from 192.168.9.10: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.9.10:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.10 metric 10
You are now using the Comcast Business Class connection!
C:\>tracert torrenty.org
Tracing route to torrenty.org [62.149.27.204]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ap2.dcs-net [192.168.9.10]
2 1 ms <1 ms <1 ms host6.dcs-net.net [75.146.8.46]
3 22 ms 78 ms 19 ms 96.191.160.1
4 9 ms 8 ms 8 ms xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
5 15 ms 8 ms 9 ms xe-11-3-0-0-sur01.murfreesboro.tn.nash.comcast.net [68.85.174.21]
6 40 ms 11 ms 15 ms xe-4-1-1-0-ar03.nashville.tn.nash.comcast.net [68.86.176.101]
7 27 ms 27 ms 44 ms pos-2-9-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.93.189]
8 25 ms 44 ms 24 ms pos-1-0-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.34]
9 23 ms 24 ms 26 ms ix-0-2-2-0.tcore2.ct8-chicago.as6453.net [206.82.141.81]
10 141 ms 166 ms 178 ms 64.86.79.2
11 182 ms 138 ms 143 ms if-8-2.tcore1.ttt-scarborough.as6453.net [216.6.125.5]
12 138 ms 146 ms 140 ms if-4-2.tcore1.mtt-montreal.as6453.net [64.86.31.17]
13 47 ms 44 ms 50 ms if-10-0-0-1896.mcore3.mtt-montreal.as6453.net [216.6.114.101]
14 136 ms 137 ms 144 ms if-10-1-0-0.tcore1.pvu-paris.as6453.net [80.231.153.17]
15 145 ms 136 ms 157 ms if-4-2.tcore1.fr0-frankfurt.as6453.net [80.231.153.9]
16 149 ms 143 ms 162 ms vlan1656.icore1.f2c-frankfurt.as6453.net [195.219.50.90]
17 187 ms 137 ms 137 ms vlan541.icore1.f2c-frankfurt.as6453.net [195.219.148.74]
18 173 ms 179 ms 181 ms xe-2-2-1.3003.quoll.as13249.net [213.133.160.253]
19 170 ms 188 ms 187 ms gw.itsystems-world.ll.colocall.com [62.149.20.77]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\>use-att.cmd
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=58ms TTL=253
Ping statistics for 192.168.1.254:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 58ms, Average = 58ms
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.9 metric 10
You are now using the Windcrest AT&T backup connection!
C:\>tracert torrenty.org
Tracing route to torrenty.org [62.149.27.204]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms ps1.dcs-net [192.168.9.9]
2 4 ms 3 ms 6 ms gw4.dcs-net [192.168.8.254]
3 * 13 ms 8 ms 192.168.1.254
4 164 ms 34 ms 127 ms adsl-98-87-117-1.bna.bellsouth.net [98.87.117.1]
5 131 ms 44 ms 307 ms 70.159.210.120
6 36 ms 246 ms 286 ms 70.159.210.122
7 372 ms 306 ms 308 ms 70.159.210.119
8 380 ms 72 ms 36 ms 12.81.32.144
9 805 ms 156 ms 278 ms 12.81.32.41
10 457 ms * * 74.175.192.198
11 53 ms 93 ms * cr1.nsvtn.ip.att.net [12.122.148.14]
12 * 606 ms * cr2.attga.ip.att.net [12.122.28.105]
13 58 ms 45 ms 152 ms attga01jt.ip.att.net [12.122.80.221]
14 * * * Request timed out.
15 50 ms 60 ms 85 ms if-7-0-0-60.har1.a56-atlanta.as6453.net [64.86.8.17]
16 190 ms 203 ms 198 ms if-5-0-0-12.tcore1.aeq-ashburn.as6453.net [66.198.154.65]
17 279 ms 410 ms 417 ms if-2-2.tcore2.aeq-ashburn.as6453.net [216.6.87.1]
18 606 ms 361 ms 606 ms if-6-871.tcore1.pvu-paris.as6453.net [216.6.87.74]
19 388 ms * * if-4-2.tcore1.fr0-frankfurt.as6453.net [80.231.153.9]
20 * * 388 ms vlan1656.icore1.f2c-frankfurt.as6453.net [195.219.50.90]
21 * * 567 ms vlan541.icore1.f2c-frankfurt.as6453.net [195.219.148.74]
22 730 ms * * xe-1-3-0.3001.quoll.as13249.net [213.133.160.245]
23 * 569 ms 186 ms gw.itsystems-world.ll.colocall.com [62.149.20.77]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\>rasdial "AT&T Mobility"
Connecting to AT&T MOBILITY...
Verifying username and password...
Registering your computer on the network...
Successfully connected to AT&T MOBILITY.
Command completed successfully.
C:\>tracert torrenty.org
Tracing route to torrenty.org [62.149.27.204]
over a maximum of 30 hops:
1 * * * Request timed out.
2 249 ms 279 ms 279 ms 172.26.248.2
3 345 ms 289 ms 299 ms 172.18.166.34
4 227 ms 298 ms 329 ms 172.18.193.79
5 1053 ms 226 ms 153 ms 172.18.193.2
6 139 ms 159 ms 139 ms 172.18.193.228
7 135 ms 159 ms 139 ms 209.183.38.226
8 135 ms 139 ms 139 ms 172.18.213.1
9 135 ms 139 ms 139 ms 12.88.97.13
10 135 ms 139 ms 139 ms cr1.attga.ip.att.net [12.123.22.6]
11 137 ms 149 ms 139 ms attga01jt.ip.att.net [12.122.80.185]
12 127 ms 139 ms 139 ms 192.205.36.202
13 135 ms 339 ms 139 ms if-5-0-0-50.har1.A56-Atlanta.as6453.net [64.86.9.13]
14 241 ms 269 ms 249 ms if-3-1200.tcore1.AEQ-Ashburn.as6453.net [66.198.154.33]
15 274 ms 279 ms 259 ms if-2-2.tcore2.aeq-ashburn.as6453.net [216.6.87.1]
16 259 ms 269 ms 259 ms if-6-871.tcore1.pvu-paris.as6453.net [216.6.87.74]
17 230 ms 259 ms 259 ms if-5-2.tcore1.FR0-Frankfurt.as6453.net [80.231.153.122]
18 254 ms 249 ms 269 ms vlan1656.icore1.f2c-frankfurt.as6453.net [195.219.50.90]
19 249 ms 269 ms 249 ms vlan541.icore1.f2c-frankfurt.as6453.net [195.219.148.74]
20 289 ms 289 ms 289 ms xe-2-2-0.3002.quoll.as13249.net [213.133.160.249]
21 319 ms 279 ms 489 ms gw.itsystems-world.ll.colocall.com [62.149.20.77]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\>rasdial "AT&T Mobility" /disconnect
Command completed successfully.
C:\>use-comcast.cmd
Pinging 192.168.9.10 with 32 bytes of data:
Reply from 192.168.9.10: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.9.10:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.10 metric 10
You are now using the Comcast Business Class connection!
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower |
|
Mele20Premium
join:2001-06-05
Hilo, HI
kudos:4 | reply to Kommie
Road Runner users in Hawaii are also apparently blocked. I get "error connecting to site" when I try to go there.
I used Ping Plotter's TCP engine not the ICMP engine. Ping Plotter TCP engine should be able to reach the site. I've never seen it, in all the years I've had Ping Plotter Pro, not be able to reach a site that was firewalled if the TCP engine was used.
I think that either the site IS down OR SPECIFIC IP's are being fully blocked (even from TCP ping). I can see that site blocking Comcast and Road Runner (SOPA/PIPA).
--
When governments fear people, there is liberty. When the people fear the government, there is tyranny. Thomas Jefferson |
|
|
|
 beachintechThere's sand in my tool bagPremium
join:2008-01-06
kudos:5
·Comcast
| reply to Robotics
said by Robotics:Care to point out where he is "immediately blaming" comcast. What I see is the op asking a question and not pointing any fingers. So happens he is on comcast or he wouldn't be in this area of the site. Sure.
said by Kommie:Is Comcast Blocking ?
;) That's a fairly direct finger, first question asked too.
--
Ex-Tech at the Beach.
I speak for myself, not my former employer. |
|
NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast
2 edits | said by beachintech:said by Robotics:Care to point out where he is "immediately blaming" comcast. What I see is the op asking a question and not pointing any fingers. So happens he is on comcast or he wouldn't be in this area of the site. Sure. said by Kommie:Is Comcast Blocking ?
;) That's a fairly direct finger, first question asked too. That is simply a question from someone who is not a network engineer/technician (the simple fact that the topic uses the "DNS" tag is proof that the OP knows nothing about networking). If the OP were pointing a finger, the statement would have been "Why is Comcast blocking site?" (and while that is often the title of threads in this forum, that is not the case here).
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower |
|
| reply to NetFixer
Re: [DNS] Comcast blocking site? Why do you guys keep using the word "blocked"
Nobody's blocking it... |
|
NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast
2 edits | said by nysports4evr:Why do you guys keep using the word "blocked"
Nobody's blocking it...
I have not said that the site in question is being blocked by Comcast (or AT&T, since I can't reach it in an AT&T connection either). I have however, pointed out that it is not accessible from more than just Comcast connections, so in that respect my access to it is indeed blocked.
It is quite possible that they (and/or their hosting service) are blocking incoming traffic from a large number of IP address ranges (and not just Comcast IP addresses). I sometimes have to do it for my servers when they are being attacked from multiple IP address ranges. A temporary wide area block stops the DDoS (or the attack vector du jour), and that allows time to go through the logs and do selective blocking at my leisure. I suspect the site in question has recently been attacked and is in defensive mode (as was reported earlier in this thread).
At this time, I can not reach torrenty.org (martin1.cc.colocall.com) [62.149.27.204] via ICMP, http, ftp, smtp, telnet, or any other common service used by on-line servers from either an AT&T DSL or 3G connection or from a Comcast connection.
This site's server can not reach it either:
And just to maks sure that this site's "siteshot" feature is working, here is a "siteshot" of www.google.com:
OTOH, Netcraft can see the web site just fine at this time, so that indicates that some selective blocking (intentional or not) is being done by someone (and my money is on a self imposed inbound block by the site or the hosting company).
Also, I think that someone else pointed out that forum.torrenty.org is accessible (and I can indeed access that server), but that server is not even located on the same continent, much less the same server farm.
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower |
|
 CjaicemanPremium,MVM
join:2004-10-12
Parker, CO
kudos:2 | reply to Kommie
Works just fine on Verizon Wireless, unreachable on Comcast and Qwest. |
|
 jkj860The Final Frontier
join:2002-01-10
Valparaiso, IN
·Comcast Digital ..
·Comcast
| reply to Kommie
Works here on Comcast:
said by Kommie:I am unable to access the following website.
»torrenty.org
Is Comcast Blocking ?
--
I know you think you understand what you thought I said, but I am not sure you realize what you heard is not what I meant. Nixon |
|
 RoboticsSee You On The Dark SidePremium
join:2003-10-23
Louisa, VA
·Verizon Wireless..
·Comcast
| reply to NetFixer
said by NetFixer: That is simply a question from someone who is not a network engineer/technician (the simple fact that the topic uses the "DNS" tag is proof that the OP knows nothing about networking). If the OP were pointing a finger, the statement would have been "Why is Comcast blocking site?" (and while that is often the title of threads in this forum, that is not the case here).
Thank you for wording it better than I probably would have.
Indeed, it was a simple question.
--
Long you live and high you fly, and smiles you'll give and tears you'll cry,
and all you touch and all you see, is all your life will ever be. |
|
