[Speed] Wierd Upload issues in Abingdon MD in Comcast HSI

[Speed] Wierd Upload issues in Abingdon MD in Comcast HSI http://www.dslreports.com/forum/r14944847 en Sun, 29 Nov 2009 01:45:07 EDT Sun, 29 Nov 2009 01:45:07 EDT Re: [Speed] Wierd Upload issues in Abingdon MD http://www.dslreports.com/forum/remark,14950845 divefox : Also, here is some information to note: The ATT T1 maxes out at 1544 kbps. Period. T1s just don't go any faster.

The Cavalier Telecom endpoint seems to be on a 3 mbit DSL connection.

Those two rates being low is normal.

Still, drop me a PM.]]> http://www.dslreports.com/forum/remark,14950845 Mon, 05 Dec 2005 10:46:37 EDT Re: [Speed] Wierd Upload issues in Abingdon MD http://www.dslreports.com/forum/remark,14950811 divefox : I'm in Aberdeen. PM me; I have a couple of ideas I want to run through, but I'm not too keen on posting my IP here.]]> http://www.dslreports.com/forum/remark,14950811 Mon, 05 Dec 2005 10:41:44 EDT Re: [Speed] Wierd Upload issues in Abingdon MD http://www.dslreports.com/forum/remark,14946260 covaro : Snip from blog post:
»www.notmyblog.com/2005/12/04/com···-part-3/

*snip*
Now for the sake of comparison (I might take screen caps of these later if I feel up to dealing with it… I’m just getting tired of this crap and Comcast insisting I have an issue with my stuff) here are the connections ala carte.

* Bel Air MD (Comcast). 4952K Down 351K Up
* Columbia MD (Comcast). 2677K Down 707K Up
* North East MD (AT&T T1). 1224K Down 1372K Up
* Baltimore MD (CavTel). 2240K Down 614K Up

*snip*
*snip*
At this point I’ve just been leaving my laptop hooked up to the VPN at my Dad’s house so I have some upload or using the Verizon air card I have. Sad part is, both work better at this point for doing anything (besides straight download) than my straight Comcast connection. Here at home my Verizon card is getting 222K Down and 115K Up. Absolutely pathetic when your wireless card is faster than your cable connection.
*snip*

-Cov]]> http://www.dslreports.com/forum/remark,14946260 Sun, 04 Dec 2005 17:23:03 EDT [Speed] Wierd Upload issues in Abingdon MD http://www.dslreports.com/forum/remark,14944847 covaro : To start this off read the following two posts on my blog I've made previously. These both follow my troubleshooting procedures I've gone through up to this point to confirm the fact that my upload is borked (I can't use it at all, any significant traffic just doesn't happen) is not the result of my computers or home network and lies somewhere outside of my realm of influence.

»www.notmyblog.com/2005/12/02/i-hate-comcast/
»www.notmyblog.com/2005/12/02/mor···t-thing/

Now, after reading this you are mostly up to date. I just posted the following information on the Comcast Forums as well.

My most interesting findings of late. Decided to perform speed tests through 4 different VPNs I have access to. Seeing as I can still not complete Speed Tests through my Comcast connection. Set each VPN to pass all traffic through the remote gateway so as to use their bandwidth to send/recieve traffic. Results as below:

Test 1
»www.flickr.com/photos/covaro/70116067/
From Abingdon MD (Comcast) to Bel Air MD (Comcast)
358K Down 369 Down

Tracert for this connection (Note, end point does not respond to pings)

Tracing route to pcp0011461215pcs.chrchv01.md.comcast.net [69.250.137.186]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.150.1
2 11 ms 10 ms 10 ms bsr01-a-rtr.chrchv01.md.comcast.net [69.250.136.1]
3 * * * Request timed out.

Trace complete.

Test 2
»www.flickr.com/photos/covaro/70116047/
From Abingdon MD (Comcast) to Columbia MD (Comcast)
1449K Down 2K Up
Tracert to the endpoint:

Tracing route to vpn.geekcenter.us [70.88.229.106]

over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.150.1

2 10 ms 9 ms 10 ms 73.139.80.1

3 11 ms 9 ms 9 ms ge-1-22-ur02.churchville.md.bad.comcast.net [68.87.132.253]

4 9 ms 9 ms 12 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net [68.87.128.226]

5 11 ms 10 ms 9 ms te-7-2-ur02.whitemarsh.md.bad.comcast.net [68.87.129.166]

