Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




5 posts

Wannabe Geek


# 173804 7-Jun-2015 08:58
Send private message

 

 

My Slingshot VDSL has constantly been disconnecting and reconnecting every few minutes. It may be a few hours in between but recently it became more frequent.

I have had this going on for more than a week now and restarted the modem/router countless times. I call Slingshot and they tell me to get another VDSL modem to test or test my VDSL modem at a friend's house who has VDSL. I cannot do any of these.... and if a tech comes out they may charge me if it is my equipment. So basically Slingshot says they can't help anymore.

Yesterday I went out and got a separate router Netgear R7000 (was going to get one anyway), I put the slingshot modem/router on full bridge and connected the Netgear. Was smooth sailing for half a day, then it started disconnecting again. Now its even more frequent...

This is really getting frustrating... any help will be appreciated. Thanks

 

 


View this topic in a long page with up to 500 replies per page Create new topic
 1 | 2
BDFL - Memuneh
63630 posts

Uber Geek
+1 received by user: 14092

Administrator
Trusted
Geekzone
Lifetime subscriber

  # 1318561 7-Jun-2015 09:18
Send private message

You should have someone looking at your wiring.

Have your property been affected by recent floods? Do you have a master filter installed? Monitored alarms? Is this disconnection detected at the modem or devices only?

Please post modem stats so people can help.




27896 posts

Uber Geek
+1 received by user: 7383

Moderator
Trusted
Biddle Corp
Lifetime subscriber

  # 1318562 7-Jun-2015 09:21
Send private message

Did Slingshot get Chorus to install a master filter at your place? If not you'll need to address your internal wiring as this is likely at fault.



 
 
 
 




5 posts

Wannabe Geek


  # 1318563 7-Jun-2015 09:30
Send private message

Yes, when I first go VDSL Chorus came to install the master filter in my house. The connection has been fine albeit a few drop out issues, but this last week or so has been constant disconnects!!! It's really crazy...

Modem VB104W

This is the log from my R7000 @ the bottom is the most recent disconnects

