SG Broadband Community

Posted: **Fri Aug 17, 2001 2:20 am**

i have a problem with my cable. my ping is very high. so i contacted tech support online. well after doing several tests all the guy did was give me a trouble ticket and tell me they would call within 1-2 days. what a waist of time.

well i hope they can fix it. im not going to pay $40 a month for something that doesnt serve any purpose to me. how can i play games with a high ping. i would probably do better with 56k right now.

Posted: **Fri Aug 17, 2001 2:22 am**

Ya i recently had trouble with them.. my internet gets disconnected a lot. they called back the next day around 5:00.

You can just call them tomrrow whenever you want and they'le transfer you to a tech

Posted: **Fri Aug 17, 2001 2:53 am**

welcome to cable tech service

, from my experiance with cable techs, they suck! my advice is to learn as much as you can about your modem, your connection and so on. hopefully learning as much as you can will prevent you from having to call them in the future.

Posted: **Fri Aug 17, 2001 3:22 am**

Yeah with @home i have the same problem. After reformattting once it took about 1hr 30 min to get a hold of someone. Then my HD broke and when i fixed everything it took 2 hr 30 min to get somone. Its not reliable, but hey your only one customer....

Posted: **Fri Aug 17, 2001 9:28 am**

Princess, can you run a tracert to Yahoo and post the results for me to take a look at?

By high ping times, can you give me some numbers to see?

Don't mean to be a pain, but RR is like this sometimes and your absolutely right about level 1 tech support. You need to get ahold of the Cable Companies Lead RR Tech support supervisor! Yes, I know they won't do squat without a ticket and that stinks, but once they get you straightened around, I think you'll like it. It seems to be a problem for all new subscribers at first and I've never gotten a good explaination as to why it is like this.

Posted: **Fri Aug 17, 2001 9:29 am**

Originally posted by cornbread
welcome to cable tech service , from my experiance with cable techs, they suck! my advice is to learn as much as you can about your modem, your connection and so on. hopefully learning as much as you can will prevent you from having to call them in the future.

Are you talking about phone techs, or field techs? Normally, from the experience that I've had, that a lot of people have had problems with the phone support, but once they get one of us out at the house, we're able to get the problem fixed without any problems...

Posted: **Fri Aug 17, 2001 9:36 am**

Good morning IndyOST!

She is speaking of Phone Tech Support. Cornbread, I'm unsure of which he speaks. Everyone knows that they are the pits, In fact, my cable company has me skip calling RR Helpdesk if I can identify a line problem. If it's something else though, I have to go through the garbage and have a ticket issued or a ongoing open ticket.

Posted: **Fri Aug 17, 2001 9:56 am**

@home is getting better, but thats like farmer bob saying "hmmm that sh!t dont smell as bad now"

Posted: **Fri Aug 17, 2001 5:13 pm**

Actually whenever they give you a ticket it always works. They dont call me like they say they will but they fix it.

Posted: **Fri Aug 17, 2001 5:50 pm**

well after going through several people on the phone... now they had me check the ping to a server 50 times and do a tracert on it aswell. so i was supposed to email it to them. i did it and now i guess i just wait. i hate this. i hope they get it fixed. i cant wait to beat someones ass in quake...

Posted: **Fri Aug 17, 2001 5:52 pm**

Can you post a copy of what you had for ping and trace in this thread for us to see?

Posted: **Fri Aug 17, 2001 5:59 pm**

sure blebs99 here it is. sorry its so lengthy...

Reply from 216.39.136.201: bytes=32 time=52ms TTL=240
Reply from 216.39.136.201: bytes=32 time=55ms TTL=240
Reply from 216.39.136.201: bytes=32 time=52ms TTL=240
Reply from 216.39.136.201: bytes=32 time=48ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=56ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=61ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=58ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=55ms TTL=240
Reply from 216.39.136.201: bytes=32 time=56ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=52ms TTL=240
Reply from 216.39.136.201: bytes=32 time=48ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=52ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=55ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=47ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=68ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=57ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=53ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=57ms TTL=240
Reply from 216.39.136.201: bytes=32 time=50ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=52ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240
Reply from 216.39.136.201: bytes=32 time=51ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=54ms TTL=240
Reply from 216.39.136.201: bytes=32 time=49ms TTL=240

