[SOLVED] DHCPDECLINE of ipaddress from mac via interface not found

McUserton · 10-15-2010, 03:16 PM

My windows XP computer cannot get an IP address from the Ubuntu 10.04 DHCP server. It is configured on the DHCP server to receive a static address outside the main DHCP pool.

Partial config:

Quote:

subnet 192.168.168.0 netmask 255.255.255.0 {
pool {
failover peer "dc02";
range 192.168.168.1 192.168.168.164;
deny dynamic bootp clients;
allow unknown clients;
}
option routers 192.168.168.168;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.168.168;
option domain-name-servers 192.168.168.203, 192.168.168.204;
option ntp-servers 192.168.168.204;
option netbios-name-servers 192.168.168.204;
option netbios-node-type 2;
default-lease-time 86400;
max-lease-time 86400;

Static IP assignment found inside the subnet portion:

Quote:

host IT-Laptop {
allow client-updates;
allow unknown-clients;
ddns-updates on;
hardware ethernet 00:1b:38:7f:eb:06;
fixed-address 192.168.168.178;
}

Error messages:

Quote:

DC01 dhcpd: DHCPDISCOVER from 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPOFFER on 192.168.168.178 to 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPREQUEST for 192.168.168.178 (192.168.168.203) from 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPACK on 192.168.168.178 to 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPREQUEST for 192.168.168.178 (192.168.168.204) from 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPACK on 192.168.168.178 to 00:1b:38:7f:eb:06 via bond0
DC01 dhcpd: DHCPDECLINE of 192.168.168.178 from 00:1b:38:7f:eb:06 via bond0: not found

The Windows machine seems to think there is already another computer on the network with 192.168.168.178, but it's wrong: there is no such address on the network.

Does anyone have any idea where to look or what to try?

rweaver · 10-15-2010, 03:33 PM

Is the windows machine configured statically already or is it actually dhcping an address? If you attempt to ping the address it doesn't work correct?

markush · 10-15-2010, 03:40 PM

Hello McUserton,

the line

Code:

option broadcast-address 192.168.168.168;

looks odd to me. Isn't 192.168.168.255 the broadcastadress for a 192.168.168.0/24 network?

Markus

McUserton · 10-17-2010, 07:38 PM

Quote:

Originally Posted by rweaver

Is the windows machine configured statically already or is it actually dhcping an address? If you attempt to ping the address it doesn't work correct?

The windows client is configured for DHCP, correct. If you try to ping .178, the address in question, no replies are returned.

McUserton · 10-17-2010, 07:39 PM

Quote:

Originally Posted by markush

Hello McUserton,

the line

Code:

option broadcast-address 192.168.168.168;

looks odd to me. Isn't 192.168.168.255 the broadcastadress for a 192.168.168.0/24 network?

Markus

Ouch - good catch!! I missed that. I'll correct it and report back if it helped the situation, which it may. Thanks.

McUserton · 10-18-2010, 08:54 AM

Quote:

Originally Posted by McUserton

Ouch - good catch!! I missed that. I'll correct it and report back if it helped the situation, which it may. Thanks.

Thanks, Markush - the incorrect broadcast address appears to have been the source of the problem.