Forum Home
Press F1
Thread ID: 142785	2016-09-09 09:16:00	Latency, timeouts, lost connections	pctek (84)	Press F1

Post ID	Timestamp	Content	User
1425840	2016-09-12 10:29:00	clicks on Chrome and the modem dies. Totally. Actually I vaguely remember something like that happening ages ago. :confused: I'll "try" to find out or remember what was the cause.	wainuitech (129)
1425841	2016-09-12 22:16:00	He's not running any torrents by any chance? I discovered I could kill one of my old Modems by launching uTorrent on a windows XP machine. 100% effective at killing the modem as long as it was running XP and uTorrent, proved it many times before replacing the modem. I think some modems/routers are just not up to heavy traffic loads and certain combinations of running programs just overload them, not sure if that's what's happening to you especially with multiple different devices tested but it's possible. And then if it's just Chrome, use another browser :)	dugimodo (138)
1425842	2016-09-13 02:33:00	He's not running any torrents by any chance? And then if it's just Chrome, use another browser :) No. It's not. I have Chrome although mostly I use FF. Granddaughter uses Chrome on my PC. He's been using Chrome this whole time I had the issue. He has used Chrome for nearly a year before the issue arrived. It's not anything to do with Chrome, it's just bizarre how I finally cure it, but oh no, he walks in and the issue is back. I have a brand new modem in now. He has a brand new network cable now too. We'll see what happens when he gets in tonight. I blame his boots.	pctek (84)
1425843	2016-09-13 19:00:00	I blame his boots.Yeah, bad shoes are often the core issue :eek:	Greg (193)
1425844	2016-09-13 20:25:00	Brand new TPLink modem in now. (Number 4) And changed the network cable to his PC, although I doubt the old one was dodgy... Anyway: TPLink Netgear SNR Margin (0.1 dB): 121 120 130 120 Attenuation (0.1 dB): 65 10 15 0 Bandwidth (Kbps): 15964 1144 15419 1208 No dropped packets, no errors since. No lag either....	pctek (84)
1425845	2016-09-13 22:58:00	TPLink != Netgear? Happens a lot with shitty routers like that, you'll often find you can't get in to the WebUI when there's "load" on the router. It's why I can't use one of those %@(*#$ Thomson / Technicolor / Huawei routers they give away (They only cost your ISP like $14 anyways)... Then, basically if the router is struggling with the load from the additional machine, any number of other issues will happen, like dropping the WAN entirely, packets disappearing into the ether, WebUI inaccessible, and a bunch of other thing.	Chilling_Silence (9)
1425846	2016-09-14 02:41:00	TPLink != Netgear? Happens a lot with shitty routers like that It's why I can't use one of those %@(*#$ Thomson / Technicolor / Huawei routers t. I know your pet hates on modems. I had the Thompson for 6 years, never had an issue. Probably still don't. TPlink I like the interface and info. The Netgear is my sons, not so keen on it's lack of info is about all. I've had loads of brands over the years. The one I'd avoid is Huawai. The rest, they're generally all fine until they die. Whatever brand.	pctek (84)
1425847	2016-09-14 02:54:00	What's anooying is all the pet theories I got: It's the bell phone. It's the 2 empty jackpoints. It's the modems. I should have a splitter/VDSL/fibre instead. Well, the only thing I can really put it down to, is most likely the Caller ID box. jackpoints as is, bell phone as is,phone wiring as is. And bugger fibre. When it's A)Cheaper the copper B)I stop reading about contractor messes maybe I'll think about it. And bugger the splitter. I'd have rewired the jackpoints if it came to it.	pctek (84)
1425848	2016-09-14 03:02:00	You said the issue now you have removed your Caller ID box is only occurring when your Sons PC was on, but when it's shut down the issue doesn't occur? Perhaps some additional isolation may be a wise idea then.	Chilling_Silence (9)
1425849	2016-09-14 06:03:00	I empathise with any frustration you are feeling, these kind of faults can take forever to pin down. It took weeks to sort out my previous issues. You just have to be systematic and eliminate possibilities one by one. If you think it's the caller ID box then remove it for a while and see. If you don't you'll just never know. Fibre is cheaper than copper isn't it? or at least the same price and faster. E.G. sparks prices www.spark.co.nz Q&gclsrc=aw.ds&dclid=CN622-CHjs8CFcSCvQodgcQG3A Contractor messes, well that's a valid concern. I didn't have any issues for my connection though. I got fibre, picked the 100/20 plan for the same price as my old unlimited VDSL plan just because 30/10 fibre would not have been any faster and for the price difference I'd rather have the extra speed. I was happy with my VDSL but upgraded anyway, taking advantage of the free install offer while it's around. The splitter suggestion is a good one and made for a reason. Spark/chorus will not even connect VDSL without upgrading to one because of the constant issues and poor performance of plug in filters. Splitters are not just better quality and more reliable, they are also a better class of filter with better characteristics. Also as I mentioned earlier when I'm trying to solve these issues I just completely remove all house wiring from the equation while testing to eliminate all the possible causes at once. You call them pet theories, I call them helpful suggestions of things to try :) If there was an obvious solution you would have found it already. Any that you choose not to try, that's up to you but if it turns out it would have solved the issue that's on you also.	dugimodo (138)
1 2 3