dhcpd static binding problem

[Frank Leonhardt]

Below I've got a dhcpd.conf file, with only symbolic names changed and 
comments removed. It generally works just fine, until today when I added 
the static binding for WINDOWSVISTA-PC. Previously it was on the 
dynamically allocated .160. Whenever its lease expires it requests and 
receives an ACK for .160.

I've got the user to run "ipconfig /release" on the interface - they say 
they did it (and they're supposed to be a computer "engineer"). The 
lease has expired many times. I can run dhcpd in debug mode and watch it 
happening live.

Is it me or is it Windoze? And why doesn't dhcpd refuse the renewal? If 
its the order in the file, why does it work on WINDOWSXP-PC?

Thanks, Frank.



option domain-name "test.junk.foo";
option domain-name-servers 192.168.1.205, 192.168.1.206;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
log-facility local7;

subnet 192.168.1.0  netmask 255.255.255.0 {
   range 192.168.1.145 192.168.1.192;
    option routers 192.168.1.210;
    authoritative;
}

host WINDOWSXP-PC {
         hardware ethernet 00:19:21:10:83:13;
         fixed-address 192.169.1.194;
}

host WINDOWSVISTA-PC {
         hardware ethernet 00:21:97:02:b2:3e;
         fixed-address 192.169.1.229;
}