[LAN access from remote] from 108.202.32.145:37983 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:47
[LAN access from remote] from 177.192.241.151:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:43
[LAN access from remote] from 95.240.28.19:13067 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:43
[LAN access from remote] from 89.65.89.140:43611 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:42
[LAN access from remote] from 74.56.143.128:29678 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:42
[LAN access from remote] from 195.211.188.16:36286 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:41
[LAN access from remote] from 70.173.3.81:1024 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:29
[LAN access from remote] from 67.237.225.148:43165 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:25
[LAN access from remote] from 5.18.223.83:36263 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:21
[LAN access from remote] from 190.108.88.38:3292 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:15
[LAN access from remote] from 178.19.251.6:48504 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:14
[LAN access from remote] from 183.186.52.253:26523 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:11
[LAN access from remote] from 92.138.202.208:64327 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:10
[LAN access from remote] from 122.189.105.132:1151 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:07
[LAN access from remote] from 94.181.4.156:26707 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:03
[LAN access from remote] from 50.32.160.121:65502 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:01
[LAN access from remote] from 222.121.244.240:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:28:01
[Admin login] from source 10.0.0.3, Saturday, Jun 06,2015 21:27:58
[LAN access from remote] from 188.191.82.249:48679 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:56
[LAN access from remote] from 92.242.112.130:59449 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:54
[LAN access from remote] from 93.43.252.35:60156 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:54
[LAN access from remote] from 71.197.184.180:7760 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:48
[LAN access from remote] from 77.168.216.135:59916 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:48
[LAN access from remote] from 74.56.149.63:47677 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:38
[LAN access from remote] from 46.166.191.23:40783 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:34
[LAN access from remote] from 178.64.23.81:17487 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:32
[LAN access from remote] from 104.137.21.44:46508 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:23
[LAN access from remote] from 93.32.198.186:63528 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:20
[LAN access from remote] from 39.181.133.206:18085 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:20
[LAN access from remote] from 83.81.6.63:9089 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:20
[LAN access from remote] from 88.227.205.34:16018 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:17
[LAN access from remote] from 89.241.234.184:17980 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:17
[LAN access from remote] from 101.18.114.94:26435 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:17
[LAN access from remote] from 210.84.13.108:39913 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:17
[LAN access from remote] from 80.78.77.42:1030 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:15
[LAN access from remote] from 123.138.213.181:61726 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:12
[LAN access from remote] from 120.145.9.83:31069 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:12
[LAN access from remote] from 118.93.149.126:55820 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:12
[LAN access from remote] from 82.112.49.209:50203 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:08
[LAN access from remote] from 37.0.34.96:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:27:00
[LAN access from remote] from 106.158.71.44:54578 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:56
[LAN access from remote] from 123.134.15.237:39143 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:52
[LAN access from remote] from 71.53.187.85:54107 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:50
[LAN access from remote] from 78.73.168.3:25167 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:45
[LAN access from remote] from 203.59.97.157:20177 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:45
[LAN access from remote] from 195.50.31.211:26616 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:44
[LAN access from remote] from 41.252.224.15:48006 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:44
[LAN access from remote] from 109.127.169.192:16750 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:38
[LAN access from remote] from 105.156.228.65:36963 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:36
[LAN access from remote] from 182.150.144.86:37249 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:35
[LAN access from remote] from 71.92.51.3:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:28
[LAN access from remote] from 176.42.206.69:28451 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:26
[LAN access from remote] from 185.34.3.12:15612 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:21
[LAN access from remote] from 175.180.189.42:1095 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:21
[LAN access from remote] from 222.64.73.79:40959 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:26:06
[LAN access from remote] from 77.73.142.132:24778 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:58
[LAN access from remote] from 108.28.92.68:44851 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:53
[LAN access from remote] from 198.15.119.130:27360 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:53
[LAN access from remote] from 218.68.13.221:2013 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:43
[LAN access from remote] from 92.108.117.99:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:42
[LAN access from remote] from 95.143.223.81:14977 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:41
[LAN access from remote] from 178.66.47.135:29786 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:40
[LAN access from remote] from 36.39.62.132:49998 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:38
[LAN access from remote] from 85.97.220.14:19677 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:38
[LAN access from remote] from 212.64.110.236:41822 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:25
[LAN access from remote] from 5.18.52.141:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:22
[LAN access from remote] from 201.133.150.15:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:20
[LAN access from remote] from 115.202.10.214:7297 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:19
[LAN access from remote] from 86.206.169.57:1024 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:19
[LAN access from remote] from 101.94.185.204:29626 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:19
[LAN access from remote] from 218.251.35.242:12920 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:13
[LAN access from remote] from 103.227.170.206:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:11
[LAN access from remote] from 73.25.226.238:22895 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:10
[LAN access from remote] from 123.240.151.20:48479 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:06
[LAN access from remote] from 125.39.223.252:9500 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:03
[LAN access from remote] from 58.6.139.85:17148 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:25:01
[LAN access from remote] from 117.82.90.170:15269 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:50
[LAN access from remote] from 111.151.72.168:3363 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:49
[LAN access from remote] from 41.141.204.142:1024 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:43
[LAN access from remote] from 218.173.3.53:9143 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:43
[LAN access from remote] from 37.104.123.94:55306 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:42
[LAN access from remote] from 37.55.157.129:62455 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:38
[LAN access from remote] from 81.166.145.189:59028 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:36
[LAN access from remote] from 172.74.0.32:59290 to 10.0.0.5:49623, Saturday, Jun 06,2015 21:24:36
[LAN access from remote] from 121.35.64.245:7339 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:35
[LAN access from remote] from 95.52.109.240:34995 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:34
[LAN access from remote] from 112.238.124.249:9101 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:32
[LAN access from remote] from 92.19.58.219:44822 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:29
[LAN access from remote] from 108.46.119.185:30002 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:25
[LAN access from remote] from 5.141.1.150:32332 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:25
[LAN access from remote] from 88.140.92.10:17529 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:22
[LAN access from remote] from 61.51.186.50:13406 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:22
[LAN access from remote] from 223.64.237.163:14707 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:18
[LAN access from remote] from 79.11.107.196:11807 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:17
[LAN access from remote] from 42.49.165.126:33935 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:17
[LAN access from remote] from 81.193.72.90:54114 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:14
[LAN access from remote] from 110.164.209.191:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:12
[LAN access from remote] from 125.230.26.196:9653 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:11
[LAN access from remote] from 78.210.22.16:19714 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:07
[LAN access from remote] from 39.188.32.54:17944 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:04
[LAN access from remote] from 83.152.108.148:54356 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:03
[LAN access from remote] from 83.149.37.116:12884 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:24:03
[LAN access from remote] from 109.229.68.174:29942 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:58
[LAN access from remote] from 177.207.43.35:25540 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:56
[LAN access from remote] from 14.153.24.169:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:53
[LAN access from remote] from 116.40.210.193:51728 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:37
[LAN access from remote] from 73.31.251.24:27432 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:33
[LAN access from remote] from 178.192.217.27:21496 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:32
[LAN access from remote] from 178.48.189.187:65432 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:30
[LAN access from remote] from 212.36.17.192:43878 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:19
[LAN access from remote] from 92.97.176.159:43611 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:18
[LAN access from remote] from 189.70.73.33:58313 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:17
[LAN access from remote] from 58.216.79.239:1026 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:07
[LAN access from remote] from 101.229.186.151:1590 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:05
[LAN access from remote] from 31.180.67.164:1024 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:23:04
[LAN access from remote] from 181.47.11.169:48580 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:58
[LAN access from remote] from 61.74.166.79:47690 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:56
[LAN access from remote] from 216.58.125.198:60842 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:53
[LAN access from remote] from 209.222.15.232:26666 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:51
[LAN access from remote] from 177.62.46.133:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:39
[LAN access from remote] from 2.150.33.17:16991 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:37
[LAN access from remote] from 145.255.179.5:25052 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:36
[LAN access from remote] from 109.133.164.20:27907 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:36
[LAN access from remote] from 1.197.42.236:7708 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:27
[LAN access from remote] from 2.137.70.149:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:25
[LAN access from remote] from 85.26.164.236:14464 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:25
[LAN access from remote] from 85.253.116.209:42702 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:23
[LAN access from remote] from 189.125.58.138:1885 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:22
[LAN access from remote] from 118.35.207.10:56457 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:22
[LAN access from remote] from 182.42.185.59:5443 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:18
[LAN access from remote] from 5.12.141.166:26401 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:18
[LAN access from remote] from 83.69.0.7:49002 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:15
[LAN access from remote] from 1.62.174.133:59002 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:22:08
[LAN access from remote] from 120.95.72.194:51504 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:52
[LAN access from remote] from 188.243.168.161:53167 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:51
[LAN access from remote] from 37.53.212.36:1024 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:43
[LAN access from remote] from 87.252.225.66:20192 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:43
[LAN access from remote] from 121.133.90.219:36080 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:39
[LAN access from remote] from 197.218.66.53:42477 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:32
[LAN access from remote] from 105.102.206.179:47620 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:29
[LAN access from remote] from 95.46.128.80:47451 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:21
[LAN access from remote] from 111.122.35.120:9508 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:20
[LAN access from remote] from 77.37.211.11:57392 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:13
[LAN access from remote] from 165.166.225.192:52724 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:12
[LAN access from remote] from 113.57.224.33:30175 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:03
[LAN access from remote] from 85.100.148.78:30444 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:02
[LAN access from remote] from 61.161.72.206:1239 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:21:02
[LAN access from remote] from 203.186.34.30:34301 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:59
[LAN access from remote] from 92.37.91.84:41959 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:54
[LAN access from remote] from 37.19.62.195:14070 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:52
[LAN access from remote] from 120.95.72.183:2099 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:52
[LAN access from remote] from 111.251.31.242:17469 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:51
[LAN access from remote] from 1.27.89.91:3072 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:51
[LAN access from remote] from 50.9.202.121:45682 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:50
[LAN access from remote] from 31.202.211.174:58542 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:43
[LAN access from remote] from 115.136.142.41:17471 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:43
[LAN access from remote] from 217.121.94.14:40500 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:42
[LAN access from remote] from 113.57.186.62:54938 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:38
[LAN access from remote] from 5.40.189.123:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:33
[LAN access from remote] from 88.147.152.231:54912 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:31
[LAN access from remote] from 177.81.168.171:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:31
[LAN access from remote] from 180.158.221.69:49833 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:31
[LAN access from remote] from 213.24.125.123:16723 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:29
[LAN access from remote] from 95.71.127.43:36437 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:28
[LAN access from remote] from 178.70.157.145:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:27
[LAN access from remote] from 223.153.27.157:29640 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:22
[LAN access from remote] from 110.73.55.12:21810 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:21
[LAN access from remote] from 157.55.56.169:40016 to 10.0.0.5:49623, Saturday, Jun 06,2015 21:20:18
[LAN access from remote] from 89.223.47.218:21999 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:12
[LAN access from remote] from 212.20.74.181:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:10
[LAN access from remote] from 220.163.245.118:8026 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:09
[LAN access from remote] from 220.170.111.241:9005 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:08
[LAN access from remote] from 182.178.162.223:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:08
[LAN access from remote] from 77.91.198.63:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:03
[LAN access from remote] from 128.70.116.205:14269 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:02
[LAN access from remote] from 90.58.40.141:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:01
[Time synchronized with NTP server] Saturday, Jun 06,2015 21:20:00
[LAN access from remote] from 62.69.52.82:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:20:00
[LAN access from remote] from 109.127.169.192:16750 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:19:59
[LAN access from remote] from 110.178.15.43:27105 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:19:58
[Internet connected] IP address: 119.224.28.19, Saturday, Jun 06,2015 21:19:34
[Internet disconnected] Saturday, Jun 06,2015 21:17:06
[LAN access from remote] from 220.250.38.191:18379 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:16:30
[LAN access from remote] from 71.92.51.3:6881 to 10.0.0.3:10022, Saturday, Jun 06,2015 21:16:29

