Telecom VDSL - Intermittent connection very frustrating

Forums › Spark New Zealand (including Skinny and BigPipe) › Telecom VDSL - Intermittent connection very frustrating

1 | 2 | 3 | 4 | 5

8955 posts

Uber Geek

#915739 15-Oct-2013 21:36

An afterthought - does this problem start / stop abruptly at about the same time, or does it slowly deteriorate, and then slowly recover?

kmx

35 posts

Geek

#915746 15-Oct-2013 21:40

RunningMan: An afterthought - does this problem start / stop abruptly at about the same time, or does it slowly deteriorate, and then slowly recover?

Umm i think it slowly starts to play up. I notice it getting worse in the weekends when im home. It probably starts playing up around midday then just gets worse and worse over the day.

When i get home from work around 630 its usually pretty bad by the time i log on

Earlier in the thread i mentioned a guy from chorus doing something outside my house (sorry i dont know what) and my connection was good for a few days but then slowly deteriorated back to what it is today.

I dont understand why it gets progressively worse, i was wondering if the line management is actually killing my connection in some way

kmx

35 posts

Geek

#915747 15-Oct-2013 21:43

Do you think it means anything that my modem doesnt register any data being sent or received??

I also checked my telecom online usage and the same thing, it doesnt reflect any upload or download since i changed to VDSL?

Config on the telecom side not being switched on, its a desperate long shot....

RunningMan

8955 posts

Uber Geek

#915757 15-Oct-2013 21:50

Cyclic problems are usually caused by some predictable behaviour or happening.

Some possibilities are:

1) Congestion - given you are with the same ISP, I wouldn't have thought a switch from ADSL to VDSL would have this sort of impact though.

2) Temperature - a joint on the line somewhere that is failing as the ambient temp goes up - rare, but possible

3) Moisture - as for temperature, but when it rains

4) Some other nearby higher frequency electrical interference that the lower frequencies of ADSL weren't so affected by. A factory, or appliance that is active at that time of day.

Earlier (I think) you posted some bit loading graphs - does this change significantly through the day?

kmx

35 posts

Geek

#915759 15-Oct-2013 21:56

Is it worth me crawling under my house to see if any other cables like power leads are close to my network cables?

I do have some phone jacks in my house that don't work that I pointed out to chorus. He was sure they would have no impact after he inspected both.

kmx

35 posts

Geek

#919397 21-Oct-2013 20:53

Can you guys see an issue here

Im not sure if this is going to show my issue. It keeps running errors then finally runs. Are these timings normal?

Traceroute has started…

traceroute to redmondpie.com (192.96.201.17), 64 hops max, 72 byte packets

1 * * *

2 122-61-216-1.jetstream.xtra.co.nz (122.61.216.1) 22.966 ms 24.572 ms 22.372 ms

3 * mdr-ip20e-int.msc.global-gateway.net.nz (203.96.66.22) 208.528 ms 22.441 ms

4 ae0-10.akbr6.global-gateway.net.nz (203.96.66.21) 21.807 ms 21.896 ms 21.545 ms

5 ae5-2.akbr4.global-gateway.net.nz (210.55.202.213) 21.584 ms 21.588 ms 21.673 ms

6 ae1-10.tkbr12.global-gateway.net.nz (202.50.232.37) 38.523 ms 35.480 ms 33.866 ms

7 * xe2-0-1.lebr7.global-gateway.net.nz (203.96.120.142) 431.915 ms *

8 122.56.127.25 (122.56.127.25) 431.490 ms 441.929 ms 162.300 ms

9 pax-ms1.us.leaseweb.net (198.32.176.205) 159.739 ms

10 te2-3.msc1.wdc.leaseweb.net (217.20.125.20) 533.764 ms 308.281 ms 305.869 ms

11 te2-3.msc1.wdc.leaseweb.net (217.20.125.20) 306.882 ms 306.987 ms

te9-2.core1.wdc.leaseweb.net (217.20.125.9) 307.155 ms

12 po5.cs2.wdc1.leaseweb.net (108.59.15.117) 306.502 ms

te9-2.core1.wdc.leaseweb.net (217.20.125.9) 306.702 ms 306.383 ms

13 192.96.201.17 (192.96.201.17) 307.426 ms

michaelmurfy

meow
13243 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#919400 21-Oct-2013 20:59

Are you running Windows 8.1?

Also, do these tests via Ethernet and NOT WiFi - seems you're doing it over WiFi which is why you're seeing these issues.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

Sharesies kids

Free kids accounts - trade shares and funds (NZ, US) with Sharesies (affiliate link).

kmx

35 posts

Geek

#919401 21-Oct-2013 21:00

michaelmurfy: Are you running Windows 8.1?

i ran this from my macbook air

I can run it from my windows 8 pc if that makes a difference

kmx

35 posts

Geek

#919406 21-Oct-2013 21:07

Ping to the same website

Ping has started… PING redmondpie.com (192.96.201.17): 56 data bytes 64 bytes from 192.96.201.17: icmp_seq=0 ttl=52 time=496.365 ms 64 bytes from 192.96.201.17: icmp_seq=1 ttl=52 time=239.631 ms Request timeout for icmp_seq 2 64 bytes from 192.96.201.17: icmp_seq=3 ttl=52 time=258.319 ms 64 bytes from 192.96.201.17: icmp_seq=4 ttl=52 time=244.710 ms 64 bytes from 192.96.201.17: icmp_seq=5 ttl=52 time=243.999 ms 64 bytes from 192.96.201.17: icmp_seq=6 ttl=52 time=238.759 ms 64 bytes from 192.96.201.17: icmp_seq=7 ttl=52 time=240.734 ms Request timeout for icmp_seq 8 64 bytes from 192.96.201.17: icmp_seq=9 ttl=52 time=241.968 ms --- redmondpie.com ping statistics --- 10 packets transmitted, 8 packets received, 20.0% packet loss round-trip min/avg/max/stddev = 238.759/275.561/496.365/83.656 ms

RUN2

Ping has started…

PING redmondpie.com (192.96.201.17): 56 data bytes

64 bytes from 192.96.201.17: icmp_seq=0 ttl=52 time=464.910 ms

64 bytes from 192.96.201.17: icmp_seq=1 ttl=52 time=385.927 ms

64 bytes from 192.96.201.17: icmp_seq=2 ttl=52 time=613.979 ms

64 bytes from 192.96.201.17: icmp_seq=3 ttl=52 time=247.167 ms

64 bytes from 192.96.201.17: icmp_seq=4 ttl=52 time=238.996 ms

64 bytes from 192.96.201.17: icmp_seq=5 ttl=52 time=374.729 ms

64 bytes from 192.96.201.17: icmp_seq=6 ttl=52 time=602.259 ms

64 bytes from 192.96.201.17: icmp_seq=7 ttl=52 time=518.413 ms

64 bytes from 192.96.201.17: icmp_seq=8 ttl=52 time=442.994 ms

64 bytes from 192.96.201.17: icmp_seq=9 ttl=52 time=363.726 ms

--- redmondpie.com ping statistics ---

10 packets transmitted, 10 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 238.996/425.310/613.979/123.210 ms

l43a2

1779 posts

Uber Geek

ID Verified

Trusted

#919470 21-Oct-2013 23:26

are you using wireless ? try with wired

kmx

35 posts

Geek

#919731 22-Oct-2013 15:00

Ok. When I get home I will kill the wireless and run test from my PC which is hard wired straight to the modem. Cheera

kmx

35 posts

Geek

#919921 22-Oct-2013 19:52

Internet starting to play up again so here are some trace run from my pc.

This computer is hardwired directly to the modem.

C:\Windows\system32>tracert telecom.co.nz

Tracing route to telecom.co.nz [210.55.11.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]

2 22 ms 23 ms 24 ms 122-61-216-1.jetstream.xtra.co.nz [122.61.216.1]

