dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
731
share rss forum feed


Soze

@sbcglobal.net

[Line Problem] Hop#4 error at 75.19.192.140

I've been having packet losses at the above address. I use Windows 7. Several others I know are having a problem as well. I've pinged it and it shows a 33% loss.

ISP is AT&T U-verse. I've reset the router twice. Yet tonight I lost connection again. That makes 43 times since September 1.

I notified AT&T but they really gave it little thought and just had me reset the router.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
Is that a destination, or a router en route to a destination? If it is an intermediary router, is their packet loss at the destination?

The reason I ask is that I am not seeing evidence of an actual host present, there. If it is an intermediary router, many such routers delay, or ignore diagnostic ping packets without affecting actual traffic to a host.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


Soze

@sbcglobal.net
It's enroute, it's actually 2 IP addresses, 75.19.192.140 and 75.19.192.106.

I've contacted AT&T 3 times now and they just don't get it.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
said by Soze :

It's enroute, it's actually 2 IP addresses, 75.19.192.140 and 75.19.192.106.

I've contacted AT&T 3 times now and they just don't get it.

If you are not seeing packet loss at the destination, then there is nothing "to get".
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum


jlibuszowski
Premium
join:2005-10-25
Hoffman Estates, IL
Try replying in the ATT direct form, you might have better luck there.


NormanS
I gave her time to steal my mind away
Premium,MVM
join:2001-02-14
San Jose, CA
kudos:12
Reviews:
·SONIC.NET
·Pacific Bell - SBC
Tell me about this trace route: Does it look like there is a problem?
Hop     Host                                   LOSS      Rcv     Sent    Best          Avg         Worst
0       ae-1.bb-d.slr.lxa.us.oneandone.net      0%       60       60       0.44         1.67       48.94
1       te-3-1.bb-d.ga.mkc.us.oneandone.net     0%       60       60       0.92         2.47       75.41
2       te-2-1.bb-d.ws.mkc.us.oneandone.net     0%       60       60       1.01         2.79       36.17
3       te-3-2.bb-d.cr.chi.us.oneandone.net     0%       60       60       11.53       12.18       35.49
4       p12-3.ir1.chicago2-il.us.xo.net         0%       60       60       11.50       13.06       42.17
5       207.88.14.193.ptr.us.xo.net             0%       60       60       13.10       16.48       34.40
6       te-4-1-0.rar3.denver-co.us.xo.net       0%       60       60       66.53       70.19       96.24
7       te-3-0-0.rar3.sanjose-ca.us.xo.net      0%       60       60       66.34       70.68       88.41
8       207.88.14.226.ptr.us.xo.net            24%       46       60       66.08       66.90       99.32
9       0.xe-4-1-0.gw3.equinix-sj.sonic.net     0%       60       60       68.69       69.39       81.62
10      0.xe-7-0-0.gw.pao1.sonic.net            0%       60       60       66.68       67.04       74.80
11      tengig4-3.cr1.lsatca11.sonic.net        0%       60       60       67.01       67.15       67.42
12      gig1-1-2.gw.snjsca12.sonic.net          0%       60       60       67.44       67.81       71.53
13      reki.aosake.net                         2%       59       60       78.01       78.61       81.31
 

And yet there is no failure reported:

»/pingtest/8695···/2841233

With packet loss, the only time a diagnostic showing loss counts is when the loss is at the destination. Intermediary routers don't count.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum