Tech-services-at-sky.neat-url.com



Onsite visit Weds 20th Nov 20192 Q meshes had joined together, escalated to us via textTAPS on 12th Nov 2 Customers one at No9 and the other one at No7, No7 was able to see the planner and the Netflix account from No9, and No9 was seeing some recordings in their planner which they hadn’t set, she just thought it was the young child who had been pressing buttons.On arrival at No9, we ran a Chrome scan which only showed a stand-alone router, shown in the photos above. Upon looking at the Q1tb box it was connected to the wrong SSID, it was showing as it was connected to No7 (SSID SKYHZPGW) When it should be connected to SSID SKYB870C.72285381329500The BBTT engineer who attended was already connected to the neighbour from his previous visit on the 15th Nov, He did a Chrome scan and he could see the Q1tb connected to the Q2tb system at No7 (below)We factory reset the Q1tb at No9, and meshed it back onto her hub, which then joined her network, and we also saw the Q1tb drop off from No9.Upon speaking to Kenneth Johnstone, he suggested we put a hub2 into the customer at No9 as it could potentially mesh together again as the boxes could remember the credentials, this would stop the mesh being active at the Q1tb house and stop any potential future issues.Both systems checked before leaving, both fully operational, and both able to only see their own planners and their own Netflix accounts.In summary, we are unsure of what caused the issue, as there were no powerline adaptors in either property, No9 had no ethernets connected to the hub, No7 had 2 ethernets, one to the main Q2tb box and one to his desktop computer.We can only summarise at some point they may have shared Wi-Fi passwords, or Netflix account log in details, we asked both sets of customers, and they were both sure they hadn’t shared any details. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download