In reply to a post by andrewh1973:

Have I got a dud router or has anyone else seen this problem?

It's not just you, one I installed for a client does the same.

Don't think the two were related, but a few weeks later it's PSU died and TP-Link support said it wasn't covered by the warranty, only the router itself is, so I'd have to buy a new one. The PSU from the clients old router fitted, so it's using that now. Put me off using TP-Link kit again though.

I have an another old router that I used to use before both of these, a D-Link DSL-504. That has never crashed, and I dug it out recently and it still works (it just connects at half the speed of an ADSL2 router and lacks wifi, which is why it's no longer used). It's just coincidence that I happen to have this kind of problem with two different routers... if you google the D-Link DSL-2640R you'll see people have had all sorts of problems with it, seems to me that is was just not one of D-Link's better products (and that's putting it kindly.. any router that can screw up displaying the system log - half the time you'd get a garbled HTML page showing inline javascript! - clearly has quite basic problems with its firmware!). The TP-Link clearly has something affecting it, so if it does this again now that it's back on the default sub net, I'll go back to the D-Link and just leave the TP-Link powered up but disconnected from everything for 2 days and see if it still plays up then. Would prove out if a client is causing the problem (and if it is, there's still a problem with their firmware - no client doing basic operations should be able to crash a routers web and telnet admin sub systems)...

Edited by andrewh1973 (Sun 05-Aug-12 10:13:14)

Hmm interesting, I have mused that it could be a power supply issue also. Not impressed by TP-Link's response to your problem though.

Thanks for letting me know I'm not alone!

I might have made it sound like the replacement PSU fixed it, but it didn't. You still have to reboot it to get into the web interface after a few days. The router itself still keeps working fine, you just can't get to the settings.

Are you doing something like collecting stats for Routerstats or something on a regular basis?
I've encountered problems with UIs freezing on many different routers when doing that.

Edited by deleted (Sun 05-Aug-12 10:51:44)

Nope. You can log in once OK, leave it a few days not accessing it at all and try again and it doesn't work.

Yup, exactly the same as for me. What hardware version is it?

In reply to a post by NICK_ADSL_UK:

Wherever possible it's always best to use IE 9 for going into the admin panel or updating routers as using other browsers can stall from time to time

Big issue if you don't have any Windows computers!

In reply to a post by jchamier:

In reply to a post by NICK_ADSL_UK:

Wherever possible it's always best to use IE 9 for going into the admin panel or updating routers as using other browsers can stall from time to time

Big issue if you don't have any Windows computers!

Why would any sane person not have a Windows computer?

On a(nother ) serious note though they always generally do work better on IE...

In reply to a post by Pipexer:

Why would any sane person not have a Windows computer?

On a(nother ) serious note though they always generally do work better on IE...

Not in my experience, never had a problem with Firefox and/or Chrome (yuck), or Safari personally, but I prefer Firefox. I have Windows in a VM, just never needed to use it for a (domestic) router configuration page !!

IE9 is the most standards compliant browser MS has ever issued, so if something doesn't work in Firefox/Chrome its unlikely to work in IE9. Unless you have an XP VM with IE 6 (yikes) around.

w3c standards are there for a reason - http://www.w3.org/