3 22 ms 23 ms 21 ms mdr-ip20e-dom.msc.global-gateway.net.nz [203.96.
66.122]

4 20 ms 20 ms 21 ms ae0-20.akcr11.global-gateway.net.nz [203.96.66.1
21]

5 21 ms 21 ms 21 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202
.49]

6 20 ms 21 ms 21 ms telecom-sdn-ak1-dom.akcr8.global-gateway.net.nz
[203.96.65.198]

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * * Request timed out.

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 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

kmx

35 posts

Geek

#919936 22-Oct-2013 20:01

Here are a couple more.

The internet is playing up right now and i can see these request time outs.

22/10/2013 19:54 C:\Windows\system32>tracert nzherald.co.nz Tracing route to nzherald.co.nz [202.175.135.91] over a maximum of 30 hops: 1     *        *        *     Request timed out.
2    21 ms    21 ms    23 ms 122-61-216-1.jetstream.xtra.co.nz [122.61.216.1] 3    21 ms    21 ms    20 ms mdr-ip20e-dom.msc.global-gateway.net.nz [203.96.
  4    21 ms    20 ms    20 ms ae0-20.akcr11.global-gateway.net.nz [203.96.66.1 21]
5    22 ms    22 ms    22 ms g7-3-3-0.tkcr5.global-gateway.net.nz [210.55.202 .50]
6    22 ms    21 ms    21 ms orcon-dom.tkcr4.global-gateway.net.nz [203.96.66 .102]
7    21 ms    21 ms    21 ms xe-0-0-1-0.mer2.nct.orcon.net.nz [121.98.9.38]
8    22 ms    21 ms    22 ms 60.234.177.2
9     *        *        *     Request timed out.
10    22 ms    40 ms    39 ms 202.175.135.91 Trace complete.

22/10/2013 19:56 C:\Windows\system32>tracert youtube.com Tracing route to youtube.com [122.56.115.18] over a maximum of 30 hops: 1     *        *        *     Request timed out.
2    22 ms    25 ms    29 ms 122-61-216-1.jetstream.xtra.co.nz [122.61.216.1] 3    21 ms    21 ms    21 ms mdr-ip20e-int.msc.global-gateway.net.nz [203.96.
4    20 ms    20 ms    27 ms ae0-10.akbr6.global-gateway.net.nz [203.96.66.21 ]
5    21 ms    21 ms    21 ms ae5-2.akbr4.global-gateway.net.nz [210.55.202.21 3]
6     *        *        *     Request timed out.
7    36 ms    35 ms    33 ms ae6-10.tkbr11.global-gateway.net.nz [203.96.120. 106]
8    37 ms    36 ms    37 ms cache.googlevideo.com [122.56.115.18]
Trace complete.

kmx

35 posts

Geek

#919939 22-Oct-2013 20:07

Ping test

C:\Windows\system32>ping telecom.co.nz

Pinging telecom.co.nz [210.55.11.13] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 210.55.11.13:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

michaelmurfy

meow
13243 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#919940 22-Oct-2013 20:08

1) Try from a computer that's connected straight to Ethernet not running Windows 8
2) Post a ping, and a speedtest along with your router stats please. We're not interested with testing over WiFi. Do a ping to Trademe.

mmurphy@charmander:~$ ping trademe.co.nz
PING trademe.co.nz (202.162.72.2) 56(84) bytes of data.
64 bytes from www.trademe.co.nz (202.162.72.2): icmp_req=1 ttl=248 time=29.5 ms
64 bytes from www.trademe.co.nz (202.162.72.2): icmp_req=2 ttl=248 time=29.7 ms
64 bytes from www.trademe.co.nz (202.162.72.2): icmp_req=3 ttl=248 time=29.9 ms
64 bytes from www.trademe.co.nz (202.162.72.2): icmp_req=4 ttl=248 time=31.6 ms
^C
--- trademe.co.nz ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 29.506/30.226/31.632/0.856 ms

Edit: Please note, the Telecom site blocks ping.

1 | 2 | 3 | 4 | 5