CrazyLEG
join:2002-06-13
Richardson, TX
| DFW Area (Richardson) PL/Ping Issues *HELP*
Over the past 3 weeks I have been getting significant ping/PL issues. These issues accure at anytime all day long, but it's really noticable during peak times.
I have called the Comcast Support ppl, only to get the reply that the pings are "within" normal limits.
Is anyone else in my area having issues?
It's very frustrating to feel like I have taken a step back to 56k preformance on a cable system.
Here are some snapshots of my issues taken a few moments ago.
 |
|
Wildwusel
Premium
join:2001-12-04
Richardson, TX
| This is what I just got.
C:\Documents and Settings\Christa>ping www.dslreports.com
Pinging dslreports.com [209.123.109.175] with 32 bytes of data:
Reply from 209.123.109.175: bytes=32 time=89ms TTL=49
Reply from 209.123.109.175: bytes=32 time=57ms TTL=49
Reply from 209.123.109.175: bytes=32 time=60ms TTL=49
Reply from 209.123.109.175: bytes=32 time=55ms TTL=49
Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 89ms, Average = 65ms |
|
CrazyLEG
join:2002-06-13
Richardson, TX
| reply to CrazyLEG
I which I had a steady ping w/o all the PL.
Comcast said they would roll a truck to my house to see if the problem was their system.
They told me they might charge me for the truck roll if they don't "see" an issue.
Sad...they feel they have to treat there customers like that.
Too bad I'm too far from a CO for DSL |
|
Nerdtalker
Working Hard, Or Hardly Working?
Premium,MVM
join:2003-02-18
Tucson, AZ
clubs:
| reply to CrazyLEG
I've always had some issues, here is a current tracert.
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 11 ms 11 ms 11 ms 10.186.80.1
2 10 ms 14 ms 11 ms 172.30.28.209
3 11 ms 11 ms 12 ms 172.30.28.238
4 14 ms 14 ms 17 ms POS2-0.hsa2.phx1.Level3.net [63.214.170.37]
5 14 ms 14 ms 15 ms ge-6-1-1.mp1.Phoenix1.Level3.net [209.247.9.201]
6 32 ms 30 ms 32 ms so-1-0-0.mp2.SanJose1.level3.net [209.247.9.182]
7 32 ms 30 ms 32 ms so-7-0-0.gar2.SanJose1.Level3.net [64.159.1.78]
8 31 ms 35 ms 31 ms so-7-0-0.edge1.SanJose1.level3.net [209.244.3.14
2]
9 31 ms 32 ms 34 ms williams-level3-oc12.SanJose1.Level3.net [209.0.
227.2]
10 32 ms 31 ms 31 ms sntcca1wcx1-pos5-0.wcg.net [64.200.240.129]
11 90 ms 89 ms 87 ms snfcca1wcx3-oc48.wcg.net [64.200.151.94]
12 90 ms 89 ms 95 ms dnvrco1wcx2-pos3-0.wcg.net [64.200.240.93]
13 88 ms 87 ms 87 ms chcgil1wcx3-pos15-0.wcg.net [64.200.210.65]
14 88 ms 88 ms 90 ms nycmny2wcx3-oc48.wcg.net [64.200.240.38]
15 90 ms 89 ms 90 ms nycmnyhlce1-oc48.wcg.net [64.200.87.110]
16 88 ms 89 ms 89 ms nycmny2lce1-netaccess-atm.wcg.net [64.200.86.150
]
17 91 ms 105 ms 90 ms 1187.at-0-1-0.gbr1.oct.nac.net [209.123.11.150]
18 90 ms 116 ms 91 ms 0095.gi-1-1.msfc1.oct.nac.net [64.21.102.2]
19 91 ms 89 ms 90 ms www.dslreports.com [209.123.109.175] |
|
JTRockville
Data Ho
Premium,MVM
join:2002-01-28
Rockville, MD
clubs:
 ·LINGO
 ·Sprint Mobile Broa..
 ·surpasshosting
 ·Verizon FIOS
