NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WNCE2001 inappropriately providing DHCP connections
I have a new WNCE2001 Wireless Ethernet bridge and have successfully configured it to connect my ethernet-only printer to my home network. This morning, I was unable to get to the internet from my iP...
jrconlin wrote: Just created an account to post what I believe resolves this problem.
The problem happens when you try to specify a static IP address for the device. The firmware kicks on DHCP with a very fast response time, causing any other devices to connect to it's subnet first. Fortunately, the firmware disables the internal DHCP when you have it connect out using DHCP (If that sounds confusing to you, don't worry, it's because I'm not going into details about WAN/LAN and other bits)
How do you have the device lock to a specific IP address? Most routers allow you to map MAC addresses to specific IP addresses. You can get the MAC address off the bottom of the device (it's the bottom most number).
Annoying as all get out, but it works.
Okay, you NEVER said specifically HOW to solve the issue. You mention all this mumbo jumbo, and we are supposed to guess?
Please, just come out and say what needs to be done:
1) Don't specify a static IP address and just let the device get its own address
2) Something about locking IPs to MAC addresses? Are you suggesting we should do this? Should we do this for ALL devices on our LAN?
I hope you see how utterly confusing your comments are and, all that aside, it is a "workaround," not a solution; not a true 'fix.'
Also, what makes you think users are setting a static IP for the device? I don't remember EVER setting a static for the device and here it is April 28, 2014, and THE PROBLEM STILL EXISTS!
There is NO commonality of "users messing up the setup;" there is just, plain and simple, a BUG in Netgear's product, and they don't want to admit it, nor do they want to fix it.
Additionally, if I had set (or other users had set) a static IP for their device, how/why does that ip seem to be 192.168.1.251? Seems very odd that almost everyone having this problem sees THAT specific IP.
And, all the above aside, whether or not users decide to set a static IP for their Netgear device, the device SHOULD ALLOW DHCP SERVER FEATURE TO BE TURNED OFF! PERIOD. END OF STORY.
Isn't it AMAZING that this BUG IS FIVE YEARS STRONG, AND NETGEAR STILL HAS *NOT* ADDRESSED THE ISSUE? And NO FIRMWARE UPDATE HAS FIXED THE ISSUE. I haven't taken mine apart to see if there's a Client/AP switch. If so, that could be the issue, but it would be nice for NETGEAR TO TELL US.
I smell a class action lawsuit as a possibility in Netgear's future!