Velocity Reviews

Velocity Reviews (http://www.velocityreviews.com/forums/index.php)
-   NZ Computing (http://www.velocityreviews.com/forums/f47-nz-computing.html)
-   -   Dial up Connectivity Tonite (http://www.velocityreviews.com/forums/t571506-dial-up-connectivity-tonite.html)

Collector 07-27-2004 09:02 AM

Dial up Connectivity Tonite
 
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]

Sue Bilstein 07-27-2004 09:27 AM

Re: Dial up Connectivity Tonite
 
On Tue, 27 Jul 2004 21:02:30 +1200, Collector
<collectorNZ@2junkit.com> 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.


Warwick 07-27-2004 09:31 AM

Re: Dial up Connectivity Tonite
 
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.

Collector 07-27-2004 09:36 AM

Re: Dial up Connectivity Tonite
 
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.

Warwick 07-27-2004 09:54 AM

Re: Dial up Connectivity Tonite
 
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.

Collector 07-27-2004 10:01 AM

Re: Dial up Connectivity Tonite
 
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.

E. Scrooge 07-27-2004 10:39 AM

Re: Dial up Connectivity Tonite
 

"Sue Bilstein" <sue_bilstein@yahoop.com> wrote in message
news:bv7cg0h1cju476gaa5nk4cnioecf1l8k2o@4ax.com...
> On Tue, 27 Jul 2004 21:02:30 +1200, Collector
> <collectorNZ@2junkit.com> 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



Worm 07-27-2004 11:31 AM

Re: Dial up Connectivity Tonite
 
"Collector" <collectorNZ@2junkit.com> wrote in message
news:2mmk1cFnnhvmU1@uni-berlin.de...
> 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 **** connections for a while
now...might be time for a change...


Worm




All times are GMT. The time now is 09:52 AM.

Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.