| reply to CrazyLEG
Have you checked for spyware?
See this topic for some good suggestions:
Re: Cable modem feels more like a 56k
What kind of modem do you have?
Have you checked your signals when you see loss? |
|
CableUZR
Cuidado, Hay Llamas
join:2003-02-04
Mount Holly, NJ
clubs:
| reply to CrazyLEG
Your trace is slow from the get-go. I'd start by checking the health of your PC (spyware, virii, trojans etc.), then check your cable modem signals. If there's a problem on the Comcast side, it looks like it's starting at the CMTS. You should never see 115-320ms times to your CMTS. (Hop one on your trace)
(here's mine which looks much more normal...):
C:\>tracert -d dslreports.com
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 31 ms 10 ms 16 ms 10.117.96.1
2 10 ms 16 ms 16 ms 172.30.119.81
3 10 ms 16 ms 10 ms 172.30.119.123
...etc.
Uzr |
|
OmenQ
Spazz
Premium
join:2003-03-21
Continuum
clubs:
| reply to CrazyLEG
Ignore my first hop (router) but here's mine... I'm in North Dallas, just south of the Bush Turnpike.
Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 * * * Request timed out.
2 13 ms 13 ms 14 ms 12-238-200-1.client.attbi.com [12.238.200.1]
3 15 ms 13 ms 11 ms 12.244.122.1
4 13 ms 12 ms 11 ms 12.244.69.22
5 13 ms 14 ms 12 ms 12.244.73.6
6 12 ms 12 ms 11 ms gbr6-p30.dlstx.ip.att.net [12.123.17.54]
7 15 ms 16 ms 13 ms tbr2-p013701.dlstx.ip.att.net [12.122.12.89]
8 29 ms 27 ms 27 ms 12.122.10.125
9 35 ms 36 ms 34 ms tbr2-p013701.cgcil.ip.att.net [12.122.10.9]
10 34 ms 34 ms 34 ms tbr1-p012501.cgcil.ip.att.net [12.122.9.133]
11 55 ms 54 ms 54 ms tbr1-p013601.n54ny.ip.att.net [12.122.10.57]
12 51 ms 52 ms 51 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
13 52 ms 53 ms 53 ms att.ge-0-0-0.gbr1.nwr.nac.net [12.119.140.30]
14 56 ms 53 ms 56 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
15 56 ms 55 ms 54 ms 0095.gi-1-1.msfc1.oct.nac.net [64.21.102.2]
16 54 ms 57 ms 55 ms www.dslreports.com [209.123.109.175]
Trace complete.
--
Now the world is gone I'm just one, oh god help me. Hold my breath as I wish for death, oh please god help me..... |
|
CrazyLEG
join:2002-06-13
Richardson, TX
| I'm Located south of 190 between Plano Rd & Jupiter.
Images taken tonight on the ongoing issues with my Comcast Cable:
[text was edited by author 2003-06-03 23:00:06] |
|
CrazyLEG
join:2002-06-13
Richardson, TX
| reply to CableUZR
quote:
Posted by Tomodachi Takusan Ureshii Na
Your trace is slow from the get-go. I'd start by checking the health of your PC (spyware, virus, trojans etc.), then check your cable modem signals. If there's a problem on the Comcast side, it looks like it's starting at the CMTS. You should never see 115-320ms times to your CMTS. (Hop one on your trace)
I ran spyware and found a couple of programs. Cleaned those. Did the normal clear cache/temp files/etc.
Did a file compression on my HD. Basically all the normal cleanups on a computer.
My PC is running fine with no "health" issues, but when it comes to I-Net connection, there is where the problem arises.
I ran some ping tests on off-peak times today, and though the packet losses were down and pings were stable, I was still encountering packet losses. Once Peak Hours are in effect...well as the images show, my situation gets worse. |
|
