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...
The WN2000RPTv2 with firmware V1.1.0.12 will connect to an existing WiFi network and can give itself an IP address via DHCP, but won't pass on DHCP requests from client devices (either wireless or wired) that attempt to connect via the WN2000RPTv2.
I manually configured the IPV4 address for the WN2000RPTv2 having identified which IP address was being handed out by DHCP server and then logging into the WN2000RPTv2 from a locally connected PC using one of the four 10/100 ports and a manually allocated IPV4 address.
Even with a non-DHCP address for the WN2000RPTv2 any client devices connecting via the WN2000RPTv2 still have the same problem (fail to get a DHCP address from the DHCP server), so need to have their IPv4 addresses etc. configured manually.
This makes the WN2000RPTv2 difficult to use for people without good network knowledge.
What should happen is that a client device should have its MAC address forwarded as part of the DHCP request packet to the primary wireless access point, which should in turn pass the DHCP request along to the DHCP server, which should then pass back the necessary set of information (IP address, gateway address, etc.) . The WN2000RPTv2 does not seem to be forwarding DHCP requests or responses for client devices attached via the WN2000RPTv2, either wired or wirelessly.
I manually configured the IPV4 address for the WN2000RPTv2 having identified which IP address was being handed out by DHCP server and then logging into the WN2000RPTv2 from a locally connected PC using one of the four 10/100 ports and a manually allocated IPV4 address.
Even with a non-DHCP address for the WN2000RPTv2 any client devices connecting via the WN2000RPTv2 still have the same problem (fail to get a DHCP address from the DHCP server), so need to have their IPv4 addresses etc. configured manually.
This makes the WN2000RPTv2 difficult to use for people without good network knowledge.
What should happen is that a client device should have its MAC address forwarded as part of the DHCP request packet to the primary wireless access point, which should in turn pass the DHCP request along to the DHCP server, which should then pass back the necessary set of information (IP address, gateway address, etc.) . The WN2000RPTv2 does not seem to be forwarding DHCP requests or responses for client devices attached via the WN2000RPTv2, either wired or wirelessly.