I am attempting to install a WZR-HP-300NH. I have not problem finding it on my LAN, but it seems unable to connect to my ISP. I am attempting to connect to Comcast using a cable modem. The old router works fine when I plug it in, but when I attempt to set up the WZR-HP-300NH it tries a few times and then just stops saying it can't connect to the ISP.
What is my nxt option? Where do I go from here?
Torrid
Have you tried power cycling the modem? If you have I will post instructions on how to set it up manually.
Thanks for the quick response.
PCPiranha asks: "Have you tried power cycling the modem? If you have I will post instructions on how to set it up manually."
Yes, multiple times. I have followed the this process:
I have resent the router to default once. I was able to reinstall my old router without a problem.
Torrid
Same exact problem here. 1.72 firmware. Modem is supplied by Comcast.
I have twice gotten a successful ISP connection after multiple attempts, but when just about any change is made to the WZR-HP-300NH the connection is broken and at this time I am still unable to connect. Self detect is giving the following messsage DHCP server or PPPoE Server not found.
Also it seems that my wirelss computers cannot see any shared folders my wired ones. Have a old WHR-HP-G54, which still works great and was trouble free, cannot say the same about the 300NH so far. Very disappointed.
Thanks for your sharing your experience. I will consider it as I address my problems wiht the router.
t
Had the same issue with Comcast but figured it out. You need to go to the routers config page and under the Internet tab, select the option to use DHCP. Once you apply it, go back to the main setup page and select the check connection button. Once I did that it worked fine.
I think I got mine figured out. There appeared to be some corrupted PPPoE entry that populated after I flashed to the latest firmware. Once that was deleted I have been able to connect so far. I think that maybe it was attempting to connect via PPPoE first and timing out. Will reply back if I have any further issues.
However my internet connection seems to be flakey since I moced over to this 300NH, my old buffalo wireless router was rock solid forever, this one has dropped my internet connection several times so far impacting both wired and wireless.
I too have the same problem with 1.72, the router gets an IP address then immediately releases it?? DHCPC Log enries are below... This problem did not exist in 1.65.
Please help!
WZR-HP-G300NH - 1.72
Comcast - Toshiba pcx26000
2010/01/01 00:01:31 DHCPC terminating on signal 1
2010/01/01 00:01:30 DHCPC sending DHCP_RELEASE for 71.195.5.76 to 68.87.77.10
2010/01/01 00:01:28 DHCPC Detected DHCP Server
2010/01/01 00:01:18 DHCPC Info : LEASETIME(3600) , RENEWALTIME(1800) , REBINDTIME(3150)
2010/01/01 00:01:18 DHCPC Info : DHCPSNAME =
2010/01/01 00:01:18 DHCPC Info : DHCPSHADDR = 00:1B:D5:FF:10:E2
2010/01/01 00:01:18 DHCPC Info : DHCPCHADDR = 00:1D:73:B3:6E:6D
2010/01/01 00:01:18 DHCPC Info : DHCPSIADDR = 0.0.0.0
2010/01/01 00:01:18 DHCPC Info : DHCPGIADDR = 73.237.176.1
2010/01/01 00:01:18 DHCPC Info : DHCPSID = 68.87.77.10
2010/01/01 00:01:18 DHCPC Info : DNS[2] = 68.87.72.134
2010/01/01 00:01:17 DHCPC Info : DNS[1] = 68.87.77.134
2010/01/01 00:01:17 DHCPC Info : Domain Name = hsd1.mn.comcast.net.
2010/01/01 00:01:17 DHCPC Info : Default Gateway = 71.195.4.1
2010/01/01 00:01:17 DHCPC Info : Subnet Mask = 255.255.254.0
2010/01/01 00:01:17 DHCPC Info : IP Address = 71.195.5.76
I had this exact same problem after updating to 1.72. I tried the responses listed but nothing worked.I did find a workaround, however: (please note I have Comcast)
Disconnect your modem from your router and connect it to your computer
Wait until you can browse web pages, then press Windows Key + R (at the same time)
Type CMD and press enter
When the dialog box appears, type ipconfig /all
Right click inside the window and select Mark
Select all the text and right click, this will copy your IP settings
Open notepad and paste what you selected into the document, save it
Plug modem back into router and power on
Connect to the router and navigate to the web configuration interface
Click Internet/LAN and select Use This Address as your Method of Acquiring IP Address
In your notepad document, find the IPV4 address and enter it as the IP
Copy the Default Gateway, DNS servers and Physical Address into the Advanced Settings fields from your notepad document
Click Apply and let the router reboot. You should be able to navigate to web pages. If so, go back into the Internet/LAN settings and select Acquire an IP Address Automatically from a DHCP Server as your Method of Acquiring IP Address. This ensures that if you power cycle your modem it will still pick up an IP from your provider.
Hope this helps everybody
Try unplugging the WAN then detecting via interface. You should get an error stating that there is no cable attached. Plug in the WAN connection. Retry. Worked for me, until...
Glad to see I'm not the only one having this issue. Yet, maybe that's not a good thing, until a solution is found. :smileywink:
Exactly the same problem here. I had this problem with 1.65. Upgraded to 1.72, still have the same problem.
Unable to connect to ISP
Unhappy Customer
Thank-you for your detailed explaination. I am on firmware 1.65.I tried it, but still have a few specific questions:
You say: "Click Internet/LAN and select Use This Address as your Method of Acquiring IP Address"
... I did not see a check-box saying "Use this address..."
You say: "In your notepad document, find the IPV4 address and enter it as the IP"
... I do not know where to enter this IP address. It does not seem to be on the Internet/LAN page.
You say: "go back into the Internet/LAN settings and select Acquire an IP Address Automatically from a DHCP Server as your Method of Acquiring IP Address"
... This option does not appear on the Internet/LAN settings page...at least on my router.
Thanks again for your help. I hope if I can get these questionsaddressed I can get it manually configured and then move on to automatic confituration. Otherwise, it's back in the box and back to Amazon.
You need to set the switch on the back to "router" and refresh the page you will see the settings as described above.
The manual configuration, after putting the router switch on worked.
Thanks for all your help!
Slightly happier customer...
** curious on how many trees it took to produce the energy required for inconveniencing all those electrons on computers and network equipment **
Hmm. I had tried this and it didn't work any different. My router did work twice without switching this, so I'm suspicious of this switch being related at all.
It's very inconsistent. With near factory defaults, the unit would connect after multiple power cycles of both the cable modem and the router. Then the other night, after it got unplugged by mistake, I couldn't get it to connect at all, in fact the interface wouldn't display in any way until I hard reset it three more times.
Overall, this router is extremely unstable.
weymouthba wrote:I had this exact same problem after updating to 1.72. I tried the responses listed but nothing worked.I did find a workaround, however: (please note I have Comcast)
Disconnect your modem from your router and connect it to your computer
Wait until you can browse web pages, then press Windows Key + R (at the same time)
Type CMD and press enter
When the dialog box appears, type ipconfig /all
Right click inside the window and select Mark
Select all the text and right click, this will copy your IP settings
Open notepad and paste what you selected into the document, save it
Plug modem back into router and power on
Connect to the router and navigate to the web configuration interface
Click Internet/LAN and select Use This Address as your Method of Acquiring IP Address
In your notepad document, find the IPV4 address and enter it as the IP
Copy the Default Gateway, DNS servers and Physical Address into the Advanced Settings fields from your notepad document
Click Apply and let the router reboot. You should be able to navigate to web pages. If so, go back into the Internet/LAN settings and select Acquire an IP Address Automatically from a DHCP Server as your Method of Acquiring IP Address. This ensures that if you power cycle your modem it will still pick up an IP from your provider.
Hope this helps everybody
I could accept this as the solution, but there are a couple of details that are missing:
1) In order to see all the options mentioned, you have to move the physical switch on the top rear of the router to "Router." This allows you to follow the above directions.
2) You need to remember that because IP addresses are served dynamically by your ISP, you need to capture the TCP/IP information and enter it into the router fields without disconnecting from the ISP. Pretty basic, really, but I missed it.
Keeping these two things in mind I was able to manually configure my router...and have it dynamically grab the new address if the cable modem restarts or there is another problem. Glad I was able to get this to work as I already had the RMA information from Amazon.
Try powering down the cable modem for like 5 mins then power on again, plug in WZR-HP-G300NH after about 1 min, once the cable modem is bridged it just has to work, make sure WZR-HP-G300NH is in Router mode (switch on back at ON).
If connection to the ISP is MAC address dependant you may need to clone the WAN MAC of your old router?
Yeah so that worked.
"Copy the Default Gateway, DNS servers and Physical Address into the Advanced Settings fields from your notepad document
Click Apply and let the router reboot. You should be able to navigate to web pages. If so, go back into the Internet/LAN settings and select Acquire an IP Address Automatically from a DHCP Server as your Method of Acquiring IP Address. This ensures that if you power cycle your modem it will still pick up an IP from your provider."
I had same problem with my WZR-HP-300H, Firmware: DD-WRT v24SP2-EU-US (08/19/10) std. I had to statically enter all the info as stated in previous posts, and then clone my PC MAC address, which finally made DHCP connect and receive same WAN IP as statically assigned before. I am a Comcast high speed internet subscriber and have never had a problem with service before buying this wireless router. This issue needs to be addressed with a firmware update or other permanent fix! Has anyone else found any update to this problem or a script that fixes? Thanks.
I've found a fix to the compatibility problem between Charter and Tomato. To fix the issue, do the following steps:
1) Login to Tomato
2) Go to advanced
3) Go to DHCP / DNS
4) Under DHCPC Options, put the following:
--retries=2 --timeout=5 --tryagain=310
(Note: this causes the router to only try to get an address twice, timeout after 5 seconds, and wait 5 minutes between attempts. On Charter, you could lower the --tryagain to 3 minutes, if you wanted, but I've set it to 5 to be safe)
5) Click save
Note: This fix only has been validated in Tomato-usb 1.28. Stock tomato 1.25 does NOT have the "DHCPC Options" field.
Details:
The root cause of the problem is that Charter's DHCP server stops communicating with any DHCP client that attempts 5 communications in a 3 minute window. Once blacklisted, devices are not able to communicate with the DHCP server until there has been 3 minutes of inactivity. However, Tomato's default behavior is to try 5 communications per attempt, and to try more frequently than every 3 minutes to connect.
When making the connection, some cable modems appear to establish the upstream connection before the downstream is fully established. This allows packets to travel FROM the router but not back TO the router. When the Tomato router attempts to get its IP address, the packets TO the DHCP server are received, but the responses are not. This causes Tomato to retry over and over, getting itself blacklisted. Once blacklisted, Tomato attempts often enough to stay blacklisted.
When power is applied simultaneously (power comes back) to the cablemodem and router, certain cable modems startup at the same time as the Tomato router. This means that Tomato has a timing condition where (after a power outage), it gets itself blacklisted and will not obtain internet access without manual intervention. However, other cable modem models appear to startup much more quickly (or establish upload/download at the same time), and are not affected by the issue.
From a Charter Rep:
The amount of time that it takes to reestablish a connection makes me think we could have a DHCP denial issue. This is where something from the customer's end is requesting an IP address from our DHCP servers more than 5 times in 3 minutes. The culprit of these issues is a router about 95% of the time. When this happens, your service is temporarily blocked. To fix it, the server has to be clear of all requests for 3 minutes. We usually accomplish this by unplugging modem and router for that time.
Fix:
The fix is to reconfigure udhcpc to try fewer times and to wait longer between attempts. This prevents the router from being blacklisted. This is achieved by passing "--retries=2 --timeout=5 --tryagain=310" to udhcpc.
Workaround:
The issue can be worked around by unplugging the Tomato router for 5 minutes, and then plugging it back in. Alternatively, you can power on the cable modem fully before starting the router.
Reproduced this issue on a WRT54GL with the following cablemodems:
Motorola SB 5100
Ambit U10C018.80
Issue did not exist with a WRT54GL the following cablemodems:
Cisco DPC3010