Page 1 of 1

Can't connect to WebUI after update

Posted: Mon Aug 31, 2015 12:17 pm
by ant!
Hi!
Just a warning: I am not very familiar with network things...

I had my T-Link WR941N (v3) updated from 1.7.2 to 1.8 about a week ago. I use this router only as a bridge wifi->LAN since I needed some LAN connections in a room where only wifi is available.
Today I experienced some hanging, had to restart twice and it was not stable (before the update and also last week after the update it was...). Since I accidentally updated before using the preserve settings option, I thought this might cause the issue. So, short backup and updating to 1.8 again, this time without the preserve setting option.

Not totally sure if something failed, all LEDs look normal (recognize new pluged in LAN devices), but I have no access to the WebUI anymore. Since the settings were not preserved, I have of course no access via wifi, but have to use a LAN connection. But 192.168.1.1 doesn't give me any access, neither do I get a ping response when scanning with Angry IP scanner 192.168.1.1 to 192.168.1.24.

I tried using the failsafe mode https://www.gargoyle-router.com/wiki/do ... e_recovery, but ssh root@192.168.1.1 gives no answer, neither telnet 192.168.1.1 when pressing the reset (not sure if at the good moment though. Wireshark confuses me at the moment, no idea how to run it as described in the documentation. I was not seeing the Power-LED flashing as described, but some general LED blinking). telnet was giving

Code: Select all

telnet: Unable to connect to remote host: Connection refused
. My PC was of cause static 192.168.1.2.

So, I guess I just try somehow the wrong IP and cannot find where to search it, since the LEDs look fine?

Any idea?

Re: Can't connect to WebUI after update

Posted: Mon Aug 31, 2015 1:26 pm
by ant!
After another 20min plugging in and out: Suddenly the connection was there and everything running fine now, could connect to 192.168.1.1. No idea what I did, but it worked...

Re: Can't connect to WebUI after update

Posted: Mon Aug 31, 2015 4:47 pm
by nworbnhoj
You have made a good go at the failsafe recovery - well done!

But I reckon that you have faulty network cable