8566 posts

Uber Geek
+1 received by user: 2939

Lifetime subscriber

  # 1318570 7-Jun-2015 09:41
Send private message

to diagnose if its a wiring or device issue you really need to get a second VDSL device and try that, if the second device still disconnects then its a wiring issue.

why did you think the R7000 would help? it has nothing to do with the VDSL side of things, you would have been better spending your money on a better modem that supports VDSL. just saying.

you could have someone check your internal wiring and sort out any issues you may have, but if you still have issues after that then the issue is in chorus' wiring. so they will need to send someone out.

i would try used a second device to rule that out, then have the internal wiring checked, then get the isp to have chours check the street wiring.

that wall of infomation doesnt really tell us much

does the modem restart or does it just drop DSL sync?

5452 posts

Uber Geek
+1 received by user: 1903


  # 1318610 7-Jun-2015 10:31
Send private message

That log seems to show only one disconnect - what are all the remote access entries though?


8566 posts

Uber Geek
+1 received by user: 2939

Lifetime subscriber

  # 1318628 7-Jun-2015 11:36
Send private message

torrenting?

BDFL - Memuneh
63630 posts

Uber Geek
+1 received by user: 14092

Administrator
Trusted
Geekzone
Lifetime subscriber

  # 1318649 7-Jun-2015 12:06
