Comcast cable not connecting to fdc servers

[oseao]

No not all of comcast but many of our faithful listeners have not been able to reach us as normal and they are all comcast users. Just thought i would let you all know in case you have any further insight. Heres some of the latest emails trying to sort out this dilemma:
04 07 05
The problem is between Yipe/FDC networks and Comcast.
I have put in a trouble ticket with comcast, but
I feel they will not prioritize it unless more
peoople call in. I will be contacting Yipe again
today to see what if any progress they are making
with FDC, as they have a direct line to them.
It is inevitable they will have to correct this
situation eventually. This can't just be effecting
oseao.com only.

04 08 05
I have some new information for you. My comcast
connection has been up and down for the last 3
days, I have finally got it all under control,
and guess what? I still can't get to your website.
So, I have contacted someone name Ben at Comcast
tech support and passed on all the information,
and actually had him try the website on his
workstation, which worked, and then on a comcast
connection, which did not. So, the problem has
been officially verified by an employee of Comcast
and is now going to be escalated to uppper network
support. I have given them my cel to contact me
regarding the failing ip adress.

[mikron15]

I know there have been a high DDOS volume on the FDC line past few days. They have been co-ordinating with the upstream provider to filter it out.Probably they blocked a class C temp or perm. ip to reduce the Ddos Effect.

Have you tried contacting FDC helpdesk or bummer to see if any such bans exist at this moment?

[faqall]

well weeks ago people from comcast couldnt connect to my fdc servers... and they still cant

[ChronoCross]

90% of all cable and dsl users are hacked. so dealing with dos attacks are difficult and sometimes require banning of entire huge blocks.

[ChronoCross]

well this might also be the problem.....might take up to like 7-14 days to be fixed in full

http://www.computerworld.com/managementtopics/outsourcing/isptelecom/story/0,10801,100960,00.html?source=x10

comcasts DNS servers aparently died HAHAHAH

[oseao]

Heres a note from one of my freinds helping me with this. Any ideas would be great. I am starting up a ticket with fdc right now:
I got the e-mail that this issue was tracked down to Comcast and that
they were investigating. That's the wrong path. I've got multiple
records of people who's connection is dying right before it gets to
your website. This is at a place outside of Comcast's network and
there is nothing they can do to solve it, nor is it anything that they
are causing. You need to speak with your website provider and give
them the ip address and tell them its blocking some Comcast modems.

209.120.155.14

This is the offending address. In the network, its right before your
webserver. I saw a mention of some company in Chicago handling that.
You need to speak with them. This is something they should be able to
resolve immediately.

[tkam]

I'm on comcast and haven't had any problems connecting to my fdc box. That IP address is the connection to Yipes I believe, so they are probably blocking some IP's. It's probably best to start a ticket and give the fdc techs that IP address so they can pass it along to Yipes.

[oseao]

Let me clarify, the website can be reached
from all networks except for Comcast customers.
This has been verified by MANY people on the
comcast network. Here is tracert done from
the comcast network.

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

C:\Documents and Settings\mame>tracert www.oseao.com

Tracing route to oseao.com [67.159.26.86]
over a maximum of 30 hops:

1 * * * Request timed out.
2 75 ms 64 ms 21 ms 12.244.21.1
3 95 ms 18 ms 29 ms 12.244.64.65
4 17 ms 15 ms 64 ms 12.118.60.9
5 63 ms 15 ms 64 ms 12.123.44.194
6 63 ms 14 ms 43 ms 12.123.44.177
7 33 ms 91 ms 16 ms so-3-2-0.gar1.Seattle1.Level3.net [4.68.127.109]

8 49 ms 41 ms 44 ms so-0-0-0.gar2.Seattle1.Level3.net [209.247.8.162
]
9 37 ms 112 ms 39 ms so-7-0-0.mp2.Seattle1.Level3.net [64.159.1.165]

10 130 ms 61 ms 62 ms as-2-0.bbr1.Chicago1.Level3.net [64.159.4.225]
11 87 ms 86 ms 65 ms ge-1-1-53.car1.Chicago1.Level3.net [4.68.101.66]

12 113 ms 194 ms 120 ms 4.79.72.46
13 163 ms 85 ms 103 ms 209.120.155.14
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.


As you can see the last hop is at fdc server.

[oseao]

this is definetely not all comcast people. just a chunk considering many of my random friends on comcast can not get in. maybe 30% of them. thanks for any help

[faqall]

here are some from clients complaining they cant connect (a few weeks old too)

1 * * * Request timed out.
2 10 ms 7 ms 9 ms 24-205-1-165.oc-nod.charterpipeline.net [24.205.
1.165]
3 8 ms 7 ms 9 ms 24-205-1-137.oc-nod.charterpipeline.net [24.205.
1.137]
4 8 ms 9 ms 11 ms bur-edge-02.inet.qwest.net [65.114.177.133]
5 10 ms 17 ms 8 ms bur-core-03.inet.qwest.net [205.171.13.85]
6 19 ms 17 ms 18 ms svl-core-03.inet.qwest.net [205.171.14.122]
7 19 ms 22 ms 19 ms svx-core-02.inet.qwest.net [205.171.14.82]
8 20 ms 18 ms 19 ms sjp-brdr-01.inet.qwest.net [205.171.214.138]
9 25 ms 53 ms 19 ms so-2-0-0.edge1.SanJose1.Level3.net [209.245.146.
229]
10 19 ms 19 ms 21 ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141
]
11 69 ms 84 ms 66 ms ae-0-0.bbr2.Chicago1.Level3.net [64.159.1.34]
12 70 ms 70 ms 67 ms ge-1-2-54.car1.Chicago1.Level3.net [4.68.101.98]

13 80 ms 75 ms * 4.79.72.42
14 74 ms 89 ms 72 ms 209.120.176.2
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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.




and an attached image:


no firewalls running nothing... im clueless

[mikron15]

Have you guys tried getting in touch with FDC helpdesk? If yes, what did they say?
Bummer, care to shed some light on this issue?

[faqall]

i did twice. they said it was problem on sever when it was brand new w/ nothing on it.

[tkam]

From the tracert's posted it sure looks like it was/is something with the Yipes connection.

[tzulo]

It IS a server issue. I've delt with this exact same issue, with comcast clients as well for my server.

Also, I'm on comcast at home and wasn't able to connect to my dedicated box just like yours in the same /24 even.

The reason: your netmask/broadcast is set improperly.
Make sure it is set to gw of 67.159.26.1 and netmask of 255.255.255.0 and broadcast of: 67.159.26.255


If you have it set incorrectly, the server will try to think anything on 67.x.x.x is on the local subnet and will ignore anything from a 67.x.x.x address (such as comcast).

Also, have your clients ping other 67.159.26.x addresses.

67.159.26.82 is pingable, which means it I can reach that box fine, but not your .86 box because your network settings (or firewall?) is set wrong. It's not FDC's network.

-tzulo
If your network settings look okay, have FDC reset it for you to make sure. Also check your routing table: netstat -drn

PM me if you can't get it working still.

[Jahizzo]

hmm but how comes more than one people have this issue with the mentioned router??

[faqall]

ill re open my ticket with fdc and see what they think about what tzulo said. ty much :)

[tzulo]

Any word yet?

[mikron15]

Dunno if this is any help
http://www.dslreports.com/shownews/62494