I have been using the Talk Talk fibre connection for at least 2 years and in general it has performed to specification. Lately though, I am getting two or three, sometimes 4 dropped connections every day. I vpn into work as I work from home most days and it is getting annoying. I've seen various messages about fibre modem and router software perhaps needing update but no mention of this from India. Openreach connected a BT master socket directly into their box on the outside wall of the house, independent of our existing phone lines and master socket, of which they had full knowledge. The master socket has the usual RJ-45 and BT phone connectors on the outside, and the RJ45 is connected directly to their fibre modem. The ethernet output from this is routed directly to a HUAWEI HG533 router via Class 5 ethernet cabling, on the upper floor. The router then supplies various wireless devices around the house, as well as feeding wired ethernet signal into a 1Gbit switch to service various hard wired ethernet devices. Both the modem, and the router and switch are on APC UPS power supplies, so mains dropouts cannot be blamed. (There is no indication on any of the UPS's of any power glitches however). Curiously, when the service drops out, restarting either the modem OR the router will normally restore service. This might indicate a problem with the ethernet port on either the modem or the router, or the connecting cable, but the cable checks out OK on an ethernet cable tester. Does anyone have any suggestions on how I can do Talk Talk's job for them and find the cause of the problem since whenever I call, the line test shows nothing, which is probably due to the connection having been restarted by then. I'd be happy to test with a new modem and a new router, as the alternative is to switch to fibre from Virgin, who are not renowned for good customer service either, but at least it would get me away from BT's crap lines. My last conversation with someone in support was interrupted by noise on a poor line - I did query this and line problems were suggested but obviously nothing to do with this issue.
↧