Cannot get N66U to detect internet connection.

[Aomber]

Hi guys, new to the forums.

I'm not sure if I'm doing something really stupid or what, but I cannot get this router to work for the life of me. Got it yesterday afternoon and every time I run through the quick setup, when it gets to searching for my connection, it fails every single time.

I updated the firmware and I ran a 30/30/30. It's on the latest one (.178). I even tried merlin's firmware and that didn't work either. I can't seem to find any solution online about this. I know it's a problem for the stock firmware from my research, but I'm definitely not running that.

Anyone have any ideas? Starting to think my unit was defective out of the box if no firmware has worked for it thus far.

 

[RMerlin]

You will need to provide more information on what type of Internet connection you have, otherwise it's hard to tell you what to look for.

As a shot in the dark, I'd say try turning your modem off for about 5-10 mins, then plug it to the router, and turn the modem back on. Give it a minute or two, then try to access the router's Quick Internet Setup. This is required for some cablemodems.

 

[Aomber]

You will need to provide more information on what type of Internet connection you have, otherwise it's hard to tell you what to look for.

As a shot in the dark, I'd say try turning your modem off for about 5-10 mins, then plug it to the router, and turn the modem back on. Give it a minute or two, then try to access the router's Quick Internet Setup. This is required for some cablemodems.

I'm using Comcast as my ISP. I know the most recent FW update addressed a specific issue for Comcast users, can't remember what though.

Anyway I'll give that a shot first and post results. Thanks

 

[RMerlin]

I'm using Comcast as my ISP. I know the most recent FW update addressed a specific issue for Comcast users, can't remember what though.

Anyway I'll give that a shot first and post results. Thanks

The Comcast-related fix was only for people using IPv6 - it doesn't apply to regular users.

Since you have cable, then your problem was probably what I indicated - you need to either release your IP, or keep the modem turned off for a while to force it to fully reset. After that you should be ok.

 

[Aomber]

Just went and left my modem off for ten minutes. Turned it back on, turned the router back on, did the quick setup - still nothing.

IP release and renew didn't work either.

=\

 

[NeutralGold]

I use Comcast as well and I always have to reset the modem if I change firmware versions or type. In my experience, since you're using asus's firmware is to start quick setup. Once you get to the "Wan" part of the setup, turn off the cable modem for 5 seconds and turn it back on. Wait 30 seconds at the least while the modem boots up. Then continue setting up "Wan". Comcast modem always gives the router default ip of 192.168.100.1 and then updates to your internet ip momentarily.

 

[NeutralGold]

Just went and left my modem off for ten minutes. Turned it back on, turned the router back on, did the quick setup - still nothing.

IP release and renew didn't work either.

=\

Also note for future cases with comcast, make sure the modem gets reset AFTER the router. Resetting the modem first will result in no connection.

Hope this helps.

 

[Aomber]

I use Comcast as well and I always have to reset the modem if I change firmware versions or type. In my experience, since you're using asus's firmware is to start quick setup. Once you get to the "Wan" part of the setup, turn off the cable modem for 5 seconds and turn it back on. Wait 30 seconds at the least while the modem boots up. Then continue setting up "Wan". Comcast modem always gives the router default ip of 192.168.100.1 and then updates to your internet ip momentarily.

Also note for future cases with comcast, make sure the modem gets reset AFTER the router. Resetting the modem first will result in no connection.

Hope this helps.

Just tried your suggestion - still not picking up anything.

Thanks guys but I think I'm just gonna return this and get a completely different router, I've been trying to fix this all afternoon/evening yesterday and all day today. At $170 I really expect a router to just work out of the box when every other router I've installed has done so. I'm sure it's a great router but it's just giving me too much of a headache to be worth it.

 

[AnthonyArmato]

No issues with with mine on Comcast. You may need to check the user guide, as this router may be a bit more "advanced" then others you've used.

Make sure you have the modem plugged into the correct port on the router. Turn the modem on, let it connect completely THEN turn on the router. Set up the router using a direct connection via an Ethernet cord to your computer.

 

[RMerlin]

I use Comcast as well and I always have to reset the modem if I change firmware versions or type.

BTW, in build 178 Asus added some code so if you turn WAN off from the first page, it will actually release its DHCP lease rather than just close the wan nterface. That means you might be able to more easily upgrade firmwares by first disabling WAN, upgrading, then re-enabling - will save you from having to keep the modem off for a given period of time to let your lease expire.

 

[Enigma69]

I had a similar issue when trying connect my RT-N66U to a Vigor 120 using PPPoE pass through, I managed to figure out that the stock & Merlins firmware needed to see both a username and password for the modem connection to complete - the password isn't something which is required for UK BT ISP, in order to get around the problem the password field needed to be populated - Shibby's FW wasn't as strict on having to have a password passed for the connection.

Anyhow this may or may not help with the issue you are seeing as I don't know the requirements for the ComCast connection but may be worthwhile checking before you return the router.

 

[NeutralGold]

BTW, in build 178 Asus added some code so if you turn WAN off from the first page, it will actually release its DHCP lease rather than just close the wan nterface. That means you might be able to more easily upgrade firmwares by first disabling WAN, upgrading, then re-enabling - will save you from having to keep the modem off for a given period of time to let your lease expire.

Nice to know, thanks for mentioning. I'll be sure to to keep that in mind for when aicloud shows up and I move back to asus's firmware.

 

[NeutralGold]

Just tried your suggestion - still not picking up anything.

Thanks guys but I think I'm just gonna return this and get a completely different router, I've been trying to fix this all afternoon/evening yesterday and all day today. At $170 I really expect a router to just work out of the box when every other router I've installed has done so. I'm sure it's a great router but it's just giving me too much of a headache to be worth it.

Well sorry you're having such a hard time. You could possibly have a faulty router and that stinks. If that is at all the case, I would suggest replacing it with the same model.

Problems happen all the time with good hardware as well as bad. I think if it is some kind of hardware malfunction, once you get a good solid router you won't be disappointed.

Good luck with what ever choice you make.

 

[FrustratedGuy]

I have the exact same problem here in Germany using a Arcor Vodafone modem box. No matter what I have tried, it does not ever detect a WAN connection. I returned the N66U and picked up the N65U. And guess what? Same problem. I've spoken to Vodafone in Germany and all that is required is username and password and PPPoe. Nothing more. But with these Asus routers nothing works. There's obliviously a larger compatibility issue with these routers. Looks like I will have to return this 65U back to Amazon.

Are there any other good FTP capable Wireless routers out there?

 

[SoCalReviews]

power cycling the modem

I have both cable and dsl. Only sometimes do I have to power cycle my cable modem for it to reconnect and give a WAN IP to the router. I usually power cycle my cable modem first (sometimes leaving the modem unplugged for a minute or two) and then I power cycle the router afterwards. For my dsl modem the sequence is reversed... When my router was new or if I power that router on after being turned off and disconnected for a long time or if I flash the router firmware I always have to power cycle the dsl modem afterwards with the router left on before the router obtains a WAN IP from the modem. This is true for both the Asus N66U and my Netgear 3700v2.

I don't know if this was brought up yet...because it's the most common and simple "the sky is blue" solution for the the age old problem of a a router not seeming to work with a modem...but for those experiencing problems who have already tried the two different power cycling sequences...Have you tried setting up the router...and then changed the router's starting LAN IP address (under the Asus router settings LAN > LAN IP) from the default of 192.168.1.1 to a different IP such as 192.168.2.1 ? A reminder to less experienced users...Remember that after you do this you will need to type in that new LAN IP (if it is 192.168.2.1) instead of the default of 192.168.1.1 to access the router's administration pages from your browser.

 

[FrustratedGuy]

I have both cable and dsl. Only sometimes do I have to power cycle my cable modem for it to reconnect and give a WAN IP to the router. I usually power cycle my cable modem first (sometimes leaving the modem unplugged for a minute or two) and then I power cycle the router afterwards. For my dsl modem the sequence is reversed... When my router was new or if I power that router on after being turned off and disconnected for a long time or if I flash the router firmware I always have to power cycle the dsl modem afterwards with the router left on before the router obtains a WAN IP from the modem. This is true for both the Asus N66U and my Netgear 3700v2.

I don't know if this was brought up yet...because it's the most common and simple "the sky is blue" solution for the the age old problem of a a router not seeming to work with a modem...but for those experiencing problems who have already tried the two different power cycling sequences...Have you tried setting up the router...and then changed the router's starting LAN IP address (under the Asus router settings LAN > LAN IP) from the default of 192.168.1.1 to a different IP such as 192.168.2.1 ? A reminder to less experienced users...Remember that after you do this you will need to type in that new LAN IP (if it is 192.168.2.1) instead of the default of 192.168.1.1 to access the router's administration pages from your browser.

Thank you very much for the effort and reply. I tried everything you mentioned, carefully, and still my Asus 65U does not get a WAN IP address.

I work in IT so I already knew about changing the default Gateway and setting the range for DHCP. I just don't get it. There are zero IP conflicts, I am using the ISP username and password with PPPoE and no luck what so ever. Never had so much headache with a router before.

 

[RMerlin]

Thank you very much for the effort and reply. I tried everything you mentioned, carefully, and still my Asus 65U does not get a WAN IP address.

I work in IT so I already knew about changing the default Gateway and setting the range for DHCP. I just don't get it. There are zero IP conflicts, I am using the ISP username and password with PPPoE and no luck what so ever. Never had so much headache with a router before.

Check in syslog to see if rp-pppoe logs any error related to the PPPoE authentication. Some ISPs might have weird setups that might require a bit of tweaking. And some ISPs expect the username to contain the realm (username@realm) - your modem might be adding it automatically for you if it's ISP-provided, but you'd need to add it manually on the router. And make sure you disable the PPPoE authentication in the modem, to avoid double PPPoE sessions.

Try a Google search for "rp-pppoe" and your ISP to see if there is any user feedback on how to get the two to work together.

I only used the RT-N66U for a short period of time with my DSL account as I switched to cable since then, and it was working fine for me (Bell Canada's DSL).

 

[SoCalReviews]

Thank you very much for the effort and reply. I tried everything you mentioned, carefully, and still my Asus 65U does not get a WAN IP address.

I work in IT so I already knew about changing the default Gateway and setting the range for DHCP. I just don't get it. There are zero IP conflicts, I am using the ISP username and password with PPPoE and no luck what so ever. Never had so much headache with a router before.

Having experience working in IT definitely gives you a big advantage at solving these kinds of problems. I don't claim to be an expert on these issues even though I have some past experience (back in the day) in the industry working in business sales and tech support for an ISP. This past year I noticed I was having some problems with reliability and latency. After some web research in my ISP forums I found a solution by going into the modem's settings and making some changes. If you were using your ISP provided modem then checking out it's settings would be where I would start. In the 65U settings there may be a change that could be made (as Merlin mentioned...maybe a change is need for the PPPoE login and password or related settings that are are required by the ISP) that will enable it to authenticate with your ISP so it can be offered a WAN IP address.

While this seems to be a problem you are having with the Asus equipment it still might be helpful to find answers to this problem by contacting your ISP's higher level support to help guide you with this issue since they might have other customers who are experiencing similar problems. Keep the forum updated on your progress. I hope you are able to find a solution.

 

[katabatik]

I'm having the exact same problem as the original poster (I don't mean to hijack the thread...). RT-N66U (latest official firmware) + Draytek Vigor120 latest official firmware). I have an ADSL2+ line that uses PPPoE.

I've tried so many things and nothing seems to work. Here is what I've tried so far.
- With and without PPPoE pass through.
- Disabling the Vigor's firewall
- Leaving the Vigor's credentials (username and password) blank and letting the ASUS do the authentication.
- Leaving the ASUS credentials blank, no PPPoE pass through and leaving the authentication to the Vigor.

Any ideas? Enigma69 you have a similar setup, don't you? Can you share your config with me or give me some suggestions?

Thanks.

 

[Enigma69]

Hi Katabatik,
Heres the sequence I followed in order to get the RT-N66U talking through the Vigor120:

- Vigor120 Settings

Internet Access >> PPPoE/PPPoA set to Enabled and that PPPoE pass-through is ticked
Internet Access >> MPoA set to Disabled
​

- RT-N66U

Cancel the Quick Internet Setup
Next goto Advanced Settings >> WAN and change the following:
WAN Type: PPPoE
Enable WAN: Yes
Enable NAT: Yes
Get WAN IP Automatically: Yes
Username: {ISP Username}
Password: {ISP Password} If your ISP doesn't provide one use the username above
Enable VPN + DHCP Connection: No
​

Once you apply the settings give it a minute or two and check under General >> Network Map >> Internet Status to verify you have a connection & WAN IP.

Assuming this worked you'll need to manually configure the rest of your options manually (Wireless, LAN etc.)

Hope the above makes sense.

Thanks,
Enigma69