Cable connection, what the shit.

E

E|C-ZemesiS

Veteran XV
Pinging www.adelphia.net [208.210.50.12] with 32 bytes of data:

Reply from 208.210.50.12: bytes=32 time=52ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=52ms TTL=246
Reply from 208.210.50.12: bytes=32 time=52ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=118ms TTL=246
Reply from 208.210.50.12: bytes=32 time=69ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=56ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=52ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=55ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=55ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=55ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=72ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Request timed out.
Request timed out.
Reply from 208.210.50.12: bytes=32 time=51ms TTL=246
Request timed out.
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=54ms TTL=246
Reply from 208.210.50.12: bytes=32 time=52ms TTL=246

Ping statistics for 208.210.50.12:
Packets: Sent = 30, Received = 22, Lost = 8 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 118ms, Average = 58ms

C:\Documents and Settings\*****>tracert www.adelphia.net

Tracing route to www.adelphia.net [208.210.50.12]
over a maximum of 30 hops:

1 * * * Request timed out.
2 10 ms 7 ms 8 ms 67.22.123.1
3 15 ms 16 ms 15 ms 67-22-121-33.atlaga.adelphia.net [67.22.121.33]

4 13 ms 15 ms 16 ms unk-426d0ed9.adelphiacom.net [66.109.14.217]
5 12 ms 16 ms 15 ms a1-00-00-00.c1.atl90.adelphiacom.net [66.109.1.2
05]
6 27 ms 27 ms 28 ms as-02-00-00.c0.dca91.adelphiacom.net [66.109.0.2
9]
7 * 34 ms 31 ms a3-00-00-00.c1.nyc90.adelphiacom.net [66.109.0.7
7]
8 * 52 ms 61 ms p0-01-00.c1.buf00.adelphiacom.net [66.109.0.206]

9 52 ms 55 ms 64 ms unk-426d012a.adelphiacom.net [66.109.1.42]
10 70 ms 92 ms * webportal-adelphia.synacor.com [208.210.50.12]
11 54 ms 51 ms * webportal-adelphia.synacor.com [208.210.50.12]
12 55 ms 108 ms 55 ms webportal-adelphia.synacor.com [208.210.50.12]

Trace complete.

C:\Documents and Settings\*****>tracert www.google.com

Tracing route to www.l.google.com [64.233.161.99]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 7 ms 8 ms 67.22.123.1
3 15 ms 14 ms * 67-22-121-33.atlaga.adelphia.net [67.22.121.33]

4 32 ms 36 ms 11 ms unk-426d0ed9.adelphiacom.net [66.109.14.217]
5 14 ms 28 ms 31 ms a1-00-00-00.c1.atl90.adelphiacom.net [66.109.1.2
05]
6 29 ms 28 ms 27 ms as-02-00-00.c0.dca91.adelphiacom.net [66.109.0.2
9]
7 27 ms 101 ms * 66.109.1.134
8 * 31 ms 43 ms eqixva-google-gige.google.com [206.223.115.21]
9 31 ms * 29 ms 216.239.47.120
10 30 ms 32 ms 111 ms 216.239.49.246
11 26 ms 27 ms 27 ms 64.233.161.99

Trace complete.

C:\Documents and Settings\*****>tracert www.yahoo.com

Tracing route to www.yahoo.akadns.net [216.109.118.66]
over a maximum of 30 hops:

1 * * * Request timed out.
2 8 ms 7 ms 7 ms 67.22.123.1
3 * 15 ms 16 ms 67-22-121-33.atlaga.adelphia.net [67.22.121.33]

4 12 ms 15 ms 16 ms unk-426d0ed9.adelphiacom.net [66.109.14.217]
5 13 ms 16 ms 16 ms a1-00-00-00.c1.atl90.adelphiacom.net [66.109.1.2
05]
6 27 ms 27 ms 27 ms as-02-00-00.c0.dca91.adelphiacom.net [66.109.0.2
9]
7 28 ms 29 ms 42 ms a1-00-00-00.p1.dca91.adelphiacom.net [66.109.1.1
86]
8 26 ms 27 ms 28 ms unk-426d0b4a.adelphiacom.net [66.109.11.74]
9 28 ms 26 ms 28 ms ae1.p401.msr1.dcn.yahoo.com [216.115.96.183]
10 28 ms 45 ms 27 ms ge2-2.bas1-m.dcn.yahoo.com [216.109.120.142]
11 * 50 ms 28 ms p3.www.dcn.yahoo.com [216.109.118.66]

Trace complete.

Out of the blue this shit starts, and any info would be great because Rick the tech 1 guy, and Stacy the tech 2 girl didn't tell me shit and offer a server tech to come out.
 
whatever the problem is, you're going to have to have it handled on your ISPs end. tell the tech you're getting horrible packet loss, and you've run lots of traceroutes and ping tests, and it appears it's at your first hop, your gateway. if they make you go through the motions of reboot your computer, cable modem, etc. etc. tell them this is the third (or however many times) you're calling and you already did all of that, and no offense, but they can skip it. ask them if they can check the signal/levels, maybe it's weak. suggest that they may need to send a tech out. assure them that the problem is most definitely not on your computer's end being that you have another computer that you tested with as well. try to do this without sounding too much like a know-it-all. :)
 
That's all futile if you have Roadrunner. : (

Edit: I had a problem with major packet loss once and, as it turns out, there was a flaw with the modem they provided. They knew this and they knew I had that particular modem but that doesn't stop them from trying their damnedest to convince me it's on my end.

That's all probably irrelivant to your problem, but likely they'll treat you like an idiot no matter what.
 
Last edited:
Sal M> Thank you for contacting Adelphia's High Speed Internet Support. Please describe how I may assist you while I look into your account information and contact history.
zemmizor> I'm having about 30 percent packet loss
zemmizor> timing out on my first hop
zemmizor> done 3 tracers
zemmizor> my first gateway is crap
Sal M> We block ICMP tracesroutes. If you do a trace it has to be done with UDP packets.
Sal M> I do see the packet loss, let me see if it's affecting anyone else.
zemmizor> and the packet loss
Sal M> I'm not getting packet loss to any other modem on your node and we are not recieving any other complaints.
Sal M> Everything looks good on the server.
zemmizor> Can someone be sent out to check my signal
Sal M> I can schedule for 09/29 8-12, 1-5 or all day.
Sal M> The 29th is Thursday.
zemmizor> 8-12 would be nice
zemmizor> also
Sal M> I have you scheduled for Thursday morning, 8-12. The tech will call ahead. Someone needs to be there to pick up. If no one answers the tech will cancel the service call and it will have to be rescheduled.
zemmizor> i have about 1kb up, 3kb down during 8 at night till this morning
zemmizor> yeah not even near dial up
Sal M> Your modem is showing a few billion errors on it.
zemmizor> er
zemmizor> ok thanks, bye
Sal M> Also, about 708 timeouts.
Sal M> Was there anything else I can assist you with?
 
Tech guy came out and said i had too much bandwidth coming from the main line, that information i was sending was coming back. Everything is fine now.
 
You must log in or register to reply here.
Back
Top