We have just upgraded our DHCP server from Red Hat Linux 6.2 to Fedora Core 4. We copied over the old dhcpd.conf file and things are not working as expected. Here is what I see whenever a dhcp client tries to obtain an IP address:

Jan 26 15:59:14 iidns dhcpd: DHCPDISCOVER from 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:14 iidns dhcpd: DHCPOFFER on 192.168.0.184 to 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:14 iidns dhcpd: DHCPREQUEST for 192.168.0.184 (206.157.72.238) from 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:14 iidns dhcpd: DHCPACK on 192.168.0.184 to 00:02:b3:28:0e:ae (ii415) via eth0

Jan 26 15:59:15 iidns dhcpd: DHCPDISCOVER from 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:15 iidns dhcpd: DHCPOFFER on 192.168.0.184 to 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:15 iidns dhcpd: DHCPREQUEST for 192.168.0.184 (206.157.72.238) from 00:02:b3:28:0e:ae (ii415) via eth0
Jan 26 15:59:15 iidns dhcpd: DHCPACK on 192.168.0.184 to 00:02:b3:28:0e:ae (ii415) via eth0

The client requests the IP address again and again and I cannot figure out why the DHCPACK message does not complete the client's request. Is the client not reading the message? Is the server not formatting the message correctly? Is there an error in the DHCPACK message?

Here is a copy of my dhcpd.conf file:

server-identifier 192.168.1.238;
ddns-update-style none;
shared-network ii_internal {

subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.10;
option broadcast-address 192.168.1.255;
option domain-name "interact.nonreg";
option domain-name-servers 192.168.1.238;
}

subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
option netbios-name-servers 192.168.1.98;
option broadcast-address 192.168.1.255;
option domain-name "interact.nonreg";
option domain-name-servers 192.168.1.238;
range 192.168.0.150 192.168.0.195;
}

I have some groups setup after this part, but I don't think it is relevant to my problem. We have 2 subnets set up and everything is configured within the routers to let them talk to each other (this is why the 192.168.0.x network uses the 192.168.1.238 dns server). I want all dhcp users to pull 192.168.0.x addresses. Like I said, this all worked under 6.2, but now it is causing some problems.

Thank you in advance for any help.

How long is the lease being granted on the address? If the Server has started handing out zero time leases due to some sort of issue with config files between versions, this would happen. Just a guess.