Helpy Hyper x.x

[Hyper]

Alrighty problem;

My old router mysteriously stopped working so I got a new one from the ISP...

The new one is a Speedtouch like the last one 5xx something... Latest firmware etc.

So the problem is that I can't get into the router page 192.168.1.254...

I tried making my IP static and going through that IP still the same, tried going through run cmd telnet, same.

It keeps prompting the authorization box and the default password/username do not work.

Also I tried it on a different computer and voila.. Works perfectly so it isn't the routers problem

Which leaves me baffled with no idea what could this shit be from since the old router got on the internet page quite fine like 2 weeks ago.

[Aηdy]

Try clearing your temp files & cookies.

[AnotherMember]

Um, forgive me if I'm wrong but 192.168.1.254 shouldn't be your routers IP.
On the computer that couldn't connect, don't mess with the IPs, leave them to the DHCP to configure and what ever your computers DNS is use that address to connect to the router. But I am 100% sure 192.168.1.254 is the wrong address. It should be 192.168.1.1 or what ever the DNS for that computer is.

[Aηdy]

Um, forgive me if I'm wrong but 192.168.1.254 shouldn't be your routers IP.

Shouldn't?

It can be pretty much anything. My old router was 192.168.0.286

[AnotherMember]

=/

Bypassing the laws of my knowledge, 255 is the limit.

[Hyper]

Try clearing your temp files & cookies.

That would mean its a browser issue which it isn't, if it isn't going through cmd telnet.

But just in case I did and a shocking suprise.. No effect x.x

[AnotherMember]

Try a different browser...............................................................

[Hyper]

Try a different browser...............................................................

Browser has nothing to do with run cmd..

telnet xxxxxxxxx

[AnotherMember]

Your connecting to your router via CMD... Not to sound like a fuck but you constantly referred to the website and auth. as if it was the webpage of the router.. If you want to connect to it so bad why not do it the easy way and use a browser rather go through telnet. GUI > CLI in my opinion; unless of ofcourse you have no choice but to go through CLI which sounds stupid.

[JunkBondTrader]

Depending on what router it is there should probably be a reset button on it somewhere. It'll be tiny, one of those things you need to poke a pencil through. Give that a shot, see if it works.

Hope this helps.

[AnotherMember]

Actually to be fair, if you're trying via CMD give administration acts a go and if your CMD is fucked, try using the CMD thats located in the Windows folder. To be perfectly honest I would still just user a browser, its so much easier.

[Hyper]

Actually to be fair, if you're trying via CMD give administration acts a go and if your CMD is fucked, try using the CMD thats located in the Windows folder. To be perfectly honest I would still just user a browser, its so much easier.

To be fair I forgot to mention the most simple and useless things

Such as it can't be the browser and I wouldn't say that unless I've tried it and the cmd telnet works just the same as the browser except without the problems of one

And also I did factory recall it and its the same

And IDK if I mentioned this in the OP but I actually got 2 routers from a technician I know with the latest firmware and we tried with his laptop, both work but neither work on my computer..

[Hyper]

So does anybody have any ideas to cure this ''anomaly'' ???

Because I don't every logical, reasonable step has been taken and its 101% clear its not the router but the computer