2 6 ms 7 ms 8 ms POS1-0-0.HNBHCA1-RTR1.socal.rr.com [24.30.161.69
]
3 8 ms 9 ms 9 ms POS1-1-0.WMNSCA1-RTR1.socal.rr.com [24.30.161.17
]
4 7 ms 7 ms 7 ms POS9-1-0.GDGVCA1-RTR3.socal.rr.com [24.30.161.13
]
5 10 ms 10 ms 10 ms sc-24-30-161-185.socal.rr.com [24.30.161.185]
6 10 ms 11 ms 12 ms sc-24-30-161-174.socal.rr.com [24.30.161.174]
7 11 ms 12 ms 11 ms 12.127.139.37
8 11 ms 17 ms 13 ms gbr5-p80.la2ca.ip.att.net [12.123.28.170]
9 11 ms 11 ms 11 ms gbr3-p100.la2ca.ip.att.net [12.122.5.90]
10 12 ms 14 ms 11 ms ggr1-p360.la2ca.ip.att.net [12.123.28.129]
11 11 ms 11 ms 12 ms pos6-2.core1.LosAngeles1.Level3.net [209.0.227.5
3]
12 12 ms 11 ms 12 ms gigabitethernet6-2.ipcolo2.LosAngeles1.Level3.ne
t [209.244.10.174]
13 12 ms 12 ms 12 ms 63.209.80.78
14 11 ms 14 ms 13 ms g6-0.cr1.lsanca.enron.net [155.251.13.45]
15 11 ms 12 ms 11 ms p4-0.cr1.lsajca.enron.net [155.251.13.33]
16 19 ms 21 ms 18 ms p3-0.cr1.lsvlnv.enron.net [155.251.13.38]
17 26 ms 25 ms 25 ms p8-0.cr1.slkdut.enron.net [155.251.13.62]
18 42 ms 41 ms 40 ms p4-0.cr1.ptldor.enron.net [155.251.13.74]
19 45 ms 43 ms 45 ms p7-0.cr1.sttlwa.enron.net [155.251.13.129]
20 47 ms 44 ms 44 ms v31.ag1.sttlwa.enron.net [155.251.13.102]
21 46 ms 47 ms 45 ms sense-sea-six.oz.net [198.32.180.26]
22 46 ms 53 ms 45 ms sense-sea-adsl-1.oz.net [216.39.128.15]
23 53 ms 52 ms 51 ms sense-sea-CovadSub-0-709.oz.net [216.39.136.201]

Trace complete.

i have no clue what all this means, but here ya go.

Posted: **Fri Aug 17, 2001 6:20 pm**

Your ping and trace times and hops, don't look all that bad. Actually, pretty good! I have done a few myself and at times that address is timing out. The one ping and trace I ran to it, shows a problem between hop #17 and #18 in tracert. Princess, edit out the 1st IP address in your Tracert. For your protection!

C:\WINDOWS>ping -n 10 216.39.136.201

Pinging 216.39.136.201 with 32 bytes of data:

Reply from 216.39.136.201: bytes=32 time=121ms TTL=244
Reply from 216.39.136.201: bytes=32 time=124ms TTL=244
Reply from 216.39.136.201: bytes=32 time=121ms TTL=244
Reply from 216.39.136.201: bytes=32 time=121ms TTL=244
Reply from 216.39.136.201: bytes=32 time=120ms TTL=244
Reply from 216.39.136.201: bytes=32 time=124ms TTL=244
Reply from 216.39.136.201: bytes=32 time=125ms TTL=244
Reply from 216.39.136.201: bytes=32 time=136ms TTL=244
Reply from 216.39.136.201: bytes=32 time=134ms TTL=244
Reply from 216.39.136.201: bytes=32 time=125ms TTL=244

