Difficulty setting up Asus AC66U with Pace 5031NV

G

gmreplay

Weaksauce
Joined
Dec 27, 2010
Messages
92
I have an AT&T Uverse and I have had one heck of a time setting up my new Asus AC66U router. I followed the video below, and I've transcribed the steps I took. Then I list off some of the strange errors I've encountered. Any advice appreciated.

These steps may be of use to anyone who is struggling with setting up their Pace 5031NV.

Video: https://www.youtube.com/watch?v=LZy1C5qHxKc
Steps:
1. Connect the AT&T U-verse Pace 5031NV (old router) to my PC by ethernet
2. Reset old router to factory settings
3. Visit 192.168.1.254. Under settings -> event notifications -> click on "enable detection of router-behind-router conditions
4. With the old router off, I hooked up the ethernet cable from my PC to slot 1 on the new router, and hooked up the ethernet cable from slot 1 on the old router to the internet port on the new router
5. Turned new router on
6. Rebooted my PC. Per the video, doing this should assign a new IP address to the new router, and I should be prompted by Windows that "Additional login information may be required." This did not happen.
7. Went back into the settings menu for the old router. Selected settings -> firewall -> Applications, Pinholes, and DMZ. Selected the new router (listed as something like UnknownAC22BEC9582) and chose the Allow All Applications (DMZplus mode) option. Hit save.
8. At this point, the internet began working on my ethernet-wired PC and my wireless devices.
9. I shut off the wireless functionality of the old router. In the Advanced Configuration menu of the old router, I also disabled stealth mode, block ping, unselected NetBios on both inbound and outbound, and unselected everything under "attack detection."
10. On the new router, I set up my network name, security code, etc.

Now here's where things get weird. These are the issues I'm wrangling with now:

1. After a few minutes I decided to change the name of my network on the new router, and rebooted it to ensure that the changes took effect. The wired and wireless connections proceeded to fail, and never came back. Nothing seemed to fix it.

At some point I got an error reading "Error: The Connection Monitor has detected a third party router connected to the 5031NV-030." I selected the "Reroute" button, which should have fixed the issue. Instead, I was told that "We have detected a 3rd Party Router connected to this gateway with a static address. Due to this, we are unable to move the device to DMZPlus mode."

Strangely, I never changed the new router's settings in this regard. Throughout the entire process the WAN connection type was set to "Automatic IP." It's currently set to the same, and is currently functional. I'm concerned if I change any other settings on the new router I'm going to encounter the same error and have to start all over again.


2. I'm getting really inconsistent behavior from the 5GHz network. Earlier today I was getting 90MBps local transfer speed (measured by the "Wifi-Sweetspots" app on iOS), but at other points I was losing access entirely, and now I'm getting an average of 18MBps. Nothing indicates that the 5GHz network is having any trouble, so I can't imagine why my iPhone would be defaulting to the 2.4GHz network. I'm in a 800sqft apartment that is in a square shape with drywall walls, so it's not like 5GHz should have trouble penetrating the walls.

3. During the time when the internet was down, I was sometimes able to perform google searches on my ethernet-connected PC, but could not click any of the links, and could not navigate to other pages. Then at other times I would have a burst of access, lasting perhaps 5 seconds, followed by no access whatsoever. If I was having trouble with the DMZ, DHCP, or some other function of the old router, I can't see why I would get some access at all.

4. Given the steps I took above, have I done all necessary to properly set up the network?
 
Ethernet to lan port on ASUS, turn off dhcp in Asus, make sure IP address is outside dhcp range of 5031, it's usually 192.168.1.1.

Done

This turns the Asus into a wap and routing done on 5031, save yourself the headache of configuring the uverse gateways are crap
 
Oh that's an interesting method. How do I ensure that my Asus's IP addy is outside the DCHP range of the 5031? By default the Asus seem set to 192.168.2.1. Is that sufficient?
 
gmreplay said:
Oh that's an interesting method. How do I ensure that my Asus's IP addy is outside the DCHP range of the 5031? By default the Asus seem set to 192.168.2.1. Is that sufficient?
Click to expand...

There are a couple of ways you can get that router to work. If all you really trying to do is use the better wireless, then just using it as a WAP will be the best option. In this case we are NOT using the WAN (Internet) port on the new router. What you will want to do is the following