Send private message

Again please post modem stats, not log.

If you are using torrent could be the router can't cope with that many connections? Try a different router and modem.




 
 
 
 


13 posts

Geek


  # 1337845 6-Jul-2015 13:27
Send private message

I am with Slingshot and am having frequent disconnect issues with my VDSL.  This has been ongoing since I joined the ISP.  These are PPP errors where the "internet" light on my router flicks between solid green, to off, to red and so on.  The DSL light on my router is mostly solid green, however sometimes it will flash green several times before a disconnect.

Firstly - Apologies for the length of this thread, however I figured details would help those in the know (hopefully) help me solve the problem.
Secondly – I work in IT so am reasonably technically proficient.  I won’t proclaim to know low level networking/comms enough that I can understand how to troubleshoot this problem to resolution on my own though.

My setup is:

 

  • Approx 200m from the cabinet.
  • Slingshot supplied router (yuk) - VB104W
  • Ethernet cable from Slingshot router to Netcomm ADSL router being used only as a WiFi bridge.  All other functions disabled.
  • Netcomm WiFi network running both 2.4 and 5Ghz 802.11b/g/n
  • Approx 10 WiFi devices connected to the WiFi including Apple TV, smart phones, tablets, and printer.
  • 2x PC's plugged into the Slingshot router via Ethernet.
  • Sonos bridge physically plugged into the Netcomm router via ethernet cable.
  • Netcomm WiFi range extender extending the 2.4Ghz range of my WiFi router to my sleep out.
  • Slingshot router is DHCP server for whole home.
  • LOTS of video streaming going on in the house with up to 4x HD video streams (Netflix or iTunes) running concurrently.  Works fine when no disconnects.
  • Phone line NOT plugged into any alarm box (though I do have an alarm in the house).
  • No fax.
  • Multiple physical phone jack points in the house, however only one in use.
  • Slingshot router is plugged into a power board sharing power with many other electrical items (though after reading another article on here about VDSL quality I have now moved it to its own wall socket).
  • No torrenting or running of any servers on my site.

