Odd DHCP behavior (Vista losing IP?)

Jason Frisvold frisvolj at lafayette.edu
Tue Apr 13 21:42:27 UTC 2010 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

	I'm having an odd problem that I haven't been able to solve, so I'm
looking for help on fixing this.

	We have several thousand machines on the network.  The majority of
these appear to be working fine as I have had no complaints regarding
connectivity.  I have one lab in particular, though, where the machines
seem to get an IP from DHCP and then drop that IP a few minutes later.
They don't renew their IP without manual intervention.  All of these
machines are Vista machines.

	Both the dhcpd.leases file as well as the dhcp.log file have been moved
to ramdisk to increase the speed of the server.  I definitely recommend
doing this, btw, as the speed increase was amazing..

	The config is pretty straightforward, lots of scopes, lots of hosts.
I've cut the config down and removed the extraneous scope and host
information :

log-facility local6;
lease-file-name "/var/ramlog/dhcpd.leases";

min-lease-time 3600;
max-lease-time 86400;
default-lease-time 86400;

allow bootp;
allow booting;

ddns-update-style ad-hoc;
ddns-updates off;

authoritative;

key OMAPI {
   algorithm hmac-md5;
   secret thisismysooperdooperseekrit;
};

omapi-port 7911;

failover peer "dhcp1" {
   primary;
   address 192.168.0.1;
   port 647;
   peer address 192.168.1.1;
   peer port 647;
   max-response-delay 60;
   max-unacked-updates 10;
   mclt 600;
   split 128;
   load balance max seconds 15;
}

option domain-name "lafayette.edu";

include "/etc/dhcpd/dhcpd-primary.cfg";

- ----------

The primary.cfg file looks like this :

subnet 192.168.0.0 netmask 255.255.255.0 {
        option routers 192.168.0.254;
        option domain-name-servers 172.20.0.1 , 172.20.0.2;
}

subnet 192.168.10.224 netmask 255.255.255.240 {
        option routers 192.168.10.225;
        option domain-name-servers 172.20.0.1 , 172.20.0.2;
        pool {
                deny dynamic bootp clients;
                failover peer "dhcp1";
                range 192.168.10.228 192.168.10.254;
        }
}

- ----------

The only section of the dhcpd.conf on the secondary server that is
different is this :

failover peer "dhcp1" {
   secondary;
   address 192.168.1.1;
   port 647;
   peer address 192.168.0.1;
   peer port 647;
   max-response-delay 60;
   max-unacked-updates 10;
   load balance max seconds 15;
}

And, of course, there's a relevant definition for the local subnet
(192.168.1.1/24)

- ----------

Here are relevant logs from the dhcp server:

- ----------
DHCP0:

Apr 13 11:25:19 dhcp0 dhcpd: DHCPDISCOVER from 00:11:22:33:44:55
(Lang05) via 192.168.100.227: load balance to peer dhcp1
Apr 13 11:25:19 dhcp0 dhcpd: DHCPDISCOVER from 00:11:22:33:44:55
(Lang05) via 192.168.100.226: load balance to peer dhcp1
Apr 13 11:25:20 dhcp0 dhcpd: uid lease 192.168.10.231 for client
00:11:22:33:44:55 is duplicate on 192.168.10.224/27
Apr 13 11:25:20 dhcp0 dhcpd: DHCPREQUEST for 192.168.10.238
(192.168.1.1) from 00:11:22:33:44:55 (Lang08) via 192.168.100.227: lease
owned by peer
Apr 13 11:25:20 dhcp0 dhcpd: DHCPREQUEST for 192.168.10.238
(192.168.1.1) from 00:11:22:33:44:55 (Lang08) via 192.168.100.226: lease
owned by peer
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.226
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.227
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.227
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.226
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.226
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.227
Apr 13 11:25:22 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:41 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.226
Apr 13 11:25:41 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:41 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.227
Apr 13 11:25:41 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:27:17 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.226
Apr 13 11:27:17 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:27:17 dhcp0 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.100.227
Apr 13 11:27:17 dhcp0 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.227
Apr 13 11:35:52 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.226
Apr 13 11:35:52 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.226
Apr 13 11:35:52 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.227
Apr 13 11:35:52 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:53 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.227
Apr 13 11:35:53 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:53 dhcp0 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.100.226
Apr 13 11:35:53 dhcp0 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0


DHCP1:

Apr 13 11:25:19 dhcp1 dhcpd: pool 2b98e56549a0 192.168.10.224/27 total
27  free 9  backup 5  lts 2
Apr 13 11:25:19 dhcp1 dhcpd: DHCPDISCOVER from 00:11:22:33:44:55
(Lang05) via 192.168.10.227
Apr 13 11:25:19 dhcp1 dhcpd: DHCPDISCOVER from 00:11:22:33:44:55
(Lang05) via 192.168.10.226
Apr 13 11:25:20 dhcp1 dhcpd: DHCPOFFER on 192.168.10.238 to
00:11:22:33:44:55 (Lang05) via 192.168.10.227
Apr 13 11:25:20 dhcp1 dhcpd: DHCPOFFER on 192.168.10.231 to
00:11:22:33:44:55 (Lang05) via 192.168.10.226
Apr 13 11:25:20 dhcp1 dhcpd: DHCPREQUEST for 192.168.10.238
(192.168.1.1) from 00:11:22:33:44:55 (Lang05) via 192.168.10.227
Apr 13 11:25:20 dhcp1 dhcpd: DHCPACK on 192.168.10.238 to
00:11:22:33:44:55 (Lang05) via 192.168.10.227
Apr 13 11:25:20 dhcp1 dhcpd: DHCPREQUEST for 192.168.10.238
(192.168.1.1) from 00:11:22:33:44:55 (Lang05) via 192.168.10.226
Apr 13 11:25:20 dhcp1 dhcpd: DHCPACK on 192.168.10.238 to
00:11:22:33:44:55 (Lang05) via 192.168.10.226
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.227
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.226
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.227
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.226
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.227
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:22 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.226
Apr 13 11:25:22 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:41 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.226
Apr 13 11:25:41 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:25:41 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.227
Apr 13 11:25:41 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:27:17 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.227
Apr 13 11:27:17 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:27:17 dhcp1 dhcpd: DHCPINFORM from 192.168.10.238 via
192.168.10.226
Apr 13 11:27:17 dhcp1 dhcpd: DHCPACK to 192.168.10.238
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.227
Apr 13 11:35:52 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.226
Apr 13 11:35:52 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.226
Apr 13 11:35:52 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:52 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.227
Apr 13 11:35:52 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:53 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.227
Apr 13 11:35:53 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0
Apr 13 11:35:53 dhcp1 dhcpd: DHCPINFORM from 169.254.139.235 via
192.168.10.226
Apr 13 11:35:53 dhcp1 dhcpd: DHCPACK to 169.254.139.235
(00:11:22:33:44:55) via eth0


If there's some other bit of information I can provide to help, please
let me know..  This one has me tearing my hair out...

- -- 
- ---------------------------
Jason Frisvold
Network Engineer
frisvolj at lafayette.edu
- ---------------------------
"What I cannot create, I do not understand"
   - Richard Feynman
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkvE5UMACgkQO80o6DJ8UvkKZwCdEo932Q2JkeNGsRYlF5WT2SgB
jUoAoJHYNAfbu/3IJ4tR+wZ8XsjEvRQt
=S4Yt
-----END PGP SIGNATURE-----

More information about the dhcp-users mailing list