New router dillema

extrememachine · 10 Dec 2013 at 12:29

So received the n66u not too long ago, updated to merlin firmware then updated ddwrt firmware from dd-wrt.com itself.
Now I am unable to login to the router 192.168.1.1. I don't think I have bricked the router.
any ideas?

schnoodles · 10 Dec 2013 at 12:45

What happens when you try to browse to the admin interface? And has your PC picked up an IP address via DHCP?

extrememachine · 10 Dec 2013 at 12:49

the config page/admin page cannot be accessed anymore it says unable to connect"
I don't think the pc has picked a dhcp as I cant login to the router how can I correct this router if so.?

schnoodles · 10 Dec 2013 at 12:56

Assign your PC a static IP... say 192.168.1.2.... and see if you can ping the router or reach the log-in screen. Was the router IP always 192.168.1.1, or did you assign it that IP yourself? If the latter, your firmware update may have reverted it to its original IP.

extrememachine · 10 Dec 2013 at 13:01

well I went to ehernet adapter tcp/ip 4 changed my ip address to 192.168.1.2 subnet to 255.255.255.0 and ip gateway to 192.168.1.1 which it was before.
the dns cannot be set to autoimatic.

schnoodles · 10 Dec 2013 at 13:03

DNS doesn't matter at this stage. Can you ping the router address or reach the admin screen?

extrememachine · 10 Dec 2013 at 13:06

cannot both

schnoodles · 10 Dec 2013 at 13:09

Try "arp -a" (without quotes) from the command line, and see if your PC is showing the router in its arp table. I take it you've checked all the cabling?

Steveocee · 10 Dec 2013 at 13:09

Have you tried doing a hard reset on the router?

extrememachine · 10 Dec 2013 at 13:12

schnoodles said:
Try "arp -a" (without quotes) from the command line, and see if your PC is showing the router in its arp table. I take it you've checked all the cabling?

interface 169..
224.. static
224.. "
224.. "
239.. "
255.. "

unleashed · 10 Dec 2013 at 13:12

Have you changed the router subnet i.e. say 192.168.1.1 to say 192.168.0.1 unknowingly?

schnoodles · 10 Dec 2013 at 13:14

Looks like it's still picking up a default Windows IP and not the one you've assigned. Double-check the static IP that you entered in the NIC config.

extrememachine · 10 Dec 2013 at 13:14

subnet is 255. etc

unleashed · 10 Dec 2013 at 13:22

extrememachine said:
subnet is 255. etc

That's not the subnet. The subnet in example I gave is either 1 or 0 i.e. it's the second number in from the end xxx.xxx.say 0 or 1. x

schnoodles · 10 Dec 2013 at 13:24

Basically, did you make any changes to the IP settings on the router at any point before you flashed the firmware?

extrememachine · 10 Dec 2013 at 13:25

I enabled ssh and telnet

schnoodles · 10 Dec 2013 at 13:27

But did you change the router's IP address?

extrememachine · 10 Dec 2013 at 13:28

unleashed · 10 Dec 2013 at 13:35

What does ipconfig /all show

unleashed · 10 Dec 2013 at 13:36

Do you have any third party bloatware handling network connectivity?