Connection Help

[Toof]

<S> Guys,

I've been having a time here recently with warping. I've read the guide and run next to nothing in the background. I'm on a 10M Cable (land line) connection. Located in Spartanburg, SC. Provider is Charter. When running PingPlotter I see the most packet loss on  mdf1-bi8k-2-eth-2-3.dal1.attens.net (pinging 206.156.60.41, 16 hops) Pinging 206.16.60.39 (16 hops) I'm losing packets at mdf1-bi8k-2-eth-2-6.dal1.attens.net and also one or two servers farther up the line.

It doesn't occur -all- the time, but I'd say a good 75% of the time I have real issues with snapping all over the sky. It's annoying for the people trying to shoot me (They can't hit me) and annoying for me (I can't hit them when it goes screwy).

Is there anything I can do to remedy this? Besides move     If I need to post any additional information, tracert's or whatnot, just let me know.

A8Toof

[Skuzzy]

I need to see the traceroute information so I can run a trace back to you as well.

[Toof]

My Tracert to 206.16.60.39 is:

C:\Documents and Settings\HP_Administrator>tracert 206.16.60.39

Tracing route to 206.16.60.39 over a maximum of 30 hops

  1     5 ms     6 ms     5 ms  10.129.128.1
  2     7 ms     5 ms     5 ms  172.22.32.246
  3     6 ms     5 ms     5 ms  172.22.33.157
  4     6 ms     8 ms     7 ms  172.22.32.217
  5    10 ms     9 ms     9 ms  atl-edge-18.inet.qwest.net [216.206.221.149]
  6    15 ms    15 ms    15 ms  atl-core-01.inet.qwest.net [205.171.21.161]
  7    15 ms    15 ms    15 ms  atl-brdr-03.inet.qwest.net [205.171.21.98]
  8    16 ms    15 ms    15 ms  63.146.26.234
  9    39 ms    40 ms    38 ms  tbr2.attga.ip.att.net [12.122.81.154]
 10    38 ms    39 ms    39 ms  cr1.attga.ip.att.net [12.122.17.89]
 11    39 ms    39 ms    40 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 12    38 ms    39 ms    40 ms  tbr2.dlstx.ip.att.net [12.122.18.214]
 13    39 ms    38 ms    39 ms  br2.dlstx.ip.att.net [12.123.16.213]
 14    39 ms    39 ms    41 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 15    40 ms    39 ms    39 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.
46]
 16    39 ms    39 ms    39 ms  206.16.60.39

Trace complete.

My Tracert to 206.156.60.41 is:


C:\Documents and Settings\HP_Administrator>tracert 206.156.60.41

Tracing route to 206.156.60.41 over a maximum of 30 hops

  1     7 ms    26 ms     6 ms  10.129.128.1
  2     7 ms     6 ms     7 ms  172.22.32.242
  3     7 ms     8 ms     7 ms  172.22.33.153
  4     7 ms     7 ms     7 ms  172.22.32.217
  5    11 ms    12 ms    10 ms  atl-edge-18.inet.qwest.net [216.206.221.149]
  6    17 ms    19 ms    18 ms  atl-core-01.inet.qwest.net [205.171.21.161]
  7    30 ms    44 ms    31 ms  cer-core-01.inet.qwest.net [67.14.8.202]
  8    30 ms    29 ms    30 ms  chp-brdr-02.inet.qwest.net [205.171.139.114]
  9    33 ms    31 ms    32 ms  ber1-ge-7-4.chicagoequinix.savvis.net [208.173.1
80.25]
 10    33 ms    32 ms    32 ms  ber1-vlan-241.chicago.savvis.net [204.70.196.21]

 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     * and so on down to 30 hops.

I thought the Tracert to the 2nd server may have been a fluke, but it continually returned those numbers....hm, Titanic Tuesday? Didn't think about that

Appreciate your help Skuzzy

[Skuzzy]

I do not know what the IP address is you are using for that second trace.  It does not belong to us.

I tried to trace back to any of the 172.* addresses in your trace and AT&T does not appear to have any route information for those IP address as the gateway router we run through drops the trace like a rock.

I can trace to the QWest gateway, but nothing after it.  It appears a bad route propagation may be the culprit.  Contact QWest about that.

[Toof]

I apologize for the bum server, here is the tracert to the correct one :


C:\Documents and Settings\HP_Administrator>tracert 206.16.60.41

Tracing route to 206.16.60.41 over a maximum of 30 hops

  1     6 ms     6 ms     5 ms  10.129.128.1
  2     6 ms     6 ms     6 ms  172.22.32.242
  3     7 ms     5 ms     5 ms  172.22.33.153
  4    10 ms     6 ms     8 ms  172.22.32.217
  5    12 ms    12 ms    13 ms  atl-edge-18.inet.qwest.net [216.206.221.149]
  6    17 ms    17 ms    16 ms  atl-core-02.inet.qwest.net [205.171.21.165]
  7    16 ms    17 ms    15 ms  atl-brdr-03.inet.qwest.net [205.171.21.102]
  8    15 ms    15 ms    16 ms  192.205.33.89
  9    40 ms    40 ms    39 ms  tbr2.attga.ip.att.net [12.122.81.154]
 10    42 ms    42 ms    42 ms  cr1.attga.ip.att.net [12.122.17.105]
 11    40 ms    40 ms    45 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 12    43 ms    42 ms    40 ms  tbr2.dlstx.ip.att.net [12.122.18.206]
 13    37 ms    37 ms    39 ms  br2.dlstx.ip.att.net [12.123.16.213]
 14    39 ms    39 ms    39 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 15    39 ms    39 ms    40 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 16    41 ms    39 ms    41 ms  206.16.60.41

Trace complete.

[Skuzzy]

Inbound looks fine.  But the return is hosed.  AT&T has no idea where QWest IP addresses are and cannot find the route.

[Toof]

Is there anything to be done about it on my end save a hostile attack on the fronts of attnet and qwest?

Thanks again for you replies

[Skuzzy]

It is a two prong approach.  I have already filed a trouble ticket with AT&T to let them know they do not have a route to QWest users, but you need to do the same thing or it probably will take a lot longer to get fixed as QWest will not do anything until there is a complaint.

[Toof]

I attempted to put in a ticket with Qwest, but not being a customer, it's extremely hard to do, lol. I can't reach anyone on the phone who seems to have any idea what "connection issues between your servers and AT&T's" means. Their online help staff simply refers me to the customer repair link and the phone # where every is clueless. Maybe AT&T will talk some smack into em 

[Skuzzy]

I take it your ISP is using QWest as its transport then?  If so, then they should be able to facilitate a trouble ticket to QWest.

Tell your ISP you cannot contact IP address 206.16.60.38 and ask them, "why".  It is a working IP address and it is being connected to by many other people.