My router logs see the problem as follows: 

 

  • 2015-07-06 09:09:54 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 09:09:59 [6] syslog: Accessor:[ACS] Method:[GetNoti] Para:[] Result:[00000000]
  • 2015-07-06 09:10:00 [6] syslog: Accessor:[ACS] Method:[ClearNoti] Para:[] Result:[00000000]
  • 2015-07-06 09:24:00 [5] syslog: Accessor:[CPE] Method:[AUTH] Para:[] Result:[] User admin session timeout and auto logout
  • 2015-07-06 09:24:02 [5] syslog: Accessor:[CPE] Method:[AUTH] Para:[] Result:[] User admin login success
  • 2015-07-06 11:34:57 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[] Result:[9001] Wan Link was Disconnected
  • 2015-07-06 11:34:57 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:34:57 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:35:11 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:35:22 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:35:46 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:36:22 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:36:23 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[User=[username]@slingshot.co.nz ip=[IP ADDRESS]] Result:[0] Wan Link was Connected
  • 2015-07-06 11:36:23 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:36:27 [6] syslog: Accessor:[ACS] Method:[GetNoti] Para:[] Result:[00000000]
  • 2015-07-05 23:36:30 [6] syslog: Accessor:[ACS] Method:[ClearNoti] Para:[] Result:[00000000]
  • 2015-07-06 11:38:20 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[] Result:[9001] Wan Link was Disconnected
  • 2015-07-06 11:38:20 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:38:20 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:38:33 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 1970-01-01 13:00:43 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 1970-01-01 13:00:43 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[User=[username]@slingshot.co.nz ip=[IP ADDRESS]] Result:[0] Wan Link was Connected
  • 1970-01-01 13:00:43 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 1970-01-01 13:01:09 [6] syslog: Accessor:[ACS] Method:[GetNoti] Para:[] Result:[00000000]
  • 2015-07-06 11:43:08 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[] Result:[9001] Wan Link was Disconnected
  • 2015-07-06 11:43:08 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:43:08 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:43:25 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:43:39 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:43:40 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:43:40 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[User=[username]@slingshot.co.nz ip=[IP ADDRESS]] Result:[0] Wan Link was Connected
  • 2015-07-06 11:43:41 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:43:48 [6] syslog: Accessor:[ACS] Method:[GetNoti] Para:[] Result:[00000000]
  • 2015-07-06 11:43:49 [6] syslog: Accessor:[ACS] Method:[ClearNoti] Para:[] Result:[00000000]
  • 2015-07-06 11:44:14 [5] syslog: Accessor:[CPE] Method:[AUTH] Para:[] Result:[9007] Not found session 295089e7, user login check failed
  • 2015-07-06 11:51:11 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[] Result:[9001] Wan Link was Disconnected
  • 2015-07-06 11:51:11 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:51:11 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:51:26 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:51:43 [5] syslog: Accessor:[CPE] Method:[INFORM] Para:[] Result:[0] CPE periodically inform to ACS!
  • 2015-07-06 11:51:43 [6] syslog: Accessor:[CPE] Method:[NotiInform] Para:[type=2] Result:[0]
  • 2015-07-06 11:51:43 [5] syslog: Accessor:[CPE] Method:[PPPoE] Para:[User=[username]@slingshot.co.nz ip=[IP ADDRESS]] Result:[0] Wan Link was Connected