6 11 ms 9 ms 22 ms te-9-2-ur01.whitemarsh.md.bad.comcast.net [68.87.129.169]

7 20 ms 9 ms 9 ms te-9-4-ur01.essex.md.bad.comcast.net [68.87.129.5]

8 27 ms 10 ms 10 ms te-9-3-ur01.catonsville.md.bad.comcast.net [68.87.128.205]

9 12 ms 11 ms 11 ms te-9-3-ur01.ellicttcty.md.bad.comcast.net [68.87.128.194]

10 14 ms 15 ms 12 ms te-9-1-ur01.elkridge.md.bad.comcast.net [68.87.128.249]

11 14 ms 10 ms 13 ms te-9-3-ur02.howardcounty.md.bad.comcast.net [68.87.128.254]

12 13 ms 13 ms 12 ms ge-15-0-bsr01.howardcounty.md.bad.comcast.net [68.87.131.94]

13 22 ms 19 ms 20 ms mail.geekscenter.us [70.88.229.106]

Test 3
»www.flickr.com/photos/covaro/70116025/
From Abingdon MD (Comcast) to North East MD (AT&T)
1373 Down 37K Up

Tracert to the endpoint:

Tracing route to 12.26.81.34 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.150.1

2 32 ms 10 ms 11 ms 73.139.80.1

3 16 ms 9 ms 9 ms ge-1-22-ur02.churchville.md.bad.comcast.net [68.87.132.253]

4 12 ms 9 ms 9 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net [68.87.128.226]

5 11 ms 11 ms 21 ms 68.87.16.141

6 16 ms 15 ms 15 ms 12.118.149.21

7 30 ms 20 ms * tbr2-p014001.n54ny.ip.att.net [12.123.3.14]

8 19 ms 21 ms 19 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]

9 23 ms 19 ms 18 ms gbr6-p40.wswdc.ip.att.net [12.122.11.190]

10 90 ms 199 ms 199 ms ar10-p3110.wswdc.ip.att.net [12.123.8.206]

11 25 ms 23 ms 23 ms 12.127.42.158

12 33 ms 21 ms 21 ms 12.26.81.34

Test 4
»www.flickr.com/photos/covaro/70116011/
From Abingdon MD (Comcast) to Baltimore MD (CavTel)
216K Down 358K Up

Tracert to endpoint (does not responnd to pings):

Tracing route to static-66-173-138-175.dsl.cavtel.net [66.173.138.175]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.150.1

2 16 ms 8 ms 7 ms 73.139.80.1

3 14 ms 10 ms 9 ms ge-1-22-ur01.churchville.md.bad.comcast.net [68.87.132.249]

4 9 ms 10 ms 9 ms te-9-1-ur02.churchville.md.bad.comcast.net [68.87.128.222]

5 11 ms 10 ms 8 ms te-8-4-ar01.whitemarsh.md.bad.comcast.net [68.87.128.226]

6 12 ms 9 ms 9 ms 68.87.16.141

7 17 ms 23 ms 13 ms 12.118.149.13

8 29 ms 17 ms 21 ms tbr2-p014001.n54ny.ip.att.net [12.123.3.14]

9 21 ms 19 ms 21 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]

10 20 ms 18 ms 19 ms gar1-p360.abnva.ip.att.net [12.123.217.18]

11 83 ms * * 12.118.132.6

12 32 ms 31 ms 44 ms atm20-1-oc3.core-01.rich.va.cavtel.net [64.83.47.2]

13 43 ms 44 ms 45 ms 64.83.67.106

14 * * * Request timed out.

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.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete

I might log in to each of these network later and perform a speed test from those particular places just to show their connections are peachy. I dunno, we'll see, I am just getting tired of troubleshooting Comcast's issue for them. Maybe I'll try calling them again later and see if I can get a CSR this time that can understand issues that don't show up on their little sheet that tells them what they need to do.

This is getting to the point of unacceptable. Basically to use the internet now I have to connect to my Dad's house via a VPN if I need to upload anything. I'm lucky if mail goes from my house (with attachments) in less than a couple hours. The thing that I don't get is regular surfing and email without attachments works fine. It's if I try to start passing any real traffic on the up side of my connection. Has Comcast started traffic shaping or something and not told anyone?

Any help here would be appreciated. I'm just getting frustrated to the point I'm about ready to start yelling at someone till someone listens. Either that or I might bite the bullet and get a new ISP if this is resolved soon.

-Cov]]> http://www.dslreports.com/forum/remark,14944847 Sun, 04 Dec 2005 13:35:05 EDT