Hi,

Thought I'd throw my thoughts in the pot...

I have experienced similar problem in the past with another ISP.
That problem turned out to be something wrong on isp's network - but only
got action on it by supplying evidence... If I ran continuous pings to
destination server it became apparent that (at different times of day) there
was about 10% packet loss over time. This was enough to stuff up ftp'ing
(although small files could get through occasionally, bigger files bombed
but also created zero sized files on server - could not copy over these
until they were first explicitly deleted).

And looking at traceroutes below, I wonder whose routers match the '*'
lines? they must have icmp replies turned off, maybe just for traceroutes
but maybe altogether.  Packet size discovery works with icmp to know when a
maximum sized packet has been rejected along the route and reduce the packet
size accordingly (from memory).

Regards,
  Bryce Stenberg.
     Harness Racing New Zealand computer department,
     emailto:[EMAIL PROTECTED]

> -----Original Message-----
> From: Rex Johnston [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 21 November 2002 11:29 a.m.
> To: [EMAIL PROTECTED]
> Subject: Re: Strangeness In Paradise
> 
> 
> Christopher Sawtell wrote:
> 
> >On Wed, 20 Nov 2002 18:51, you wrote:
> >Here is a failing ping and a traceroute from a Paradise 
> Cable connection:-
> >
> Here is one from a paradise ADSL connection.
> rex@gecko:~$ traceroute ftp.tait.co.nz
> traceroute to ftp.tait.co.nz (210.55.236.69), 30 hops max, 38 
> byte packets
>  1  router (192.168.0.100)  6.810 ms  2.129 ms  3.581 ms
>  2  203-79-124-ABC.adsl.paradise.net.nz (203.79.124.ABC)  45.331 ms  
> 44.876 ms  44.440 ms
>  3  192.168.253.225 (192.168.253.225)  47.236 ms  48.264 ms  46.196 ms
>  4  kelly.ipnet2.paradise.net.nz (203.96.155.158)  47.052 ms  
> 46.601 ms  
> 49.797 ms
>  5  fa7-0.bertha.paradise.net.nz (203.96.152.232)  47.576 ms  
> 53.983 ms  
> 46.695 ms
>  6  g1-0-1042.u21.tar.telstraclear.net (203.98.23.41)  59.918 
> ms  56.161 
> ms  51.825 ms
>  7  210-55-41-1.citylink.xtra.co.nz (210.55.41.1)  49.820 ms  
> 50.926 ms  
> 50.960 ms
>  8  a9-0-0-3.XTRAK2-B1.xtra.co.nz (202.27.176.141)  62.775 ms  74.357 
> ms  61.677 ms
>  9  v60.XTRAK1-B1.xtra.co.nz (203.96.111.148)  63.629 ms  63.830 ms  
> 62.539 ms
> 10  a0-1.IPNCH1-B3.xtra.co.nz (203.96.111.10)  76.548 ms  83.312 ms  
> 78.104 ms
> 11  e1.IPNCH1-B4.xtra.co.nz (202.27.176.102)  76.388 ms  82.730 ms  
> 80.958 ms
> 12  f1-0.IPNCH1-B6.xtra.co.nz (202.27.176.245)  80.589 ms  81.132 ms  
> 79.616 ms
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 
> but if we look at gatekeeper
> rex@gecko:~$ traceroute gatekeeper.tait.co.nz
> traceroute to gatekeeper.tait.co.nz (202.37.96.11), 30 hops 
> max, 38 byte 
> packets
>  1  router (192.168.0.100)  1.332 ms  1.639 ms  6.285 ms
>  2  203-79-124-ABC.adsl.paradise.net.nz (203.79.124.ABC)  43.917 ms  
> 49.089 ms  43.242 ms
>  3  192.168.253.225 (192.168.253.225)  46.178 ms  51.733 ms  45.814 ms
>  4  kelly.ipnet2.paradise.net.nz (203.96.155.158)  45.352 ms  
> 46.248 ms  
> 47.652 ms
>  5  fa7-0.bertha.paradise.net.nz (203.96.152.232)  47.989 ms  
> 49.298 ms  
> 49.804 ms
>  6  g1-0-1042.u21.tar.telstraclear.net (203.98.23.41)  53.463 ms  
> 117.466 ms  88.192 ms
>  7  210-55-41-1.citylink.xtra.co.nz (210.55.41.1)  51.846 ms  
> 50.932 ms  
> 48.201 ms
>  8  a9-0-0-3.XTRAK2-B1.xtra.co.nz (202.27.176.141)  58.215 ms  65.420 
> ms  63.655 ms
>  9  a4-0-0-1.IPNCH1-B6.xtra.co.nz (202.27.176.146)  79.743 ms  77.843 
> ms  78.786 ms
> 10  * * *
> 11  * * *
> 
> I think you'll find that telecom's responsibility ends at 
> XYZ.IPNCH1-B6.xtra.co.nz.
> 
> >>>Does anyone else have similar problems, suggestions, ideas?
> >>>
> rex@gecko:~$ traceroute -p 20 ftp.tait.co.nz
> traceroute to ftp.tait.co.nz (210.55.236.69), 30 hops max, 38 
> byte packets
>  1  router (192.168.0.100)  1.342 ms  0.969 ms  5.897 ms
>  2  203-79-124-ABC.adsl.paradise.net.nz (203.79.124.ABC)  44.141 ms  
> 43.501 ms  45.630 ms
>  3  192.168.253.225 (192.168.253.225)  50.971 ms  48.252 ms  49.527 ms
>  4  kelly.ipnet2.paradise.net.nz (203.96.155.158)  48.091 ms  
> 52.669 ms  
> 52.124 ms
>  5  fa7-0.bertha.paradise.net.nz (203.96.152.232)  47.737 ms  
> 47.986 ms  
> 49.398 ms
>  6  g1-0-1042.u21.tar.telstraclear.net (203.98.23.41)  52.928 
> ms  52.867 
> ms  49.946 ms
>  7  210-55-41-1.citylink.xtra.co.nz (210.55.41.1)  49.933 ms  
> 50.916 ms  
> 52.571 ms
>  8  a9-0-0-3.XTRAK2-B1.xtra.co.nz (202.27.176.141)  61.305 ms  65.349 
> ms  65.025 ms
>  9  v60.XTRAK1-B1.xtra.co.nz (203.96.111.148)  73.077 ms  63.824 ms  
> 65.238 ms
> 10  a0-1.IPNCH1-B3.xtra.co.nz (203.96.111.10)  79.890 ms  76.243 ms  
> 76.515 ms
> 11  e1.IPNCH1-B4.xtra.co.nz (202.27.176.102)  82.431 ms  79.196 ms  
> 89.426 ms
> 12  f1-1.IPNCH1-B6.xtra.co.nz (202.27.176.100)  79.426 ms 
> f1-0.IPNCH1-B6.xtra.co.nz (202.27.176.245)  75.351 ms  78.821 ms
> 13  * * *
> 
> 
> Hmm, that last line looks a bit strange.  Are they perchance 
> attempting 
> to multiplex some lines ?
> 
> Cheers, Rex
> 
> PS JohnC, you seem to have interited my old machine (or at least IP 
> address) @ TEL.  Still running debian ?
> 


CAUTION: This email message and accompanying data may contain information
that is confidential and subject to legal privilege. If you are not the
intended recipient you are notified that any use, dissemination,
distribution or copying of this message or data is prohibited. If you have
received this email message in error please notify us immediately and erase
all copies of the message and attachments.
 ALSO, unless expressly stated otherwise, the contents of this message
represent only the views of the sender as expressed only to the intended
recipient, do not commit Harness Racing New Zealand (HRNZ) to any course of
action and are not intended to impose any legal obligation upon HRNZ.


Reply via email to