Author Topic: This cant be good...  (Read 741 times)

Offline Dadsguns

  • Silver Member
  • ****
  • Posts: 1979
This cant be good...
« on: January 17, 2011, 03:58:11 PM »
Looks to me ATT is messing this all up...... 
I am still getting packet loss and contacted Cox.net but there is nothing they can do.  What is there to do, just wait it out?



"Your intelligence is measured by those around you; if you spend your days with idiots you seal your own fate."

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Re: This cant be good...
« Reply #1 on: January 17, 2011, 04:01:56 PM »
It is actually at Cox's gateway.  I can run a reverse trace, but I doubt that it will show much.  By the way, all bets are off after the first hop where packet loss starts occuring.

I am getting a lot of complaints from Cox customers today.  I know part of it has to do with the cutover to Level3, so I can only surmise they are doing somthing along those lines.
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline Dadsguns

  • Silver Member
  • ****
  • Posts: 1979
Re: This cant be good...
« Reply #2 on: January 17, 2011, 04:11:00 PM »
The "technical support" lady told me that it wasnt cox BTW.  Give me something Skuzzy to blow their minds with make them go "how did he find that out"   :rofl

Let me know if there is anything you want me to do if you want to test it.


UPDATE:
Reset modem again this time it looks to be clear.

« Last Edit: January 17, 2011, 04:26:57 PM by Dadsguns »


"Your intelligence is measured by those around you; if you spend your days with idiots you seal your own fate."

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Re: This cant be good...
« Reply #3 on: January 17, 2011, 04:23:33 PM »
Ok Dadsguns, here you go.  I traced to your IP address (hop #2 in your trace).

 traceroute 68.10.14.85
traceroute to 68.10.14.85 (68.10.14.85), 30 hops max, 40 byte packets
 1  206.16.60.46 (206.16.60.46)  0.378 ms  0.297 ms  0.236 ms
 2  mdf001c7613r0002-gig-10-2.dal1.attens.net (63.241.193.17)  0.275 ms  0.277 ms  0.262 ms
 3  gar23.dlstx.ip.att.net (12.122.254.153)  2.107 ms gar23.dlstx.ip.att.net (12.122.254.189)  1.323 ms gar23.dlstx.ip.att.net (12.122.254.153)  1.037 ms
 4  cr2.dlstx.ip.att.net (12.122.138.162)  19.273 ms  18.823 ms  18.908 ms
 5  cr1.attga.ip.att.net (12.122.28.173)  18.314 ms  18.244 ms  18.655 ms
 6  attga04jt.ip.att.net (12.122.84.113)  17.886 ms  17.869 ms  17.878 ms
 7  192.205.35.218 (192.205.35.218)  18.151 ms  18.177 ms 192.205.35.214 (192.205.35.214)  18.151 ms
 8  ae-27-52.car1.Atlanta4.Level3.net (4.69.150.71)  18.305 ms  18.277 ms  18.273 ms
 9  COX-COMMUNI.car1.Atlanta4.Level3.net (4.53.233.130)  50.102 ms  18.234 ms  18.235 ms
10  nrfkdsrj01-ae0.0.rd.hr.cox.net (68.1.0.25)  60.701 ms  60.351 ms  60.325 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  *^C

Now, ask the nice Tech folks at Cox, why is it there is a router flap at hop #9, which happens to be their gateway between Level3 and themselves.  If they areno responsible for it, then ask them for a phone number to Lvel3's Tech Support so you can ask them about it.

Then ask, why is it Cox cannot route to the active IP address you have, once the trace gets into their network.

Feel free to point them at this thread.

EDIT:  By the way, if you are only talking to the first line of support, they are only responsible for your immedaite connection to their service.  You need to be talking to a Tier 2, or higher support technician/engineer.
« Last Edit: January 17, 2011, 04:26:54 PM by Skuzzy »
Roy "Skuzzy" Neese
support@hitechcreations.com