Dial up Connectivity Tonite

Discussion in 'NZ Computing' started by Collector, Jul 27, 2004.

  1. Collector

    Collector Guest

    Anyone experiencing dial up issues tonite


    Tracing route to ns1.orcon.net.nz [210.55.12.1]
    over a maximum of 30 hops:

    1 121 ms 100 ms 110 ms 192.168.251.42
    2 * * 1162 ms 192.168.31.131
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * 110 ms 120 ms 219.88.242.249
    7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]
     
    Collector, Jul 27, 2004
    #1
    1. Advertising

  2. Collector

    Sue Bilstein Guest

    On Tue, 27 Jul 2004 21:02:30 +1200, Collector
    <> wrote:

    >Anyone experiencing dial up issues tonite
    >
    >
    >Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >over a maximum of 30 hops:
    >
    > 1 121 ms 100 ms 110 ms 192.168.251.42
    > 2 * * 1162 ms 192.168.31.131
    > 3 * * * Request timed out.
    > 4 * * * Request timed out.
    > 5 * * * Request timed out.
    > 6 * 110 ms 120 ms 219.88.242.249
    > 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]


    Seems to be OK on Slingshot.
     
    Sue Bilstein, Jul 27, 2004
    #2
    1. Advertising

  3. Collector

    Warwick Guest

    On Tue, 27 Jul 2004 21:02:30 +1200, Collector wrote:

    > Anyone experiencing dial up issues tonite
    >
    >
    > Tracing route to ns1.orcon.net.nz [210.55.12.1]
    > over a maximum of 30 hops:
    >
    > 1 121 ms 100 ms 110 ms 192.168.251.42
    > 2 * * 1162 ms 192.168.31.131
    > 3 * * * Request timed out.
    > 4 * * * Request timed out.
    > 5 * * * Request timed out.
    > 6 * 110 ms 120 ms 219.88.242.249
    > 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]


    My trace appended for completeness sakes.
    The problem appears confined to those routers on the intermediate path
    between you and orcon.

    Tracing route to ns1.orcon.net.nz [210.55.12.1]

    over a maximum of 30 hops:



    1 131 ms 120 ms 120 ms ras5-a-wgtn-loop.paradise.net.nz
    [202.0.46.65]

    2 173 ms 119 ms 120 ms ge9-0-928.u22.tce.telstraclear.net
    [202.0.46.78]

    3 132 ms 120 ms 120 ms fa7-0.bertha.paradise.net.nz
    [203.96.152.232]

    4 140 ms 120 ms 120 ms g1-0-1042.u21.tar.telstraclear.net
    [203.98.23.41]

    5 132 ms 130 ms 130 ms g9-0.1041.u12.brh.telstraclear.net
    [203.98.21.37]

    6 132 ms 140 ms 130 ms orcon2.ape.net.nz [192.203.154.67]

    7 161 ms 130 ms 130 ms fe-b-distribution.nct.orcon.net.nz
    [219.88.242.209]

    8 132 ms 140 ms 140 ms fe-2621services-core.nct.orcon.net.nz
    [219.88.242.249]

    9 131 ms 140 ms 140 ms ns1.orcon.net.nz [210.55.12.1]



    Trace complete.
     
    Warwick, Jul 27, 2004
    #3
  4. Collector

    Collector Guest

    Warwick said the following on 27/07/2004 21:31:

    > On Tue, 27 Jul 2004 21:02:30 +1200, Collector wrote:
    >
    >
    >>Anyone experiencing dial up issues tonite
    >>
    >>
    >>Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >>over a maximum of 30 hops:
    >>
    >> 1 121 ms 100 ms 110 ms 192.168.251.42
    >> 2 * * 1162 ms 192.168.31.131
    >> 3 * * * Request timed out.
    >> 4 * * * Request timed out.
    >> 5 * * * Request timed out.
    >> 6 * 110 ms 120 ms 219.88.242.249
    >> 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]

    >
    >
    > My trace appended for completeness sakes.
    > The problem appears confined to those routers on the intermediate path
    > between you and orcon.
    >
    > Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >
    > over a maximum of 30 hops:
    >
    >
    >
    > 1 131 ms 120 ms 120 ms ras5-a-wgtn-loop.paradise.net.nz
    > [202.0.46.65]
    >
    > 2 173 ms 119 ms 120 ms ge9-0-928.u22.tce.telstraclear.net
    > [202.0.46.78]
    >
    > 3 132 ms 120 ms 120 ms fa7-0.bertha.paradise.net.nz
    > [203.96.152.232]
    >
    > 4 140 ms 120 ms 120 ms g1-0-1042.u21.tar.telstraclear.net
    > [203.98.23.41]
    >
    > 5 132 ms 130 ms 130 ms g9-0.1041.u12.brh.telstraclear.net
    > [203.98.21.37]
    >
    > 6 132 ms 140 ms 130 ms orcon2.ape.net.nz [192.203.154.67]
    >
    > 7 161 ms 130 ms 130 ms fe-b-distribution.nct.orcon.net.nz
    > [219.88.242.209]
    >
    > 8 132 ms 140 ms 140 ms fe-2621services-core.nct.orcon.net.nz
    > [219.88.242.249]
    >
    > 9 131 ms 140 ms 140 ms ns1.orcon.net.nz [210.55.12.1]
    >
    >
    >
    > Trace complete.

    Hop 3 is Telecom 0867 and has ICMP disabled, the next Telecom to orcon
    and so on.

    Trouble is the tracert is hardly typical the delays (and packet loss)
    are all over the place being almost random as to which hops they occur on.
     
    Collector, Jul 27, 2004
    #4
  5. Collector

    Warwick Guest

    On Tue, 27 Jul 2004 21:36:55 +1200, Collector wrote:

    > Warwick said the following on 27/07/2004 21:31:
    >
    >> On Tue, 27 Jul 2004 21:02:30 +1200, Collector wrote:
    >>
    >>
    >>>Anyone experiencing dial up issues tonite
    >>>
    >>>
    >>>Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >>>over a maximum of 30 hops:
    >>>
    >>> 1 121 ms 100 ms 110 ms 192.168.251.42
    >>> 2 * * 1162 ms 192.168.31.131
    >>> 3 * * * Request timed out.
    >>> 4 * * * Request timed out.
    >>> 5 * * * Request timed out.
    >>> 6 * 110 ms 120 ms 219.88.242.249
    >>> 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]

    >>
    >>
    >> My trace appended for completeness sakes.
    >> The problem appears confined to those routers on the intermediate path
    >> between you and orcon.
    >>
    >> Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >>
    >> over a maximum of 30 hops:
    >>
    >>
    >>
    >> 1 131 ms 120 ms 120 ms ras5-a-wgtn-loop.paradise.net.nz
    >> [202.0.46.65]
    >>
    >> 2 173 ms 119 ms 120 ms ge9-0-928.u22.tce.telstraclear.net
    >> [202.0.46.78]
    >>
    >> 3 132 ms 120 ms 120 ms fa7-0.bertha.paradise.net.nz
    >> [203.96.152.232]
    >>
    >> 4 140 ms 120 ms 120 ms g1-0-1042.u21.tar.telstraclear.net
    >> [203.98.23.41]
    >>
    >> 5 132 ms 130 ms 130 ms g9-0.1041.u12.brh.telstraclear.net
    >> [203.98.21.37]
    >>
    >> 6 132 ms 140 ms 130 ms orcon2.ape.net.nz [192.203.154.67]
    >>
    >> 7 161 ms 130 ms 130 ms fe-b-distribution.nct.orcon.net.nz
    >> [219.88.242.209]
    >>
    >> 8 132 ms 140 ms 140 ms fe-2621services-core.nct.orcon.net.nz
    >> [219.88.242.249]
    >>
    >> 9 131 ms 140 ms 140 ms ns1.orcon.net.nz [210.55.12.1]
    >>
    >>
    >>
    >> Trace complete.

    > Hop 3 is Telecom 0867 and has ICMP disabled, the next Telecom to orcon
    > and so on.
    >
    > Trouble is the tracert is hardly typical the delays (and packet loss)
    > are all over the place being almost random as to which hops they occur on.


    My old boss called that slow response to ping. It is obvious when the hop
    after the suspect one comes in at less lag.

    There are two types of trace, windows (uses ICMP) and Unix (sends raw udp
    packets). From memory visroute will revert to udp ping when the ICMP one
    times out. This can give a more accurate picture of what is going on.
     
    Warwick, Jul 27, 2004
    #5
  6. Collector

    Collector Guest

    Warwick said the following on 27/07/2004 21:54:

    > On Tue, 27 Jul 2004 21:36:55 +1200, Collector wrote:
    >
    >
    >>Warwick said the following on 27/07/2004 21:31:
    >>
    >>
    >>>On Tue, 27 Jul 2004 21:02:30 +1200, Collector wrote:
    >>>
    >>>
    >>>
    >>>>Anyone experiencing dial up issues tonite
    >>>>
    >>>>
    >>>>Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >>>>over a maximum of 30 hops:
    >>>>
    >>>> 1 121 ms 100 ms 110 ms 192.168.251.42
    >>>> 2 * * 1162 ms 192.168.31.131
    >>>> 3 * * * Request timed out.
    >>>> 4 * * * Request timed out.
    >>>> 5 * * * Request timed out.
    >>>> 6 * 110 ms 120 ms 219.88.242.249
    >>>> 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]
    >>>
    >>>
    >>>My trace appended for completeness sakes.
    >>>The problem appears confined to those routers on the intermediate path
    >>>between you and orcon.
    >>>
    >>>Tracing route to ns1.orcon.net.nz [210.55.12.1]
    >>>
    >>>over a maximum of 30 hops:
    >>>
    >>>
    >>>
    >>> 1 131 ms 120 ms 120 ms ras5-a-wgtn-loop.paradise.net.nz
    >>>[202.0.46.65]
    >>>
    >>> 2 173 ms 119 ms 120 ms ge9-0-928.u22.tce.telstraclear.net
    >>>[202.0.46.78]
    >>>
    >>> 3 132 ms 120 ms 120 ms fa7-0.bertha.paradise.net.nz
    >>>[203.96.152.232]
    >>>
    >>> 4 140 ms 120 ms 120 ms g1-0-1042.u21.tar.telstraclear.net
    >>>[203.98.23.41]
    >>>
    >>> 5 132 ms 130 ms 130 ms g9-0.1041.u12.brh.telstraclear.net
    >>>[203.98.21.37]
    >>>
    >>> 6 132 ms 140 ms 130 ms orcon2.ape.net.nz [192.203.154.67]
    >>>
    >>> 7 161 ms 130 ms 130 ms fe-b-distribution.nct.orcon.net.nz
    >>>[219.88.242.209]
    >>>
    >>> 8 132 ms 140 ms 140 ms fe-2621services-core.nct.orcon.net.nz
    >>>[219.88.242.249]
    >>>
    >>> 9 131 ms 140 ms 140 ms ns1.orcon.net.nz [210.55.12.1]
    >>>
    >>>
    >>>
    >>>Trace complete.

    >>
    >>Hop 3 is Telecom 0867 and has ICMP disabled, the next Telecom to orcon
    >>and so on.
    >>
    >>Trouble is the tracert is hardly typical the delays (and packet loss)
    >>are all over the place being almost random as to which hops they occur on.

    >
    >
    > My old boss called that slow response to ping. It is obvious when the hop
    > after the suspect one comes in at less lag.
    >
    > There are two types of trace, windows (uses ICMP) and Unix (sends raw udp
    > packets). From memory visroute will revert to udp ping when the ICMP one
    > times out. This can give a more accurate picture of what is going on.


    I will recheck my connections tomorrow (My Telecom line) and then chase
    it up with the provider.
    I have already been working with them (along with others) testing due to
    recurring difficulties on dial up.
     
    Collector, Jul 27, 2004
    #6
  7. Collector

    E. Scrooge Guest

    "Sue Bilstein" <> wrote in message
    news:...
    > On Tue, 27 Jul 2004 21:02:30 +1200, Collector
    > <> wrote:
    >
    > >Anyone experiencing dial up issues tonite
    > >
    > >
    > >Tracing route to ns1.orcon.net.nz [210.55.12.1]
    > >over a maximum of 30 hops:
    > >
    > > 1 121 ms 100 ms 110 ms 192.168.251.42
    > > 2 * * 1162 ms 192.168.31.131
    > > 3 * * * Request timed out.
    > > 4 * * * Request timed out.
    > > 5 * * * Request timed out.
    > > 6 * 110 ms 120 ms 219.88.242.249
    > > 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]

    >
    > Seems to be OK on Slingshot.


    Told you Slingshot is good value.

    E. Scrooge
     
    E. Scrooge, Jul 27, 2004
    #7
  8. Collector

    Worm Guest

    "Collector" <> wrote in message
    news:...
    > Anyone experiencing dial up issues tonite
    >
    >
    > Tracing route to ns1.orcon.net.nz [210.55.12.1]
    > over a maximum of 30 hops:
    >
    > 1 121 ms 100 ms 110 ms 192.168.251.42
    > 2 * * 1162 ms 192.168.31.131
    > 3 * * * Request timed out.
    > 4 * * * Request timed out.
    > 5 * * * Request timed out.
    > 6 * 110 ms 120 ms 219.88.242.249
    > 7 110 ms 110 ms 111 ms ns1.orcon.net.nz [210.55.12.1]


    I don't understand any of that output...but I do know that Orcon are having
    troubles with Telecom systems or something. Hope they get it sorted soon,
    I've been beating my head against a wall over shit connections for a while
    now...might be time for a change...


    Worm
     
    Worm, Jul 27, 2004
    #8
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. paulsy

    Target Tonite - Comp Techs

    paulsy, Sep 21, 2003, in forum: NZ Computing
    Replies:
    67
    Views:
    1,058
  2. Waylon Smithers

    Swain on Holmes tonite at 7pm

    Waylon Smithers, May 19, 2004, in forum: NZ Computing
    Replies:
    89
    Views:
    1,444
    brundlefly
    May 24, 2004
  3. Collector»NZ

    News Group Trouble tonite

    Collector»NZ, Feb 3, 2005, in forum: NZ Computing
    Replies:
    5
    Views:
    298
    Collector»NZ
    Feb 3, 2005
  4. canon paora

    Tonite on Xtra Go Large

    canon paora, Dec 3, 2006, in forum: NZ Computing
    Replies:
    54
    Views:
    1,151
    Lawrence D'Oliveiro
    Dec 9, 2006
  5. canon paora

    Tonite on Xtra Go Large

    canon paora, Dec 3, 2006, in forum: NZ Computing
    Replies:
    29
    Views:
    739
    ~misfit~
    Dec 10, 2006
Loading...

Share This Page