Getting constant connection problems after VDSL connection

Forums › Spark New Zealand › Getting constant connection problems after VDSL connection

HappilyInsane

50 posts

Geek

# 135162 16-Nov-2013 17:49

Our VDSL connection recently got all hooked a few days ago and ever since it was all done I've been constantly been getting steam error 101 every time I try to access any steam pages using steam. Or when I use the browser, it just doesn't connect to the page.

1 | 2 | 3 | 4

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 934973 16-Nov-2013 18:16

Were you a Telecom customer before the VDSL connection was installed?

Are you using a new modem/router?

Do you have a master filter installed?

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

RunningMan

5577 posts

Uber Geek

# 934980 16-Nov-2013 18:43

Are you using a custom DNS, or the Telecom assigned ones?

HappilyInsane

50 posts

Geek

# 935096 17-Nov-2013 08:19

The slip that chorus left mentioned no installation of a master filter. I was originally a slingshot customer before we switched over, and I am using the standard Technicolor VDSL router (TG589vn v2). Also I will change my DNS from google's and see if that helps.

freitasm

BDFL - Memuneh
64691 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 935100 17-Nov-2013 08:26

1. Usually VDSL connections require a master splitter installed, unless this is the only point in the house and there is no other device connected to it

2. In New Zealand do not use third party DNS. Always use your ISP's DNS settings or you risk content being downloaded from overseas when it could easily be reached from a CDN in New Zealand.

Post you model DSL stats now for people to comment on.

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

HappilyInsane

50 posts

Geek

# 935102 17-Nov-2013 08:29

This what you wanted?

Uptime:

0 days, 15:17:00

DSL Type:

ITU-T G.993.2

Bandwidth (Up/Down) [kbps/kbps]:

10,352 / 42,887

Data Transferred (Sent/Received) [B/B]:

0 / 0

Output Power (Up/Down) [dBm]:

429496720.1 / 13.5

Line Attenuation (Up/Down) [dB]:

17.3 / 8.5

SN Margin (Up/Down) [dB]:

20.4 / 12.3

System Vendor ID (Local/Remote):

TMMB / ----

Chipset Vendor ID (Local/Remote):

BDCM / IKNS

Loss of Framing (Local/Remote):

0 / 0

Loss of Signal (Local/Remote):

0 / 0

Loss of Power (Local/Remote):

0 / 0

Loss of Link (Remote):

Error Seconds (Local/Remote):

13 / 0

FEC Errors (Up/Down):

89 / 1,403

CRC Errors (Up/Down):

1 / 47

HEC Errors (Up/Down):

0 / 437

RunningMan

5577 posts

Uber Geek

# 935104 17-Nov-2013 08:38

There's a few errors showing up, but no doubt as DLM does it thing over the next couple of weeks, that will settle down.

Any difference using the correct DNS settings?

HappilyInsane

50 posts

Geek

# 935116 17-Nov-2013 09:50

Nope, using telecom's DNS with no differences whatsoever.

RunningMan

5577 posts

Uber Geek

# 935126 17-Nov-2013 10:15

Can you be more specific about what is happening?

Is it just Steam you have a problem with?

Is it all computers, or just one on your network?

Can you browse the internet OK?

HappilyInsane

50 posts

Geek

# 935131 17-Nov-2013 10:35

It appears to be all computers in the network cannot connect to steam. But I can connect to the internet just fine.

RunningMan

5577 posts

Uber Geek

# 935135 17-Nov-2013 10:42

Try traceroute to the Steam servers.

HappilyInsane

50 posts

Geek

# 935137 17-Nov-2013 10:52

Running a traceroute on the steam servers produces this:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

E:\Users\Darryl & Chelle>tracert steamcommunity.com

Tracing route to steamcommunity.com [63.228.223.103]
over a maximum of 30 hops:

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

2 38 ms 32 ms 34 ms 115-188-144-1.jetstream.xtra.co.nz [115.188.144.1]

3 51 ms 60 ms 51 ms mdr-ip20e-int.msc.global-gateway.net.nz [203.96.66.22]

4 51 ms 51 ms 51 ms ae0-10.akbr6.global-gateway.net.nz [203.96.66.21]

5 * * 50 ms ae5-2.akbr4.global-gateway.net.nz [210.55.202.213]

6 * * * Request timed out.

7 179 ms * 179 ms 202.50.232.18

8 214 ms 211 ms 180 ms ae3-10.lebr7.global-gateway.net.nz [122.56.127.26]

9 210 ms 210 ms 210 ms ae1-10.lebr6.global-gateway.net.nz [122.56.127.21]

10 211 ms 213 ms 245 ms ae51.edge2.LosAngeles9.Level3.net [4.53.230.13]

11 188 ms 187 ms * ae-4-90.edge1.LosAngeles9.Level3.net [4.69.144.202]

12 188 ms 187 ms 187 ms lap-brdr-03.inet.qwest.net [63.146.27.33]

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.

michaelmurfy

Mr Snotty
8881 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

# 935145 17-Nov-2013 11:14

Are you doing this over WiFi or Ethernet? Please try Ethernet, you might well have WiFi interference around your area.

HappilyInsane

50 posts

Geek

# 935149 17-Nov-2013 11:24

The traceroute showed was over ethernet. It produced the same result over WiFi

RunningMan

5577 posts

Uber Geek

# 935150 17-Nov-2013 11:30

I'm getting a similar result for a traceroute from a different ISP - could be a routing problem to Steam's servers, or may just not be responding to ICMP somewhere along the way.

Quick google of the 101 error seems to indicate it is a generic Steam communication error.

michaelmurfy

Mr Snotty
8881 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

# 935152 17-Nov-2013 11:32

HappilyInsane: The traceroute showed was over ethernet. It produced the same result over WiFi

Have you tried Steam over Ethernet as well? Your line stats seem fine but if you don't have a RJ45 socket for your VDSL and you're sure that Chorus have not stopped by to install a master filter phone up 0800225598 and get them to investigate. I'm personally on Telecom VDSL and have never had an issue with it (and my VDSL's uptime is up to 49 days now) and can connect to Steam fine.

1 | 2 | 3 | 4