ASUS RT-AC68R Refurb router issues!!

[Mwwilliams]

This thing keeps losing wireless completely. I have had to hard reset this multiple times to even get back into a firmware recovery mode. I believe it will be going back to NewEgg if I can get them to take it back or replace it. Is that my best option?

 

[KGB7]

Which firmwares have you tried?
Full reset after firmware flashes.

 

[Mwwilliams]

Which firmwares have you tried?
Full reset after firmware flashes.

I have used the latest to now using 376_44_0. After all working at 11:00 it can not even be discovered right now. I am grabbing an IP from my DSL modem but I am connected by straight cable to the AC68. It's like it's just a pass through switch at the moment. I have looked in the ASUS manual for a "full reset" instructions and see none. Do you mean a reboot? And how do you do that if you can't get to the GUI? Just power it off?

 

[Mwwilliams]

Okay, so now I held down the reset button for 5 seconds and my setup for both the 2Ghz and 5Ghz wireless went away and came up with the ASUS and ASUS_5G setup. I had powered off my PC that is connected by cable to the router and still gets no IP from the AC68 but gets an IP from my DSL Modem. Discovery utility does not find modem and neither does the Setup Wizard. I connect via wireless with my iPhone and it gives me a login prompt for the router setup. Connect with my Dell Laptop and it prompts for an 8 digit pin from router label that doesn't exist. This is crazy. I work in IT and this router has challenged me. Never had issues setting up a router before so this is crazy.

 

[Mwwilliams]

Ongoing saga for which no one wants to reply to. Got ASUS tech support chat online and went through what she said to do which returned the modem back to default. Powered on PC and now it sees router because it finally got an IP from the router not the DSL. Wireless was generic ASUS and ASUS_5G and it worked until I renamed it and put passwords on and for now it is working. Should I push it and set channels for the wireless. Is the scan supposed to pick up the wireless from the router because it doesn't. Isn't that a little strange?

 

[KGB7]

There is a lot of info on the forums that have been discussed many times.over.

Install 374.41 firmware. Wait 5 min for firmware to install and for.router to boot up.
Reset router by holding reset button for 15 sec, or until you see power light rapidly blinking.
Configure router settings.


If,.you still have issues, then return router for a new one.

 

[Mwwilliams]

Just curious, why recommend that particular firmware? I am currently using 3.0.0.4.374.42_2.

Also, when held down for 15 seconds that wipes all my settings and I have to re-enter, correct?

Does that have to be done on every single firmware update?

 

[KGB7]

Just curious, why recommend that particular firmware? I am currently using 3.0.0.4.374.42_2.

Also, when held down for 15 seconds that wipes all my settings and I have to re-enter, correct?

Does that have to be done on every single firmware update?

In many cases like mine, some firmwares work better then others in different environment and situations, because we dont live in a perfect world where everything works with zero issues.

Yes, all settings have to be manually re-entered after reset. I highly recommend that you use manual settings vs letting router using Auto settings.

Its highly recommended that you reset after each firmware flash.

 

[Mwwilliams]

If I have a PC connected to this router, and reboot it after a day and half or so, then it grabs an IP from the Modem. I have to power the router off and back on and reboot about the PC three time before it will grab an IP from the router. Should I turn off DHCP on the modem, and hard set an IP for the router?

 

[RMerlin]

If I have a PC connected to this router, and reboot it after a day and half or so, then it grabs an IP from the Modem. I have to power the router off and back on and reboot about the PC three time before it will grab an IP from the router. Should I turn off DHCP on the modem, and hard set an IP for the router?

Make sure you didn't disable the firewall and NAT option on the router, and that the router and modem don't have a local IP within the same subnet. DHCP requests shouldn't reach your modem unless you are somehow bridging the WAN and LAN sides of your router.

 

[Mwwilliams]

Make sure you didn't disable the firewall and NAT option on the router, and that the router and modem don't have a local IP within the same subnet. DHCP requests shouldn't reach your modem unless you are somehow bridging the WAN and LAN sides of your router.

Are these disabled by default? Because what is set up is generic as possible to just get this to work for even a week. The router has 192.168.1.1, which is default. The modem has 192.168.0.1 which is also default.

I come back today from work and my PC has grabbed a 192.168.0.** address again and was not even rebooted today, it was rebooted last night at 3:55 PM. This is just extremely frustrating. I also went to the firmware version recommended on Sunday and reset all this back up at that time.

 

[RMerlin]

Are these disabled by default? Because what is set up is generic as possible to just get this to work for even a week. The router has 192.168.1.1, which is default. The modem has 192.168.0.1 which is also default.

I come back today from work and my PC has grabbed a 192.168.0.** address again and was not even rebooted today, it was rebooted last night at 3:55 PM. This is just extremely frustrating. I also went to the firmware version recommended on Sunday and reset all this back up at that time.

No, they are both enabled by default.

If you get a DHCP lease in the 192.168.0.0 subnet, then something on your network is doing it. I suggest double checking every device on your network. Computers with Internet sharing services, that kind of stuff. Also make sure your modem is definitely plugged in the WAN port, not one of the LAN ports. I had a customer once who kept getting those weird DNS assigned to them. Turns out they had added an access point to their network without notifying me, and said AP wasn't half configured, so it was still assigning DHCP leases to the LAN, sometime randomly beating the real router into providing leases to clients.

 

[Mwwilliams]

I checked my connection and it's in the WAN port. I changed out my cable for the heck of it. I have no Internet sharing services enabled. I do have a Buffalo router set up as an AP upstairs in a bedroom. DHCP is off on that. I can see the clients on my modem and the IP's assigned. I don't see any setting that would be a "bridge" in the LAN or WAN sections.

I can send you a link to my syslog if you like?

 

[RMerlin]

I checked my connection and it's in the WAN port. I changed out my cable for the heck of it. I have no Internet sharing services enabled. I do have a Buffalo router set up as an AP upstairs in a bedroom. DHCP is off on that. I can see the clients on my modem and the IP's assigned. I don't see any setting that would be a "bridge" in the LAN or WAN sections.

I can send you a link to my syslog if you like?

A syslog won't help. The issue isn't the router, it's something else on the LAN providing DHCP leases.