Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am runnig centos 6.4, isc-dhcpd-4.1.1-P1. I have over 100 desktop laptops on win7. my dhcpd.log file is being flooded with following messages

Mar  3 11:08:06 tanaga dhcpd: DHCPREQUEST for 172.16.17.143 from 58:16:26:be:56:d7 via em1
Mar  3 11:08:06 tanaga dhcpd: DHCPACK on 172.16.17.143 to 58:16:26:be:56:d7 via em1
Mar  3 11:08:11 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:08:11 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:08:13 tanaga dhcpd: DHCPREQUEST for 172.16.17.140 from 58:16:26:be:56:7b via em1
Mar  3 11:08:13 tanaga dhcpd: DHCPACK on 172.16.17.140 to 58:16:26:be:56:7b via em1
Mar  3 11:08:15 tanaga dhcpd: DHCPREQUEST for 172.16.17.150 from 80:1d:aa:3b:ac:35 via em1
Mar  3 11:08:15 tanaga dhcpd: DHCPACK on 172.16.17.150 to 80:1d:aa:3b:ac:35 via em1
Mar  3 11:08:18 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:08:18 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:08:18 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:08:18 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:08:40 tanaga dhcpd: DHCPREQUEST for 192.168.1.18 from 4c:8d:79:b2:5a:da via em1: wrong network.
Mar  3 11:08:40 tanaga dhcpd: DHCPNAK on 192.168.1.18 to 4c:8d:79:b2:5a:da via em1






Mar  3 10:47:22 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:53:59 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:54:03 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:54:50 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:54:55 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:55:42 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 10:57:00 tanaga dhcpd: uid lease 172.16.19.242 for client b8:ca:3a:d3:78:d0 is duplicate on 172.16.16.0/22
Mar  3 11:02:32 tanaga dhcpd: uid lease 172.16.18.22 for client 18:03:73:b2:08:fe is duplicate on 172.16.16.0/22
Mar  3 11:02:52 tanaga dhcpd: uid lease 172.16.19.219 for client b8:ca:3a:81:26:5d is duplicate on 172.16.16.0/22
Mar  3 11:04:35 tanaga dhcpd: uid lease 172.16.19.251 for client 00:25:64:c0:51:fc is duplicate on 172.16.16.0/22
Mar  3 11:05:08 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 11:05:08 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22
Mar  3 11:06:07 tanaga dhcpd: uid lease 172.16.19.77 for client 90:b1:1c:64:36:55 is duplicate on 172.16.16.0/22

Mar  3 11:08:43 tanaga dhcpd: DHCPREQUEST for 192.168.1.18 from 4c:8d:79:b2:5a:da via em1: wrong network.
Mar  3 11:08:43 tanaga dhcpd: DHCPNAK on 192.168.1.18 to 4c:8d:79:b2:5a:da via em1
Mar  3 11:08:51 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:08:51 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:08:54 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:08:54 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:09:00 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:09:00 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:09:11 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:09:11 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:09:11 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:09:11 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1
Mar  3 11:09:11 tanaga dhcpd: DHCPREQUEST for 172.16.19.180 from 00:d0:23:0a:ea:cf via em1: lease 172.16.19.180 unavailable.
Mar  3 11:09:11 tanaga dhcpd: DHCPNAK on 172.16.19.180 to 00:d0:23:0a:ea:cf via em1

The problem is the machines are asking for ip addresses that where statically previously assigned to them, then they get set the ip they should from dhcp. this should not be happening. the pcs should not be asking dhcp for their old address.

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.