windows clients decline on second lan segment

Jonathan Hirschman jonathan at hirschman.net
Wed Nov 7 01:51:02 UTC 2007


My windows clients reject dhcp addresses with a DHCPDECLINE one of two 
subnets/lan segments. Other clients (Linux, embedded stuff) have no 
problems. Windows clients are fine on one of the two segments, to the 
point where you can switch the network cable on a machine and it either 
works or does not depending upon which segment.

 From the Windows event viewer:

Your computer has detected that the IP address xxx.xxx.xxx.xxx for the 
Network Card with network address <MAC ADDRESS> is already in use on the 
network. Your computer will automatically attempt to obtain a different 
address.

The <MAC ADDRESS> mentioned above is the device's own mac address - 
absolutely nothing else is using the IP address, nor is the mac 
duplicated in any way.

Any clues?

Details:

I'm running dhcpd3 version 3.0.4 on Debian stable. No iptables or packet 
forwarding is enabled.

The hardware consists of two nics, one each for two network segments: 
192.168.1.0/24 and 192.168.2.0/24. The nics have been swapped during 
troubleshooting, no effect.

The following routing commands are issued (or not, does not seem to make 
a difference):

route add -host 255.255.255.255 dev eth0
route add -host 255.255.255.255 dev eth1

All Windows clients on the 192.168.2.0/24 network are doing this:

Nov  6 20:33:39 dhcpdns dhcpd: DHCPDISCOVER from 00:0a:e4:f3:34:96 via eth0
Nov  6 20:33:40 dhcpdns dhcpd: DHCPOFFER on 192.168.2.150 to 
00:0a:e4:f3:34:96 (relev_portable) via eth0
Nov  6 20:33:40 dhcpdns dhcpd: DHCPREQUEST for 192.168.2.150 
(192.168.2.2) from 00:0a:e4:f3:34:96 (relev_portable) via eth0
Nov  6 20:33:40 dhcpdns dhcpd: DHCPACK on 192.168.2.150 to 
00:0a:e4:f3:34:96 (relev_portable) via eth0
Nov  6 20:33:40 dhcpdns dhcpd: Abandoning IP address 192.168.2.150: 
declined.
Nov  6 20:33:40 dhcpdns dhcpd: DHCPDECLINE of 192.168.2.150 from 
00:0a:e4:f3:34:96 (relev_portable) via eth0: not found

Excerpts from dhcpd.conf:

authoritative;
option domain-name "xxx.com";

subnet 192.168.1.0 netmask 255.255.255.0 {
    range 192.168.1.100 192.168.1.199;
    option routers 192.168.1.1;
    option broadcast-address 192.168.1.255;

}
subnet 192.168.2.0 netmask 255.255.255.0 {
    range 192.168.2.100 192.168.2.150;
    option routers 192.168.2.1;
    option broadcast-address 192.168.2.255;
}


More information about the dhcp-users mailing list