Dammit, Comcast. Get your shit together.

Miscellaneous and Personal Stuff I Must Share
1

I don’t think this is really pit worthy… but:

Running on five days now my cable internet service has been frustrating as hell.

Three examples for you, right now, not cherry picked:


C:\Documents and Settings\Brad>ping -t yahoo.com

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=120ms TTL=49
Request timed out.
Reply from 66.94.234.13: bytes=32 time=125ms TTL=50
Request timed out.
Reply from 66.94.234.13: bytes=32 time=105ms TTL=49
Reply from 66.94.234.13: bytes=32 time=96ms TTL=49
Request timed out.
Request timed out.
Reply from 66.94.234.13: bytes=32 time=95ms TTL=50
Reply from 66.94.234.13: bytes=32 time=160ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 66.94.234.13: bytes=32 time=97ms TTL=49
Reply from 66.94.234.13: bytes=32 time=95ms TTL=50
Reply from 66.94.234.13: bytes=32 time=93ms TTL=50
Reply from 66.94.234.13: bytes=32 time=94ms TTL=49

Ping statistics for 66.94.234.13:
    Packets: Sent = 17, Received = 10, Lost = 7 (41% loss),
Approximate round trip times in milli-seconds:
    Minimum = 93ms, Maximum = 160ms, Average = 108ms

41%, wow better than average



C:\Documents and Settings\Brad>ping -t yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=42ms TTL=51
Reply from 216.109.112.135: bytes=32 time=53ms TTL=51
Request timed out.
Reply from 216.109.112.135: bytes=32 time=39ms TTL=51
Reply from 216.109.112.135: bytes=32 time=43ms TTL=51
Request timed out.
Reply from 216.109.112.135: bytes=32 time=67ms TTL=51
Reply from 216.109.112.135: bytes=32 time=81ms TTL=51
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=36ms TTL=51
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=39ms TTL=51
Reply from 216.109.112.135: bytes=32 time=44ms TTL=51
Reply from 216.109.112.135: bytes=32 time=65ms TTL=51
Reply from 216.109.112.135: bytes=32 time=49ms TTL=51
Reply from 216.109.112.135: bytes=32 time=36ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=38ms TTL=51
Reply from 216.109.112.135: bytes=32 time=37ms TTL=51
Request timed out.
Reply from 216.109.112.135: bytes=32 time=630ms TTL=51
Reply from 216.109.112.135: bytes=32 time=36ms TTL=51

Ping statistics for 216.109.112.135:
    Packets: Sent = 26, Received = 16, Lost = 10 (38% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 630ms, Average = 83ms

Woohoo! That’s FUCKING GREAT!!


C:\Documents and Settings\Brad>ping -t yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Request timed out.
Reply from 216.109.112.135: bytes=32 time=50ms TTL=51
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=38ms TTL=51
Reply from 216.109.112.135: bytes=32 time=38ms TTL=51
Reply from 216.109.112.135: bytes=32 time=41ms TTL=51
Reply from 216.109.112.135: bytes=32 time=38ms TTL=51
Reply from 216.109.112.135: bytes=32 time=96ms TTL=51
Reply from 216.109.112.135: bytes=32 time=37ms TTL=51
Reply from 216.109.112.135: bytes=32 time=36ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=61ms TTL=51
Reply from 216.109.112.135: bytes=32 time=35ms TTL=51
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=37ms TTL=51

Ping statistics for 216.109.112.135:
    Packets: Sent = 20, Received = 11, Lost = 9 (45% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 96ms, Average = 46ms

Roughly average. :frowning: :rolleyes:

I’ve called them several times to complain.

But guess what? I’ve got Vonage! :smack:

So I get halfway through the menus then I get disconnected.

Between yesterday and today I’ve managed to get all the way through two whole telephone conversations, over my wife’s cell phone.

They’re sending someone out tomorrow but I know that won’t help because it isn’t on my end. I powercycle my modem, it works for 20 minutes then back to packetloss city. They’ve got some 20 year old Cisco Systems router on the fritz, in a dusty shed with no one watching it. They reboot it as often as I reboot my modem, then they stick their thumb back up their ass.

Prediction: Some “tech dude” with 5% of the experience that I have comes out, powercycles the modem, waits 10 minutes, and leaves. 10 minutes later I call back. :mad:

But I guess I’ll give them the benefit of the doubt.
The worst of it all: I’ve played three large poker tourneys in the last few days, and a ton of small ones. Everytime I get a hand I time out… I’ve been running back to my office and un-re-plugging the damn modem every other hand… and now I’m afraid to play.

No worky = no money.

2

Let me expand on that a little:

$100 buyin multi table tournement, close to the bubble. I have a larger than average stack. I flop the nut flush. Dude has a slightly smaller stack. I string him along, making perfect bets and raises to keep him involved. By fifth street, I still have the nuts. I bet half the other dude’s stack, begging for a call. At this point, three fourths of my stack is already in the pot. Dude reraises all in. I click call. Time out, get folded. Out two hands later with AQs all in preflop.

ARrrrgggghhh.

3

Once more, for the record… 90 minutes later… yes I had to reboot it again to post this:


C:\Documents and Settings\Brad>ping -t yahoo.com

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=64ms TTL=51
Reply from 216.109.112.135: bytes=32 time=49ms TTL=51
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=36ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=48ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.109.112.135:
    Packets: Sent = 21, Received = 4, Lost = 17 (80% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 64ms, Average = 49ms
Control-C
4

Note to self: keep land line.

Sorry for your troubles, hon.

5

We had a similar problem for a couple of years, that got steadily worse. We’re on Comcast, and have been since the first day they offered cable internet. Over time, the connection would drop at will and I would have to reset the modem. It got to where I was resetting it several times a day. We called them and they sent somebody out. The guy’s eyes bugged out when he saw the modem… he said, “Wow, I’ve never seen one of these. We stopped using them years ago because they’re crap.” He connected a new modem, and now our outages have decreased by, I’d say 95%. The only site where I get any time outs is the SDMB. That’s not a Comcast problem.

So maybe it’s your modem.

6

We had similar problems with Comcast. It had worked just fine for a VERY long time, but somehow something got mucked up.

The tech removed all of the extraneous splitters (we’ve got Dish Network for TV now, only the internet is over the cable line), and of course, it worked just fine.

I was of the thought that the problem was in the afore mentioned “crappy 20yo Cisco router”, but was utterly wrong… granted it’s the only time with Comcrap that I’ve been wrong about a network diagnosis (network/systems engineer as a career), but it does happen.

I’d bet that something is wrong with the line, and you’re getting a low signal level.

Just my guess of course.

7

Jeezopete, I had to look at your location to see if you were in my neighborhood.

When Comcast works, it works great. But periodically it just… gets… s.l.o.w. and unreliable.

8

Well they came out… twice…

And it’s no better :smack:
Mods: just close this please

9

Closed at the request of the OP.