Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[amb9800]

My DIR-655 worked perfectly for many months and then began to give some connectivity problems, so I upgraded to the 1.34NA firmware.

Since then, DHCP seems to have gone haywire.  We have about 15 wired or wireless clients (PCs/phones/printers/etc.) on the LAN, and at any given time, at least a few, if not most, are off the network because they've been assigned duplicate IPs and go into APIPA addressing (thus losing net connectivity).

The Windows PCs give an error message that a duplicate IP has been detected (and so does my Windows Mobile phone), and the printers and Apple devices just don't work.

I've checked to make sure no machine has any static IPs or other configuration issues and reloaded the router firmware, to no effect.  After a firmware reload, it generally works fine for a few hours then starts giving out duplicate IPs.

Any ideas?

[EddieZ]

Another DHCP device present in the LAN?

[amb9800]

Yeah that's what I initially suspected, but I went through each device on the network to check (particularly looking for things like smartphone Wifi tethering apps)-- doesn't look like it.

[davevt31]

How long is you DHCP lease set for on the router settings?  Might be too short a time period and the different devices are getting addresses that conflict with other devices.

[amb9800]

How long is you DHCP lease set for on the router settings?  Might be too short a time period and the different devices are getting addresses that conflict with other devices.

For some reason it listed "never" as the lease expiry time for all the DHCP clients (despite none being reserved), but once I manually revoked all the assignments, it started giving out 1440 minute (24 hour) leases as the (default) settings specified.  Made no difference though.

I have a whole subnet open for addressing, so I'm sort of perplexed how such issues could happen with just 15-20 clients.  Will try checking Windows networking logs on the PCs to look for any clues...

[amb9800]

Interesting-- checked the Event Viewer logs on the PCs.  Turns out the IP address conflict errors are occurring for APIPA addresses or 0.0.0.0 (i.e. "The system detected an address conflict for IP address 169.254.111.112 with the system having network hardware address ___[MAC address]___. Network operations on this system may be disrupted as a result.")

So essentially the problem is that the router is periodically just not giving clients IP addresses / renewing the leases.

[amb9800]

Ok, after trying everything under the moon, I think it's time to replace the router.

Stuck with D-Link for several years, but this has been annoying enough that I'm not touching D-Link again until they seriously improve their firmware.

Considering the Netgear WNDR3700 and Linksys E3000...

[EddieZ]

Ok, after trying everything under the moon, I think it's time to replace the router.

Stuck with D-Link for several years, but this has been annoying enough that I'm not touching D-Link again until they seriously improve their firmware.

Considering the Netgear WNDR3700 and Linksys E3000...

If it were a generic issue you resentment would be valid. But judging a whole brand only on your own experiences with this specimen is a bit dramatic, wouldn't you think so? Even Maybachs and Ferrari's break down once in a while.