1) Reset new router to factory defaults and disconnect from network
2) Setup the Local IP address of the new router to be within the range of the ATT Modem (i.e. 192.168.1.1 - 192.168.1.253) - note you will lose connection to the router - if you can't get reconnected simply release/renew your IP address (or unplug/plugin the ethernet cable) to get a new IP address. 192.168.1.253 will probably work for now for the router address- see below
2a) You will want to login to the old router provided by ATT and see what the dhcp range is, and confirm if 192.168.1.253 is outside of the range once everything is hooked back up
3) Disable DHCP server entirely on the new router
4) Save changes on new router - plug an ethernet cable in from the back of the ATT router, into one of the 4 LAN ports of your new router.

That should do it there, now just finish configuring wireless and such.

Be aware that port forwarding and firewall rules will still exist/be managed through the ATT router. If you want this to be more than a wireless access point, let me know.
 
Last edited:
I'd prefer to use the full functionality of the AC66U rather than just using it as a WAP. The 5031NV is real hunk of junk so I'd like to bypass it to whatever extent possible. Thank you for your help!
 
Right, so that's the method I attempted, but because my 5031NV is different from the 2Wire they use in that thread, I wasn't able to implement all of the steps. For instance I wasn't able to set my 5031NV to get its IP from DHCP. It just apparently isn't an option on my router. Does my method effectively work around that issue?


I should also add that following my renaming of the network and subsequent failures to connect, I was totally incapable of accessing the 5031NV's settings menu at 192.168.1.254 for some reason. Not sure if this helps establish a diagnosis of what went wrong.
 
Last edited:
gmreplay said:
Right, so that's the method I attempted, but because my 5031NV is different from the 2Wire they use in that thread, I wasn't able to implement all of the steps. For instance I wasn't able to set my 5031NV to get its IP from DHCP. It just apparently isn't an option on my router. Does my method effectively work around that issue?


I should also add that following my renaming of the network and subsequent failures to connect, I was totally incapable of accessing the 5031NV's settings menu at 192.168.1.254 for some reason. Not sure if this helps establish a diagnosis of what went wrong.
Click to expand...

It is an option on your router, firewall, apps and pinholes, select your routers name, select dmz plus radio button at the bottom of the page, save, reboot your 5031nv, wait 3 min after you have sync and service, reboot the asus.

As long as you have the asus set up as a router (not in bridge mode) it will have a public Wan ip.
 
gmreplay said:
Right, so that's the method I attempted, but because my 5031NV is different from the 2Wire they use in that thread, I wasn't able to implement all of the steps. For instance I wasn't able to set my 5031NV to get its IP from DHCP. It just apparently isn't an option on my router. Does my method effectively work around that issue?


I should also add that following my renaming of the network and subsequent failures to connect, I was totally incapable of accessing the 5031NV's settings menu at 192.168.1.254 for some reason. Not sure if this helps establish a diagnosis of what went wrong.
Click to expand...

You're getting it a little backwards on how this dmz plus mode works. On each router you essentially have 2 interfaces, an inside and outside. The outside is the internet, inside is your network obviously. With the ATT Gateway your outside is already defined for you, you cannot change that. It is recommended you do not change the inside IP, you can, but its not usually worth it. With that in mind, what you are doing is plugging the "outside" of the Asus router into the inside of the ATT Gateway. Your computers will then be on the inside of the Asus clearly.

With that in mind, you need the outside of the Asus set to DHCP, to grab an IP Address automatically from the ATT Gateway. What this does is allow the ATT Gateway to recognize the device in the inside of the gateway. So leave the ATT Gateway in the defaults for now. reset the the Asus router to defaults, and leave/change the WAN/Internet/Outside IP to DHCP.. This allows the you to login to the ATT Gateway now, and select the Asus Router from the DMZ Plus mode selection (it will be either an IP address, or hostname for the selection).

If the Asus router is smart, it should change the inside IP address to something other than 192.168.1.X. If not you will have to manually change it to something other than 192.168.1.X (e.g. 192.168.2.1, or 192.168.100.1). There will be a couple more settings in the ATT GAteway that will have to be configured, I will see if I can find more info, but I think that should get you going/using the Asus for the time being.
 
You must log in or register to reply here.
Back
Top