cancel
Showing results for 
Search instead for 
Did you mean: 
Micker
Contributor
390 Views
Message 1 of 18

Service worse after engineer visit

I have been having problems with fibre from it was installed on 23rd April.

Connection always dropping at least 1-2 days and orange light and as a consequnece the line speed drops.

 

Engineer visted on Tuesday 19th April and now service ir dropping to orange light every 15-20 minutes and has rendered service unusable, when it is active it is sitting around 42mb.

 

Rang this morning and sending engineer again next Monday, very disappointed and frustrated with BT expected better, especially since I was a TalkTalk customer, at least with them I had constant speed in the early 60s

0 Ratings
Reply
17 REPLIES 17
Distinguished Sage
Distinguished Sage
380 Views
Message 2 of 18

Re: Service worse after engineer visit

can you post stats from your hub  if hh6 then advanced settings then technical log information

are you using the test socket with a filter to see if that helps stability

try quiet line test  dial 17070 option 2  should be quiet and best with corded phone



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
0 Ratings
Reply
Micker
Contributor
343 Views
Message 3 of 18

Re: Service worse after engineer visit

Service now orange every couple of minutes so I effectively have no service.

0 Ratings
Reply
Micker
Contributor
342 Views
Message 4 of 18

Re: Service worse after engineer visit

17:46:30, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:46:30, 20 Jun. WAN Sensing Auto sensing Running
17:46:30, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:46:28, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
17:46:28, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
17:46:28, 20 Jun. WAN DHCPv6 events: BOUND
17:46:28, 20 Jun. WAN Sensing Auto sensing Running
17:46:28, 20 Jun. Success - secondary DNS servers
17:46:28, 20 Jun. Success - primary DNS servers
17:46:28, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
17:46:27, 20 Jun. WAN DHCPv6 events: INIT
17:46:21, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:46:21, 20 Jun. WAN Sensing Auto sensing Running
17:46:21, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:46:20, 20 Jun. WAN Auto-sensing detected port DSL WAN
17:46:14, 20 Jun. WAN Sensing Auto sensing Running
17:46:14, 20 Jun. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
17:46:08, 20 Jun. DSL Link Up: Down Rate=46076kbps, Up Rate=17682kbps; SNR Margin Down=5.8dB, Up=6.2dB
17:45:01, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:45:01, 20 Jun. WAN Sensing Auto sensing Running
17:45:00, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:58, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
17:44:58, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
17:44:58, 20 Jun. WAN DHCPv6 events: BOUND
17:44:58, 20 Jun. WAN Sensing Auto sensing Running
17:44:58, 20 Jun. Success - secondary DNS servers
17:44:58, 20 Jun. Success - primary DNS servers
17:44:58, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
17:44:57, 20 Jun. WAN DHCPv6 events: INIT
17:44:51, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:51, 20 Jun. WAN Sensing Auto sensing Running
17:44:51, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:50, 20 Jun. WAN Auto-sensing detected port DSL WAN
17:44:44, 20 Jun. WAN Sensing Auto sensing Running
17:44:44, 20 Jun. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
17:44:37, 20 Jun. DSL Link Up: Down Rate=46076kbps, Up Rate=17682kbps; SNR Margin Down=5.9dB, Up=6.2dB
17:44:36, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:36, 20 Jun. WAN Sensing Auto sensing Running
17:44:36, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:34, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
17:44:34, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
17:44:34, 20 Jun. WAN DHCPv6 events: BOUND
17:44:34, 20 Jun. WAN Sensing Auto sensing Running
17:44:34, 20 Jun. Success - secondary DNS servers
17:44:34, 20 Jun. Success - primary DNS servers
17:44:34, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
17:44:33, 20 Jun. WAN DHCPv6 events: INIT
17:44:25, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:24, 20 Jun. WAN Sensing Auto sensing Running
17:44:24, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:44:23, 20 Jun. WAN Auto-sensing detected port DSL WAN
17:44:16, 20 Jun. WAN Sensing Auto sensing Running
17:44:16, 20 Jun. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
17:44:10, 20 Jun. DSL Link Up: Down Rate=46076kbps, Up Rate=17682kbps; SNR Margin Down=5.9dB, Up=6.2dB
17:40:00, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:40:00, 20 Jun. WAN Sensing Auto sensing Running
17:40:00, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:39:54, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
17:39:54, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
17:39:54, 20 Jun. WAN DHCPv6 events: BOUND
17:39:54, 20 Jun. WAN DHCPv6 events: INIT
17:39:54, 20 Jun. WAN Sensing Auto sensing Running
17:39:54, 20 Jun. Success - secondary DNS servers
17:39:54, 20 Jun. Success - primary DNS servers
17:39:54, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
17:39:00, 20 Jun. WAN Auto-sensing detected port DSL WAN
17:39:00, 20 Jun. DSL Link Up: Down Rate=46076kbps, Up Rate=17682kbps; SNR Margin Down=0.0dB, Up=0.0dB
17:37:53, 20 Jun. Detect and configure Ethernet port1 as LAN
17:37:53, 20 Jun. WAN Auto-sensing last connection port: DSL WAN
17:25:01, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:25:01, 20 Jun. WAN Sensing Auto sensing Running
17:25:01, 20 Jun. WAN Sensing Auto sensing Complete, interface selected
17:24:59, 20 Jun. WAN Sensing Auto sensing Running
17:24:59, 20 Jun. Success - secondary DNS servers
17:24:59, 20 Jun. Success - primary DNS servers
17:24:59, 20 Jun. WAN connection WAN2_INTERNET_PTM connected
17:24:59, 20 Jun. WAN IPv6 Global unicast prefix / length: 2a00:23c4:ca6:f100::/56
17:24:59, 20 Jun. WAN IPv6 Global unicast address allocated: 2a00:23c4:ca6:f100::1/64
17:24:59, 20 Jun. WAN DHCPv6 events: BOUND
17:24:58, 20 Jun. WAN DHCPv6 events: INIT
17:24:52, 20 Jun. WAN Sensing Auto sensing Complete, interface selec
0 Ratings
Reply
Micker
Contributor
341 Views
Message 5 of 18