Ping statistics for 216.39.136.201:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 136ms, Average = 125ms

Tracing route to sense-sea-CovadSub-0-709.oz.net [216.39.136.201]
over a maximum of 30 hops:

1 10 ms 8 ms 9 ms
2 8 ms 10 ms 10 ms pos6-3.ncntoh-rtr1.neo.rr.com [24.164.96.193]
3 10 ms 11 ms 11 ms srp1-0.polkoh-rtr1.neo.rr.com [24.164.96.101]
4 12 ms 13 ms 11 ms srp0-0.mnfdoh3-rtr1.neo.rr.com [24.164.96.70]
5 13 ms 13 ms 23 ms pos1-0.mtvnoh1-rtr1.columbus.rr.com [24.95.81.12
5]
6 14 ms 26 ms 14 ms srp6-0.clmboh1-rtr3.columbus.rr.com [24.95.81.21
9]
7 24 ms 27 ms 25 ms 12.125.142.29
8 25 ms 25 ms 27 ms gbr6-p80.cgcil.ip.att.net [12.123.5.222]
9 26 ms 26 ms 43 ms 12.122.11.45
10 53 ms 24 ms 25 ms 12.122.11.206
11 25 ms 26 ms 42 ms pos6-0.core1.Chicago1.Level3.net [209.0.225.9]
12 24 ms 24 ms 24 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161
]
13 49 ms 50 ms 50 ms so-2-0-0.mp1.NewYork1.level3.net [64.159.0.234]

14 50 ms 51 ms 50 ms pos8-0.core2.NewYork1.Level3.net [209.247.10.38]
15 51 ms 50 ms 51 ms gigabitethernet6-0.ipcolo2.NewYork1.Level3.net [
209.244.12.46]
16 50 ms 51 ms 77 ms 166.90.136.142
17 51 ms 50 ms 53 ms g9-0.cr1.nycmny.enron.net [155.251.12.89]
18 100 ms 104 ms 102 ms p9-0.cr1.chcgil2.enron.net [155.251.13.213]
19 105 ms 102 ms 101 ms p2-0.cr1.chcgil.enron.net [155.251.12.170]
20 101 ms 102 ms 102 ms p9-0.cr1.dnvtco.enron.net [155.251.12.69]
21 101 ms 102 ms 101 ms p10-0.cr1.slkdut.enron.net [155.251.12.74]
22 117 ms 116 ms 116 ms p4-0.cr1.ptldor.enron.net [155.251.13.74]
23 120 ms 123 ms 122 ms p7-0.cr1.sttlwa.enron.net [155.251.13.129]
24 120 ms 120 ms 121 ms v31.ag1.sttlwa.enron.net [155.251.13.102]
25 123 ms 124 ms 123 ms sense-sea-six.oz.net [198.32.180.26]
26 121 ms 132 ms 113 ms sense-sea-adsl-1.oz.net [216.39.128.15]
27 141 ms 122 ms 127 ms sense-sea-CovadSub-0-709.oz.net [216.39.136.201]

Trace complete.

Posted: **Fri Aug 17, 2001 6:33 pm**

why is my time so different then yours

Posted: **Fri Aug 17, 2001 7:43 pm**

Those traces and pings show no problems in RRs network, or anyones. Its perfect. What was wrong?

Here is my trace, which is dreadful.

Tracing route to sense-sea-CovadSub-0-709.oz.net [216.39.136.201]
over a maximum of 30 hops:

1 61 ms 10 ms 20 ms 10.154.32.1
2 10 ms 20 ms 10 ms mke-rtco-gsr-a-srp2-0.wi.rr.com [24.160.225.17]

