I recently observed the same symptoms, and my solution isn't listed here, so in case this helps someone. It is way too much of a security risk and if you need to open ports instead of uPnP's automated method, do it manually and learn what this entails.Īlso, disable remote administration and set a strong admin password. I would strongly suggest to always disable uPnP as mligor has suggested. This may be at worst, a specific attacker, or otherwise anything of: some buggy process on any connected device, or some network connection type (overloading, bug, etc).Īs suggested, the router running out of RAM (and a bug in handling this condition) is a common problem, especially under heavy load.Īlso, check that there isn't some sort of firewall setting on the router (or even your PC) blocking your client IP from accessing the web interface. If not, it suggests that something is interfering when other connections (WAN, LAN, WiFi) are plugged-in/active. However, try some basic troubleshooting first:ĭisconnect the WAN-side cable (phone line or ethernet, assuming it is either of these).Īlso applies to LAN-side access: Make sure you access it with ethernet cable and isolate the router to just the one ethernet cable and client PC that you're trying to access the config page with.ĭo all this before booting the router to make sure the boot is 'clean'. If it is one of those lovely TP-Link bugs, then all bets are off.

Tp link advanced setup