Re: Service worse after engineer visit

Part of WAN Category

0 Ratings
Reply
Micker
Contributor
337 Views
Message 6 of 18

Re: Service worse after engineer visit

Product name:Smart Hub
Serial number:+088044+1801001519
Firmware version:v0.09.05.11160-BT
Firmware updated:Mon Apr 23 20:09:42 2018
Board version:01
DSL uptime:0 days,00 Hours01 Mins03 Secs
Data rate:17.682 Mbps / 46.076 Mbps
Maximum data rate:22.202 Mbps / 52.738 Mbps
Noise margin:6.2 / 5.9
Line attenuation:25.2 / 19.1
Signal attenuation:24.9 / 19.1
Data sent / received:1.1 MB / 33.2 MB
Broadband username:bthomehub@btbroadband.com
BT Wi-fi:No
2.4 GHz wireless network name:BTHub6-J537
2.4 GHz wireless channel:Automatic (Smart Wireless)
5 GHz wireless network name:BTHub6-J537-5
5 GHz wireless channel:Automatic (Smart Wireless)
Wireless security:WPA2
Wireless mode:Mode 1
Firewall:Default
MAC address:EC:F4:51:C9:6B:02
Software variant:-
Boot loader: 0.1.6-BT (Fri Sep 9 10:05:09 2016)
0 Ratings
Reply
Distinguished Sage
Distinguished Sage
322 Views
Message 7 of 18

Re: Service worse after engineer visit

are you now connected to test socket with a filter?

did you try quiet line test?



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
0 Ratings
Reply
Micker
Contributor
318 Views
Message 8 of 18

Re: Service worse after engineer visit

Tried quiet test seems OK, but not connected to test socket
0 Ratings
Reply
Micker
Contributor
314 Views
Message 9 of 18

Re: Service worse after engineer visit

Have it on test socket now
0 Ratings
Reply
Micker
Contributor
277 Views
Message 10 of 18

Re: Service worse after engineer visit

Have it on test socket with filter and been up now constant for 13 hours, so speed still low at 44m, does that mean faulty faceplate and who changes it
0 Ratings
Reply