[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
> I've tried on a different machine and the problem is the same there - > I've also reset the router to its factory settings, but none of this > has made a difference. (Technically a modem not a router, according to the 120 description... </pedant>) My first step would be to swap the modem/router out for something else if you have it. If symptoms persist with another box, dig a little deeper, runs adsl tests in the router supports it (some drayteks do), listen on the line for noise, consider escalating the issue to BT, check for newer firmware, put it in the corner and give it a stern telling off, etc. We're exclusively a draytek shop now. 2820's and 2830's - I love them. Good mid-level well featured bits of kit, we run, um, six of them at the moment. They cope well with varying line qualities and have the best vpn compatibilities I've yet met. The latest (last week) was actually capable of ipv6 once firmware was upgraded. I now have exactly *one* piece of v6 capable network hardware, should my ISP ever decide to roll it out :) We used to run netgear dg834's, but around v3 onwards they started being really unreliable and got very hot. That said... I have had two Drayteks fail in four years. One would start, then as soon as sync was achieved, reset itself. Rinse and repeat. Another would stop routing after hours or days. Responded fine to ui, just wouldn't route to the internet. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq