What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-66u No Internet Connection

Stormexe

New Around Here
Hello,

I am having a bit of difficulty setting up my new Asus RT-66u. I am not overly knowledgeable with technical devices, but I purchased this router (at the strong suggestion of a friend) to replace an old one since I have just moved and changed ISPs.

Anyways, after setting up the router, I found that I have no internet. My ISP is Comcast, and the Modem (Zoom 5341J) seems to work just fine as I have no issues and good speed when I directly connect to the modem without the router. However, as soon as the router is introduced into the equation I have no internet, as I can't browse or ping.

So far, I have tried every possible combination of power-cycling that I can imagine. I've reset the modem, then router, then computer and vice versa, and everything in between. I've unplugged all cables, and let the devices set from anywhere from 30 seconds to 30 minutes each, and still no go. I also tried cloning the MAC address of the PC for the router, which didn't result in any changes.

I can access the router just fine, and all LEDs light up, and it broadcasts a network that devices can join (but have no internet). Additionally, the router is showing a WAN IP. I have the factory Asus Firmware (3.0.0.5.354) and it shows the internet status as "Connected" it even shows a very small amount of internet traffic, but again I can't browse or ping anything.

I called Comcast, who ran me through the basic power cycling process, then told me I have to contact Asus. I contacted Asus who told me to power cycle.

Since power cycling and MAC cloning seem to be the suggestions I come to again and again, does anyone have any further suggestions?
 
When power cycling the modem, make sure to leave it turned off for 10 minutes, to ensure the connexion fully gets reset.

Also make sure the cable between the modem and the router is either Cat 5e or Cat6.
 
RMerlin,

Thank you for your response.

I had let the modem set for 10 minutes+ in the past, but I went ahead and tried it again (removing all the cables) just to see. Sadly it did not make a difference.

I had been using an older Cat6 cable, so I switched that out for a brand new Cat6 cable, which didn't fix the problem. On the off chance that both the old and new cables were bad, I tried a Cat5e cable that I know is working, and I still had no internet.

On each cable, and after each power cycle, I keep coming to the same point. Where the router page is showing a WAN connection and IP, but I just can't browse.

Do you have any additional suggestions?
 
So you do get a lease. Is the WAN IP really a public one?

If you try a traceroute on an external IP (for example, tracert 8.8.8.8), is it able to go out? If it is, then your problem is related to name resolution. Check your DNS settings.
 
Hi,
Is your ISP IP dynamic or fixed? Tried to ping that IP address? Can you ping like www.yahoo.com and what is the result? Did you try command ipconfig /all or
ipconfig /renew? What is the result? Tried with default setting of the router?
Log into the router and what the first page show? Anything on syslog? Tried rebooting
the router with everything connected(just click the reboot button on the top)?
 
This may be unrelated and just a fluke.

But about a little over a week ago I had an issue where I couldn't connect to the internet even though my router showed connected. It happened after a power outage and I couldn't see anything wrong other than maybe corrupted nvram settings. I restored a settings file from the previous firmware as a quick and dirty see if it works type deal.

Everything seemed to be okay after that. How ever, it happened again a few days later when rebooting the router. This is the only issue I've ever had by not clearing nvram on a new update.

You say you're on the latest firmware. Did you clear previous settings after the update? The way your router is acting is very close to the way mine was. I suggest resetting things to default and seeing if that helps.
 
do you have the vpn-server activated? try to deactivate

if i activate the vpn-server, after a few time i had the same problem. :/
 
Is your modem set to bridge mode?

Bridge mode provides a public IP to the router. This public IP can be anything in a large range and is assigned to your ISP.

If it's not in bridge mode, the modem will be providing a private IP to your router. Private IPs are listed here. (Something like 192.168.1.1 is a private IP). If your router shows your WAN IP as something in the range of private IPs, then your modem is operating as a router and your network won't work properly with another router.

Your ISP can set your modem to bridge mode.
 
Thank you for your responses everyone, I do appreciate them.

I've had an unrelated circumstance come up that requires me to be away from the home for a couple of days, I will return to troubleshooting once I return.

I just didn't want you to think that I had asked a question then ran, I appreciate all your responses and will update accordingly once I have a chance to look into each of them.
 
Alright,

Just as an update to this. After returning home I decided to try my old tried and true Linksys WRT160n v2, just to make sure it wasn't a problematic rt-n66u. I had the exact same issue with the Linksys, which I knew worked because it had been working for five years. At this point I called Comcast, and after some continued prodding and multiple transfers, I finally found out that the issue was on their end (go figure). They reset several things, and suddenly everything worked. I am not exactly sure what they did, but apparently my modem wasn't authenticated properly. Why I could browse with the modem, but not with the router, I have no idea. Anyways, its been working (with router) for about 12 hours now. So I'm hoping that it was limited to an authentication issue.

Thank you everyone for your responses, and I will let you know if anything changes.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top