NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WN2000RPTv2 Connecting To Wireless Network But No Internet
I recently purchased a WN2000RPTv2 to extend the wireless in my house. I've ran through the setup multiple times with multiple browsers (IE, Firefox, and Safari). Each time it properly detects my home...
I generally don't like to broadcast my SSID, and for all previous experiences, that has worked just fine. My family and friends has been informed about my (hidden) SSID and passphrase, and everyone has been able to connect to my main WNDR3700-router.
Yesterday I burned some good hours trying to get my WN2000RPTv2 up and running. WPS was of course tried, but didn't work.
The first error I saw, was the absolute requirement of having an plain vanilla IP range structure on my net. I happend to have 192.168.100.x and shame on me, that won't work! So after rearranging my IP-structure to 192.168.1.x I could get the WN2000RPTv2 to attach to my network. However, it wouldn't connect to the internet! Not until I defined the static IP adress, gateway and primary DNS.
Today everything was down on the WN2000RPTv2! The only thing I did as the last operation yesterday evening, was to turn off the SSID broadcasting on my main router. After re-installing everything today on the WN2000RPTv2, I still couldn't get it work. Then it came to me - perhaps the WN2000RPTv2 needs to see the main SSID?!? I haven't seen anything like "Connect even if the network is not broadcasting it's name (SSID)" on the WN2000RPTv2, so perhaps it can't connect to a hidden SSID?!?! Turning on the broadcast of my SSID on WNDR3700, and voilá - The WN2000RPTv2 got connection instantly!
Summary
1. Ensure your IP subnet structure is based on 192.168.1.x
2. Ensure your main router's SSID is broadcasting
I haven't tried, but I bet even WPS works now.
Hopefully this may save some time for some users!
PS! Not impressed with the software quality of the WN2000RPTv2. Isn't it pretty common that users hide their SSID? I certainly look like the "super-noob of my street" with both my main SSID and SSID+Ext visible! And why bother with having the fields accepting IP adresses accept anything but the last digit? Don't even expose the options to the user if he/she can't use them anyway! Finally, why not expose the hidden pages like www.mywifiext.net/cgi-bin/hidden_dhcpd.html in the menu so everybody doesn't have to be a configuration-god to use them?
Yesterday I burned some good hours trying to get my WN2000RPTv2 up and running. WPS was of course tried, but didn't work.
The first error I saw, was the absolute requirement of having an plain vanilla IP range structure on my net. I happend to have 192.168.100.x and shame on me, that won't work! So after rearranging my IP-structure to 192.168.1.x I could get the WN2000RPTv2 to attach to my network. However, it wouldn't connect to the internet! Not until I defined the static IP adress, gateway and primary DNS.
Today everything was down on the WN2000RPTv2! The only thing I did as the last operation yesterday evening, was to turn off the SSID broadcasting on my main router. After re-installing everything today on the WN2000RPTv2, I still couldn't get it work. Then it came to me - perhaps the WN2000RPTv2 needs to see the main SSID?!? I haven't seen anything like "Connect even if the network is not broadcasting it's name (SSID)" on the WN2000RPTv2, so perhaps it can't connect to a hidden SSID?!?! Turning on the broadcast of my SSID on WNDR3700, and voilá - The WN2000RPTv2 got connection instantly!
Summary
1. Ensure your IP subnet structure is based on 192.168.1.x
2. Ensure your main router's SSID is broadcasting
I haven't tried, but I bet even WPS works now.
Hopefully this may save some time for some users!
PS! Not impressed with the software quality of the WN2000RPTv2. Isn't it pretty common that users hide their SSID? I certainly look like the "super-noob of my street" with both my main SSID and SSID+Ext visible! And why bother with having the fields accepting IP adresses accept anything but the last digit? Don't even expose the options to the user if he/she can't use them anyway! Finally, why not expose the hidden pages like www.mywifiext.net/cgi-bin/hidden_dhcpd.html in the menu so everybody doesn't have to be a configuration-god to use them?