3 10 ms 10 ms 10 ms 12.125.142.25
4 10 ms 20 ms 40 ms gbr5-p80.cgcil.ip.att.net [12.123.5.218]
5 40 ms 20 ms 70 ms 12.122.11.41
6 20 ms 60 ms 20 ms 12.122.11.206
7 20 ms 10 ms 20 ms pos6-0.core1.Chicago1.Level3.net [209.0.225.9]
8 20 ms 10 ms 60 ms so-4-0-0.mp1.Chicago1.Level3.net [209.247.10.161
]
9 40 ms 40 ms 41 ms so-2-0-0.mp1.NewYork1.level3.net [64.159.0.234]

10 80 ms 80 ms 41 ms pos8-0.core2.NewYork1.Level3.net [209.247.10.38]

11 70 ms 40 ms 50 ms gigabitethernet6-0.ipcolo2.NewYork1.Level3.net [
209.244.12.46]
12 80 ms 70 ms 40 ms 166.90.136.142
13 60 ms 81 ms 70 ms g9-0.cr1.nycmny.enron.net [155.251.12.89]
14 130 ms 131 ms 130 ms p9-0.cr1.chcgil2.enron.net [155.251.13.213]
15 150 ms 111 ms 90 ms p2-0.cr1.chcgil.enron.net [155.251.12.170]
16 90 ms 90 ms 131 ms p9-0.cr1.dnvtco.enron.net [155.251.12.69]
17 110 ms 90 ms 110 ms p10-0.cr1.slkdut.enron.net [155.251.12.74]
18 110 ms 120 ms 100 ms p4-0.cr1.ptldor.enron.net [155.251.13.74]
19 140 ms 130 ms 150 ms p7-0.cr1.sttlwa.enron.net [155.251.13.129]
20 240 ms 110 ms 181 ms v31.ag1.sttlwa.enron.net [155.251.13.102]
21 110 ms 130 ms 110 ms sense-sea-six.oz.net [198.32.180.26]
22 110 ms 100 ms 101 ms sense-sea-adsl-1.oz.net [216.39.128.15]
23 100 ms 211 ms 150 ms sense-sea-CovadSub-0-709.oz.net [216.39.136.201]

Trace complete.

and blebs..were you talking about that 10.xxx.xxx.xxx address? That does no harm because its a local address, not public so no one could get to it anyways.

Posted: **Fri Aug 17, 2001 8:41 pm**

Originally posted by P4 Lover
Those traces and pings show no problems in RRs network, or anyones. Its perfect. What was wrong?

and blebs..were you talking about that 10.xxx.xxx.xxx address? That does no harm because its a local address, not public so no one could get to it anyways.

I'm seeing crap on my own screen! Forget about the 10.xxx.xxx.xxx address Princess, my fault, P4Lover is correct.

As far as the times Princess, I don't know where the Covad address is that they had you trace to, but I'm on the opposite side of the U.S. from where you are and I also take a different route to get to that address. Your times look great, although I can't understand why RR has you doing a ping and trace to that address. Maybe something else new that I don't know about!

Posted: **Fri Aug 17, 2001 9:00 pm**

they said to do a trace to the server i always play on for quake. but how could my ping be good in there when its very high when i play. i dont know. i just hope they fix it!

Posted: **Fri Aug 17, 2001 10:13 pm**

I don't have the answer for ya on this one. I can tell you that out of 5 different times that I pinged and traced that IP, 3 times, it timed out all together. It may be that site server is having problems. I also wonder if the Code Red Worm traffic isn't causing some of what your experiencing. Some areas are seeing slow performance and speeds because of the traffic that infected servers are sending out. Are you having any other problems besides gaming?

Posted: **Sat Aug 18, 2001 12:38 am**

not really. every now and then my browser is slow. but it speeds right back up right away. i was playing a little bit ago and my ping was okay. so maybe they fixed it. who knows. but im just going to enjoy it while it lasts.

SG Broadband Community

road runner tech sucks...

road runner tech sucks...