I have had many troubleshooting calls with Slingshot, and many call outs from a Chorus engineer.  Generally speaking the main issue I have with this process is that Slingshot works to remove themselves from the cause of the problem rather than owning the problem from end to end.  That doesn’t result in a good customer experience. Each Chorus visit results in the Chorus engineer telling me that the signal quality to the cabinet is excellent and I get speeds of around 30Mbps down and 10 up (when it's working).  The last visit resulted in the Chorus guys changing the physical cable going from my house (terminated at the eve of my roof) to the junction box on the footpath (via a power pole).  Apparently they were supposed to do that during the original install but didn’t.  Aside from one repeat issue during the last few months the problem has never returned and performance has been very stable, until last week.  Last week Vector came and replaced the power pole outside my house (the one that the copper phone/VDSL cable runs via to my house).  Since then the problem has returned with a vengeance.  Constant disconnections, especially during peak times.

I am going through a process of elimination to try and isolate the problem.  At this stage I personally can't rule anything out, although I do find it hard to believe any of my own equipment could be playing a role.  I have done my best to eliminate anything within my house as being part of the problem.  Possible contributors to the problem:

1) My own setup:
I have disconnected everything from the Slingshot router to see if it is stable.  With nothing connected it often is very stable (however there are still some disconnects).  That doesn’t help, but I still don’t see how there is anything in my house that could be impacting the stability of my PPP connection.  Even if I go through a process of slowly reconnecting my things to the infrastructure how does that help me?  I need it all connected.  As you’ll see from my setup there is nothing unusual on my network.  Will this just lead me to concluding that I need a new router because the current one can’t handle so many devices/connections?  Should the number of connected devices result in PPP errors?  I don’t know.

2) Router type/quality and or config:
This has been constant throughout.  I’ve been through multiple factory resets and config verifications over the phone with Slingshot and to no avail.  Conversations with Slingshot about swapping out the modem to see if a new one improves the situation always result in them telling me that I should borrow one from a friend and try it out (like I know hundreds of people with VDSL that are willing to forgo home broadband for a day or two while I use their router), otherwise they could send me a new one, however they will charge me for the old one it if it’s not faulty.  Considering how intermittent this problem is it’s likely that I would end up being charged.  Sufficed to say I haven’t done this yet. 

NOTE TO SLINGSHOT: It would make sense for you to improve your process so that a router swap out was much easier – at least so it could be eliminated as the source of the problem.  Perhaps keep a known good test router or two handy, then send those out to customers to try?  If they don’t return them then yes charge them for it, but don’t just charge them because their current one isn’t faulty.  Good customer service will focus on resolving the customer issue and doing anything you can to help that process of elimination go smoothly.  Bad customer service (like the service you provide now) is one where you just try to eliminate yourselves from the issue (your own view of what that is), then walk away.

3) Wiring from jack point to cabinet:
I read that cable quality plays a key role in VDSL performance so I'm wondering what Chorus is actually obligated to install/replace when it comes to physical cable when they do the installation. Pretty much the only piece of cable that hasn’t changed since the VDSL install is the cable from the eve of the house to the new jack point (in the roof cavity).  That’s about 2m long (max) before the cable is broken and attached to a line splitter (piece of plastic with those screw holes in it that other cables are plugged into).  Then two new cables are fed into that – one of which goes down to my office (2-3m away) for phone and VDSL jack points, and one which feeds several other jack points (not in use) throughout the house.  Was Chorus supposed to change that cable during the install? 

So I am at a loss as to how to fix the problem.  The most logical next steps I see are:
1) Clean up the remaining cable inside my roof; perhaps disconnecting the other jack points entirely.  Why would they be contributing when they're not in use though?  Why would the line quality be so clear?  Should Chorus not have replaced all cable to the VDSL jack point when they did the VDSL install?
2) Replace the router.  I would much rather just test out a replacement router that Slingshot could send me as I don’t want to spend $300 on a new router if it’s not the cause of the problem.  Also if I DO need to spend the money on a new router I’m not going to want to buy the same one that caused me all the problems in the first place.

Any thoughts/comments/suggestions are welcome.

8566 posts

Uber Geek
+1 received by user: 2939

Lifetime subscriber

  # 1337892 6-Jul-2015 14:39
One person supports this post
Send private message

i personally think that you should eliminate your house wiring and then after that you can put the pressure on slingshot to sort the issue out.

poor wiring can cause frequent disconnections, my brother in law had issues with their line and it turned out one of the street feed ins was partially broken which was causing disconnects every few hours. fixed that problem and its been good since.

there could be an issue within your house causing the issue, so i would elminate it if possible.

do you have a master filter/splitter? should look like this: https://www.ascent.co.nz/productspecification.aspx?itemID=408072

13 posts

Geek


  # 1337895 6-Jul-2015 14:45
Send private message

Jase2985: i personally think that you should eliminate your house wiring and then after that you can put the pressure on slingshot to sort the issue out.

poor wiring can cause frequent disconnections, my brother in law had issues with their line and it turned out one of the street feed ins was partially broken which was causing disconnects every few hours. fixed that problem and its been good since.

there could be an issue within your house causing the issue, so i would elminate it if possible.

do you have a master filter/splitter? should look like this: https://www.ascent.co.nz/productspecification.aspx?itemID=408072


Jase2985 - Thanks for the feedback.  Short answer on master filter/splitter is: I don't know.  
- If I did have one where would I find it?  Where is it supposed to be fitted?  
- Is this something Chorus should have installed at the initial installation?  

Thanks

8566 posts

Uber Geek
+1 received by user: 2939

Lifetime subscriber

  # 1337899 6-Jul-2015 14:50
One person supports this post
Send private message

they should have installed one if they were instructed by your ISP, generally speaking most ISP's include it as part of the installation process but i dont know if slingshot does or not.

It would be in the ETP. where the street cable meets the house, or some where along the run to the first jackpoint.

if the house wiring is sctill connected and your not using any phones this can still cause issues with reflections and can lead to interference and dropouts. hence why you should remove the connections to the other jacks or isolate them with a filter/splitter.

13 posts

Geek


  # 1339972 9-Jul-2015 13:36
Send private message

According to the Chorus tech who has been troubleshooting the problem for me he says the lines are split as there are two separate jack points (One for the phone line and one for the VDSL) therefore that effectively is a splitter/filter.  I don't reckon there is any kind of filter/splitter (like the link you have provided) anywhere in the house though.  I know the installer didn't put anything in the wall behind the jack point, I know there is no filter in the roof as the installer never went in the roof, and there is nothing at the point where the street cable meets the house either.

He's now told me it must be the modem (because the signal he's getting to the Cabinet is so strong) so he's sending the job back to Slingshot.

Does this make any sense?

Regards


13 posts

Geek


  # 1340029 9-Jul-2015 14:37
Send private message

Also here are my current router stats.  

Router stats

282 posts

Ultimate Geek
+1 received by user: 76


  # 1340039 9-Jul-2015 14:49
Send private message

HI Quaywe,

You still haven't posted the modem stats as requested several times. These are not the logs - they should show things like line speed, attenuation, etc.

 

You also haven't tried a new modem.

The fact of the matter is it's either the modem or the wiring, and a temporary modem would let you know either way. You say you don't have any friends with VDSL that want to go without internet for a couple of days, and fair enough, but what if you asked one of your friends to swap for a few days. This way if they start getting problems and you don't, you can be even more sure it is the modem. If they have concerns, promise them you'll swap back as soon as they get problems if they do.


GM

282 posts

Ultimate Geek
+1 received by user: 76


  # 1340041 9-Jul-2015 14:50
Send private message

I see the stats are there now - appeared while i was typing...

 1 | 2
View this topic in a long page with up to 500 replies per page Create new topic



Twitter and LinkedIn »



Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Xero announces new smarter tools, push into the North American market
Posted 19-Jun-2019 17:20


New report by Unisys shows New Zealanders want action by social platform companies and police to monitor social media sites
Posted 19-Jun-2019 17:09


ASB adds Google Pay option to contactless payments
Posted 19-Jun-2019 17:05


New Zealand PC Market declines on the back of high channel inventory, IDC reports
Posted 18-Jun-2019 17:35


Air New Zealand uses drones to inspect aircraft
Posted 17-Jun-2019 15:39


TCL Electronics launches its first-ever 8K TV
Posted 17-Jun-2019 15:18


E-scooter share scheme launches in Wellington
Posted 17-Jun-2019 12:34


Anyone can broadcast with Kordia Pop Up TV
Posted 13-Jun-2019 10:51


Volvo and Uber present production vehicle ready for self-driving
Posted 13-Jun-2019 10:47


100,000 customers connected to fibre broadband network through Enable
Posted 13-Jun-2019 10:35


5G uptake even faster than expected
Posted 12-Jun-2019 10:01


Xbox showcases 60 anticipated games
Posted 10-Jun-2019 20:24


Trend Micro Turns Public Hotspots into Secure Networks with WiFi Protection for Mobile Devices
Posted 5-Jun-2019 13:24


Bold UK spinoff for beauty software company Flossie
Posted 2-Jun-2019 14:10


Amazon Introduces Echo Show 5
Posted 1-Jun-2019 15:32



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.