HELP! dhcp server not talking to clients

[Charles Lewis <lewisc@delta.swau.edu>]

I have dhcp set up on my linux box to serve a Win2000 box, a Win98 box, 
a WinXP box, and networked HP LJ1200. It works fine, until I try to 
upgrade the kernel from 2.4.18 to 2.4.20 (from an earlier thread). The 
machine locks up after a few minutes, so I go back to 2.4.18, and all my 
 machines are getting 198.168.1.x numbers when my dhcp server is 
supposed to be providing 10.0.0.x numbers. It's very frustrating to 
everyone in the house because suddenly none of them can use the 
internet, print, or save files to their samba shares. Now I am not a 
network guru, so maybe someone can help me spot some problems in my setup.

Here is my dhcpd.conf:

#option domain-name "";
#option domain-name-servers 205.165.192.254,205.165.193.254;

server-identifier lewisc;
authoritative;
option subnet-mask 255.255.255.0;
default-lease-time 600;
max-lease-time 7200;
subnet 10.0.0.0 netmask 255.255.255.0 {
  range 10.0.0.6 10.0.0.254;
  option broadcast-address 10.0.0.255;
  option routers 10.0.0.1;
  option netbios-name-servers 10.0.0.1;
}

host lewisc2 {
  hardware ethernet 00:01:03:E7:48:1F;
  fixed-address 10.0.0.2;
}

host lewisc3 {
  hardware ethernet 00:00:39:F0:9A:C5;
  fixed-address 10.0.0.3;
}

host caleb {
  hardware ethernet 00:A0:CC:D2:A0:73;
  fixed-address 10.0.0.4;
}

host officelj {
  hardware ethernet 00:01:E6:48:69:A2;
  fixed-address 10.0.0.5;
}

When I run dhcpd in debug mode, I get:

Listening on LPF/eth0/00:01:03:dd:22:e0/10.0.0.0
Sending on   LPF/eth0/00:01:03:dd:22:e0/10.0.0.0
Sending on   Socket/fallback/fallback-net

And it just sits there with no feedback.

When I do a tcpdump -i eth0, I get the following junk:
23:46:04.324753 192.168.1.102.netbios-dgm > 192.168.1.255.netbios-dgm: 
NBT UDP PACKET(138)
23:46:33.933645 192.168.1.1.bootps > 255.255.255.255.bootpc: 
xid:0xbee8b113 C:192.168.1.101 Y:192.168.1.101 ether 0:1:e6:48:69:a2 
file ""[|bootp]
23:46:36.287786 arp who-has 192.168.1.1 tell 192.168.1.102
23:46:36.289146 192.168.1.1.bootps > 255.255.255.255.bootpc: 
xid:0xf220e34f C:192.168.1.102 Y:192.168.1.102 ether 0:a0:cc:d2:a0:73 
file ""[|bootp]
23:49:04.314952 192.168.1.1.bootps > 255.255.255.255.bootpc: 
xid:0x28e8b113 C:192.168.1.101 Y:192.168.1.101 ether 0:1:e6:48:69:a2 
file ""[|bootp]
23:49:06.268378 arp who-has 192.168.1.1 tell 192.168.1.102
23:49:06.269729 192.168.1.1.bootps > 255.255.255.255.bootpc: 
xid:0xdd3f9a45 C:192.168.1.102 Y:192.168.1.102 ether 0:a0:cc:d2:a0:73 
file ""[|bootp]

The last time this happened, it eventually started working, but I think 
it may have been because the lease ran out on all the machines. *shrug* 
I don't know but I'm ready to pull what little hair I have left out. Any 
ideas would be GREATLY appreciated.

Charles Lewis