LAN connectivity interrupted while renewing IP address lease

[searay]

This is when you ask for a supervisor until you are transfered to one. I am not sticking up for them I am only telling you how it has worked for me. I have had 2 different cases on two routers in the past year. One has been resolved and I am testing currently to be sure the second has also been resolved. Read my old post if your interested and read between the lines.

[searay]

Regarding address reservations list, I removed a device from the list but it still showed up as attached without an IP.

I ended up fixing this by going to factory defaults, reloaded firmware, then reloaded config.

[searay]

IP AddressDevice NameMAC Address1192.168.0.7VAIO00:0E:0C:C6:6F:A62192.168.0 .16HPSTORAGE00:0A:E4:86:8F:403192.168.0.13Airave00 :05:B9:05:58:B84192.168.0.11LanBox6C:62:6D:E2:C8:2 C5192.168.0.12NeoTVE0:91:F5:93:69:126192.168.0.4Le novo G555C4:46:19:40:10:427192.168.0.6Acer00:24:2B:21:3 1:3D8192.168.0.10Pcg-K2700:0E:9B:28:FB:A09192.168.0.5ILSCHL-2S335L100:24:E8D:54:7C10192.168.0.8DeskJet00:30: 6E:C6:70:BE11192.168.0.25Evo_Patti38:E78:6B3 B12192.168.0.24Evo_Kim38:E78:6E:2E:C513192.168.0 .23Evo_Bill38:E78:6D:07:1E14192.168.0.15YM900CFB 00:0B:3F:90:0C:FB15192.168.0.14YM900EDD00:0B:3F:90 :0ED16192.168.0.2VGN-Z54000:21:5D:88:19:4C17192.168.0.30WNDR3700C0:3F:0 E:904:66
I do not have any issue with DHCP using .60

[James_NOT_Bond]

There's an exception for this case. If the DHCP IP reservration is correct with the DHCP client, that would be worth to be further studied.

[punkUser]

Originally Posted by searay

I do not have any issue with DHCP using .60

As I mentioned earlier, the issue definitely still occurs in .60. Not sure of the exact repro steps but I have all my machines getting IPs via DHCP w/ some of them having reserved ones. At least with the reserved ones ever 12 hours they'll get a DHCPNACK packet when trying to renew, drop the interface, renew and then get the exact same (reserved) IP as before... as noted, just bad state machine logic on the router it seems.

The only workaround I've found so far is to assign the machine(s) a static IP. This isn't the worst thing ever since the router relays DNS traffic (and thus you don't need to hard-core the ISP DNS servers or anything), but it shouldn't be necessary.

I'm sure there's an easy software fix for this. I can't see this being done in hardware considering how infrequent and inexpensive DHCP logic is.

[BillTheCat]

Originally Posted by punkUser

I'm sure there's an easy software fix for this. I can't see this being done in hardware considering how infrequent and inexpensive DHCP logic is.

Agreed. There's no way that any manufacturer is implementing TCP/IP application layer protocols like DHCP in hardware for consumer-grade routers.

Unfortunately, bugs that can be easily fixed in firmware frequently aren't by D-Link and Linksys. On a good day, their firmware developers can sometimes tie their own shoes. We simply discard resumes from developers with consumer appliance work history with those two firms. Of course, these are not the same people as the ones that develop firmware for high-end Cisco routers.

I'm beyond the allowable return date for my WNDR4000, but trying Netgear out was an experiment anyway. I can and will be blacklisting Netgear purchases where I work if they don't demonstrate themselves superior to their competition, but I'd still like to think Netgear may come through. We'll probably give them another month, 7 weeks max.

So, Netgear, will you step up and show us that you can not only fix this simple problem but release the fix in a timely fashion?

[92merc]

I think I'm having a similar issue. I'll have my son's Vizio TV on and working. I booted up my PC that has an IP reservation, son comes out, TV isn't on the network anymore. (He was watching Netflix).

I had my Wii setup yesterday and working wirelessly. I boot up another machine, and the Wii drops off.

Netgear definitely has something fubar withe their DHCP. I just got done hard coding my son's laptop, TV, and the Wii. I'll see if they stop having issues.

While my old Linksys didn't have the best reception, it flat out worked. I would return my new Netgear if I could. With all the hassles, having Parental controls just doesn't justify the issues I'm having.

[CheDigital]

I've been experiencing occasional very brief wireless internet drops - disconnects lasting maybe a minute or so, then re-connecting without any issues. I've had trouble identifying whether the issue was my internet, or some other setting in the router, but I'm pretty confident I'm having this same issue.

I've checked event logs on my desktop running Win7 and a laptop running XP, both showing the DHCPNACK error consistently in logs. There are periods where I'm getting the DHCPNACK more than every 12 hours, but I think those are during periods where I've been trying to troubleshoot the router and doing reboots on various devices to figure out what's wrong. There are also long periods that show the error every 12 hours.

This is an extremely annoying problem, and I'm just beyond the month for returning the router. Not sure what to do next other than hope this gets fixed.

[searay]

I checked my HPMediasever an found that it too receives the DHCPNACK every 12 hours. I use DHCP Resverations for everything. Today I E-mailed a screen shot of these ERRORS to the Product Engineer for the WNDR4000 and asked him if he could explain why this is happening.

[searay]

Good News!

This appears to be fixed expect a update in Sept.