Windows clients unable to obtain DHCP lease after server move.

I recently moved a dhcp server to another machine, the same ip address
and dhcp configuration, but now the clients cannot obtain a lease
anymore. I checked the logs and here is a sample:

Apr 27 04:07:09 dhcpd: DHCPINFORM from 10.1.10.148 via eth0
Apr 27 04:07:09 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via
eth0
Apr 27 04:07:09 dhcpd: DHCPINFORM from 10.1.10.148 via 10.1.10.1
Apr 27 04:07:09 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via
10.1.10.1
Apr 27 04:07:13 dhcpd: DHCPINFORM from 10.1.10.148 via eth0
Apr 27 04:07:13 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via
eth0
Apr 27 04:07:13 dhcpd: DHCPINFORM from 10.1.10.148 via 10.1.10.1
Apr 27 04:07:13 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via
10.1.10.1

thank,

--tj

On Fri, 02 May 2008 08:42:36 -0700, (E-Mail Removed) wrote:

> I recently moved a dhcp server to another machine, the same ip address
> and dhcp configuration, but now the clients cannot obtain a lease
> anymore. I checked the logs and here is a sample:
>
> Apr 27 04:07:09 dhcpd: DHCPINFORM from 10.1.10.148 via eth0 Apr 27
> 04:07:09 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via eth0

This looks like a quite normal behavior, but AFAIK not part of the
process of obtaining an IP address from the DHCP server.

Please look at the "Windows Client" section of:
http://www.brennan.id.au/10-DHCP_Server.html

--
Regards/mvh Joachim Mæland

If everything seems under control, you're just not going fast enough.
-Mario Andretti

On May 2, 11:41 am, Joachim Mæland <jm-n...@profine.net> wrote:
> On Fri, 02 May 2008 08:42:36 -0700, techjoh...@gmail.com wrote:
> > I recently moved a dhcp server to another machine, the same ip address
> > and dhcp configuration, but now the clients cannot obtain a lease
> > anymore. I checked the logs and here is a sample:
>
> > Apr 27 04:07:09 dhcpd: DHCPINFORM from 10.1.10.148 via eth0 Apr 27
> > 04:07:09 dhcpd: DHCPACK to 10.1.10.148 (00:17:31:c0:9e:d5) via eth0
>
> This looks like a quite normal behavior, but AFAIK not part of the
> process of obtaining an IP address from the DHCP server.
>
> Please look at the "Windows Client" section of:http://www.brennan.id.au/10-DHCP_Server.html
>
> --
> Regards/mvh Joachim Mæland
>
> If everything seems under control, you're just not going fast enough.
> -Mario Andretti

Here is my dhcpd.conf file:

authoritative;
ddns-update-style ad-hoc;
subnet 10.1.10.0 netmask 255.255.255.0
{
range 10.1.10.50 10.1.10.150;
option domain-name "domain.com";
option routers 10.1.10.15;
option subnet-mask 255.0.0.0;
option domain-name-servers 10.1.10.15;
option broadcast-address 10.1.10.255;
default-lease-time 21600;
max-lease-time 43200;

}

This is exactly the same confirmation that I had on serverA, but after
moving ISC dhcp server to serverB, my Windows clients can no longer
obtain their ip address, so I've configured everybody with static.

--tj

On Thu, 08 May 2008 10:13:39 -0700, (E-Mail Removed) wrote:

> This is exactly the same confirmation that I had on serverA, but after
> moving ISC dhcp server to serverB, my Windows clients can no longer
> obtain their ip address, so I've configured everybody with static.

Where in this does your trying my suggested test by forcing your ill
behaved Wintendoes to release and obtain a new IP addresses go?

Believe me, you have not posted anything from your Windblows obtaining an
IP address. At best, you have posted the result of your Billys performing
something like: "I'm a sucking ignorant blower, I don't care about
protocol and I'm used to have the IP address XX:XX:XX:XX:XX:XX, any
objections???" Or something else, way out of context, I don't know.

Please read the link I gave you...!

The part about "Testing The Server" is good practice too...


--
Regards/mvh Joachim Mæland

If everything seems under control, you're just not going fast enough.
-Mario Andretti

On May 8, 11:30 am, Joachim Mæland <jm-n...@profine.net> wrote:
> On Thu, 08 May 2008 10:13:39 -0700, techjoh...@gmail.com wrote:
> > This is exactly the same confirmation that I had on serverA, but after
> > moving ISC dhcp server to serverB, my Windows clients can no longer
> > obtain their ip address, so I've configured everybody with static.
>
> Where in this does your trying my suggested test by forcing your ill
> behaved Wintendoes to release and obtain a new IP addresses go?
>
> Believe me, you have not posted anything from your Windblows obtaining an
> IP address. At best, you have posted the result of your Billys performing
> something like: "I'm a sucking ignorant blower, I don't care about
> protocol and I'm used to have the IP address XX:XX:XX:XX:XX:XX, any
> objections???" Or something else, way out of context, I don't know.
>
> Please read the link I gave you...!
>
> The part about "Testing The Server" is good practice too...
>
> --
> Regards/mvh Joachim Mæland
>
> If everything seems under control, you're just not going fast enough.
> -Mario Andretti

OK, I followed the instructions, and I even put the old server back on-
line, but the Windows clients do not obtain the IP Address. The
client tries to obtain an IP address and after failing it is given a
Microsoft private IP address (169 subnet).

The following is from the /var/log/messages during an attempt for a
Windows client to download an IP address (located on the same switch
as the server):

May 14 12:20:20 xxx dhcpd: DHCPDISCOVER from 00:16:d4:0f:02:14 (sales)
via 10.1.10.1
May 14 12:20:20 xxx dhcpd: DHCPOFFER on 10.1.10.50 to 00:16:d4:0f:
02:14 (sales) via 10.1.10.1
May 14 12:20:20 xxx dhcpd: DHCPREQUEST for 10.1.10.50 (10.1.10.15)
from 00:16:d4:0f:02:14 (sales) via eth0
May 14 12:20:20 xxx dhcpd: DHCPACK on 10.1.10.50 to 00:16:d4:0f:02:14
(sales) via eth0

Here is the current dhcpd.conf configuration:
ddns-update-style interim;
ignore client-updates;

subnet 10.1.10.0 netmask 255.255.255.0
{
range 10.1.10.25 10.1.10.75;
option domain-name "xxx";
option routers 10.1.10.15;
option subnet-mask 255.0.0.0;
option domain-name-servers 10.1.10.15;
option broadcast-address 10.1.10.255;
default-lease-time 21600;
max-lease-time 43200;

}

On Fri, 16 May 2008 12:40:10 -0700, (E-Mail Removed) wrote:

> Here is the current dhcpd.conf configuration: ddns-update-style interim;
> ignore client-updates;

Sorry, but insisting on having the same configuration on a working server
made me ignore your configuration file...

> subnet 10.1.10.0 netmask 255.255.255.0 {
[..]
> option subnet-mask 255.0.0.0;
> option broadcast-address 10.1.10.255;

This does not make sense to me. Remove "option subnet-mask 255.0.0.0;" or
better; change the line to: "option subnet-mask 255.255.255.0;" That is:
Make sure your netmask match your subnet addresses AND broadcast address.

Dunno if this will take care of your problem after restarting the DHCP
daemon, but if not:

Please read the "4.2. DHCP server configuration" section of http://
tldp.org/HOWTO/DHCP/x369.html. AFAIK, modern Windozes are not affected.

Please stop your server! Then read, understand and post the result of the
proper "/usr/sbin/dhcpd -d -f" from "4.4. Starting the server" at http://
tldp.org/HOWTO/DHCP/x369.html according to your setup!

And please post some additional information from your DHCP server:

# route -n
# ifconfig -a


--
Regards/mvh Joachim Mæland

If everything seems under control, you're just not going fast enough.
-Mario Andretti

On May 17, 2:46 am, Joachim Mæland <jm-n...@profine.net> wrote:
> On Fri, 16 May 2008 12:40:10 -0700, techjoh...@gmail.com wrote:
> > Here is the current dhcpd.conf configuration: ddns-update-style interim;
> > ignore client-updates;
>
> Sorry, but insisting on having the same configuration on a working server
> made me ignore your configuration file...
>
>
>
> > subnet 10.1.10.0 netmask 255.255.255.0 {
> [..]
> > option subnet-mask 255.0.0.0;
> > option broadcast-address 10.1.10.255;
>
> This does not make sense to me. Remove "option subnet-mask 255.0.0.0;" or
> better; change the line to: "option subnet-mask 255.255.255.0;" That is:
> Make sure your netmask match your subnet addresses AND broadcast address.
>
> Dunno if this will take care of your problem after restarting the DHCP
> daemon, but if not:
>
> Please read the "4.2. DHCP server configuration" section of http://
> tldp.org/HOWTO/DHCP/x369.html. AFAIK, modern Windozes are not affected.
>
> Please stop your server! Then read, understand and post the result of the
> proper "/usr/sbin/dhcpd -d -f" from "4.4. Starting the server" at http://
> tldp.org/HOWTO/DHCP/x369.html according to your setup!
>
> And please post some additional information from your DHCP server:
>
> # route -n
> # ifconfig -a
>
> --
> Regards/mvh Joachim Mæland
>
> If everything seems under control, you're just not going fast enough.
> -Mario Andretti
OK. I'm now getting a DORA (Discover/Offer/Requets/Ack), but still
unable to ping the XP client. It even updates the DNS records for the
internal zone. Another note, the ARP table for the ip address is
reported as (incomplete).

route -n:
255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 eth0
0.0.0.0 10.0.0.99 0.0.0.0 UG 0 0
0 eth0

ifconfig -a:

eth0 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:92
inet addr:10.1.10.15 Bcast:10.255.255.255 Mask:255.0.0.0
inet6 addr: fe80::20f:1fff:fe6e:a992/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42826401 errors:0 dropped:0 overruns:0 frame:0
TX packets:30846410 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2225403177 (2.0 GiB) TX bytes:1227483600 (1.1 GiB)
Interrupt:209

eth1 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:93
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:217

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1396628 errors:0 dropped:0 overruns:0 frame:0
TX packets:1396628 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:781296412 (745.1 MiB) TX bytes:781296412 (745.1
MiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

On May 28, 11:59 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
wrote:
> On May 17, 2:46 am, Joachim Mæland <jm-n...@profine.net> wrote:
>
> > On Fri, 16 May 2008 12:40:10 -0700, techjoh...@gmail.com wrote:
> > > Here is the current dhcpd.conf configuration: ddns-update-style interim;
> > > ignore client-updates;
>
> > Sorry, but insisting on having the same configuration on a working server
> > made me ignore your configuration file...
>
> > > subnet 10.1.10.0 netmask 255.255.255.0 {
> > [..]
> > > option subnet-mask 255.0.0.0;
> > > option broadcast-address 10.1.10.255;
>
> > This does not make sense to me. Remove "option subnet-mask 255.0.0.0;" or
> > better; change the line to: "option subnet-mask 255.255.255.0;" That is:
> > Make sure your netmask match your subnet addresses AND broadcast address..
>
> > Dunno if this will take care of your problem after restarting the DHCP
> > daemon, but if not:
>
> > Please read the "4.2. DHCP server configuration" section of http://
> > tldp.org/HOWTO/DHCP/x369.html. AFAIK, modern Windozes are not affected.
>
> > Please stop your server! Then read, understand and post the result of the
> > proper "/usr/sbin/dhcpd -d -f" from "4.4. Starting the server" at http://
> > tldp.org/HOWTO/DHCP/x369.html according to your setup!
>
> > And please post some additional information from your DHCP server:
>
> > # route -n
> > # ifconfig -a
>
> > --
> > Regards/mvh Joachim Mæland
>
> > If everything seems under control, you're just not going fast enough.
> > -Mario Andretti
>
> OK. I'm now getting a DORA (Discover/Offer/Requets/Ack), but still
> unable to ping the XP client. It even updates the DNS records for the
> internal zone. Another note, the ARP table for the ip address is
> reported as (incomplete).
>
> route -n:
> 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> 0 eth0
> 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 eth0
> 0.0.0.0 10.0.0.99 0.0.0.0 UG 0 0
> 0 eth0
>
> ifconfig -a:
>
> eth0 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:92
> inet addr:10.1.10.15 Bcast:10.255.255.255 Mask:255.0.0.0
> inet6 addr: fe80::20f:1fff:fe6e:a992/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:42826401 errors:0 dropped:0 overruns:0 frame:0
> TX packets:30846410 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2225403177 (2.0 GiB) TX bytes:1227483600 (1.1 GiB)
> Interrupt:209
>
> eth1 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:93
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:217
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1396628 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1396628 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:781296412 (745.1 MiB) TX bytes:781296412 (745.1
> MiB)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Looks like the MAC and WYSE clients are able to pickup leases, but not
the XP home machines.

On May 29, 10:06 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
wrote:
> On May 28, 11:59 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
> wrote:
>
>
>
> > On May 17, 2:46 am, Joachim Mæland <jm-n...@profine.net> wrote:
>
> > > On Fri, 16 May 2008 12:40:10 -0700, techjoh...@gmail.com wrote:
> > > > Here is the current dhcpd.conf configuration: ddns-update-style interim;
> > > > ignore client-updates;
>
> > > Sorry, but insisting on having the same configuration on a working server
> > > made me ignore your configuration file...
>
> > > > subnet 10.1.10.0 netmask 255.255.255.0 {
> > > [..]
> > > > option subnet-mask 255.0.0.0;
> > > > option broadcast-address 10.1.10.255;
>
> > > This does not make sense to me. Remove "option subnet-mask 255.0.0.0;"or
> > > better; change the line to: "option subnet-mask 255.255.255.0;" That is:
> > > Make sure your netmask match your subnet addresses AND broadcast address.
>
> > > Dunno if this will take care of your problem after restarting the DHCP
> > > daemon, but if not:
>
> > > Please read the "4.2. DHCP server configuration" section of http://
> > > tldp.org/HOWTO/DHCP/x369.html. AFAIK, modern Windozes are not affected..
>
> > > Please stop your server! Then read, understand and post the result of the
> > > proper "/usr/sbin/dhcpd -d -f" from "4.4. Starting the server" at http://
> > > tldp.org/HOWTO/DHCP/x369.html according to your setup!
>
> > > And please post some additional information from your DHCP server:
>
> > > # route -n
> > > # ifconfig -a
>
> > > --
> > > Regards/mvh Joachim Mæland
>
> > > If everything seems under control, you're just not going fast enough.
> > > -Mario Andretti
>
> > OK. I'm now getting a DORA (Discover/Offer/Requets/Ack), but still
> > unable to ping the XP client. It even updates the DNS records for the
> > internal zone. Another note, the ARP table for the ip address is
> > reported as (incomplete).
>
> > route -n:
> > 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> > 0 eth0
> > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> > 0 eth0
> > 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> > 0 eth0
> > 0.0.0.0 10.0.0.99 0.0.0.0 UG 0 0
> > 0 eth0
>
> > ifconfig -a:
>
> > eth0 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:92
> > inet addr:10.1.10.15 Bcast:10.255.255.255 Mask:255.0.0.0
> > inet6 addr: fe80::20f:1fff:fe6e:a992/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:42826401 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:30846410 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:2225403177 (2.0 GiB) TX bytes:1227483600 (1.1 GiB)
> > Interrupt:209
>
> > eth1 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:93
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > Interrupt:217
>
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:1396628 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1396628 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:781296412 (745.1 MiB) TX bytes:781296412 (745.1
> > MiB)
>
> > sit0 Link encap:IPv6-in-IPv4
> > NOARP MTU:1480 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Looks like the MAC and WYSE clients are able to pickup leases, but not
> the XP home machines.

more info:

dhcpd.leases has multiple entries on the same client address, over 10.

On Jun 3, 9:23 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
wrote:
> On May 29, 10:06 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
> wrote:
>
>
>
> > On May 28, 11:59 am, "techjoh...@gmail.com" <techjoh...@gmail.com>
> > wrote:
>
> > > On May 17, 2:46 am, Joachim Mæland <jm-n...@profine.net> wrote:
>
> > > > On Fri, 16 May 2008 12:40:10 -0700, techjoh...@gmail.com wrote:
> > > > > Here is the current dhcpd.conf configuration: ddns-update-style interim;
> > > > > ignore client-updates;
>
> > > > Sorry, but insisting on having the same configuration on a working server
> > > > made me ignore your configuration file...
>
> > > > > subnet 10.1.10.0 netmask 255.255.255.0 {
> > > > [..]
> > > > > option subnet-mask 255.0.0.0;
> > > > > option broadcast-address 10.1.10.255;
>
> > > > This does not make sense to me. Remove "option subnet-mask 255.0.0.0;" or
> > > > better; change the line to: "option subnet-mask 255.255.255.0;" Thatis:
> > > > Make sure your netmask match your subnet addresses AND broadcast address.
>
> > > > Dunno if this will take care of your problem after restarting the DHCP
> > > > daemon, but if not:
>
> > > > Please read the "4.2. DHCP server configuration" section of http://
> > > > tldp.org/HOWTO/DHCP/x369.html. AFAIK, modern Windozes are not affected.
>
> > > > Please stop your server! Then read, understand and post the result of the
> > > > proper "/usr/sbin/dhcpd -d -f" from "4.4. Starting the server" at http://
> > > > tldp.org/HOWTO/DHCP/x369.html according to your setup!
>
> > > > And please post some additional information from your DHCP server:
>
> > > > # route -n
> > > > # ifconfig -a
>
> > > > --
> > > > Regards/mvh Joachim Mæland
>
> > > > If everything seems under control, you're just not going fast enough..
> > > > -Mario Andretti
>
> > > OK. I'm now getting a DORA (Discover/Offer/Requets/Ack), but still
> > > unable to ping the XP client. It even updates the DNS records for the
> > > internal zone. Another note, the ARP table for the ip address is
> > > reported as (incomplete).
>
> > > route -n:
> > > 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> > > 0 eth0
> > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> > > 0 eth0
> > > 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> > > 0 eth0
> > > 0.0.0.0 10.0.0.99 0.0.0.0 UG 0 0
> > > 0 eth0
>
> > > ifconfig -a:
>
> > > eth0 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:92
> > > inet addr:10.1.10.15 Bcast:10.255.255.255 Mask:255.0.0.0
> > > inet6 addr: fe80::20f:1fff:fe6e:a992/64 Scope:Link
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:42826401 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:30846410 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:1000
> > > RX bytes:2225403177 (2.0 GiB) TX bytes:1227483600 (1.1 GiB)
> > > Interrupt:209
>
> > > eth1 Link encap:Ethernet HWaddr 00:0F:1F:6E:A9:93
> > > BROADCAST MULTICAST MTU:1500 Metric:1
> > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:1000
> > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > > Interrupt:217
>
> > > lo Link encap:Local Loopback
> > > inet addr:127.0.0.1 Mask:255.0.0.0
> > > inet6 addr: ::1/128 Scope:Host
> > > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > > RX packets:1396628 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:1396628 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:781296412 (745.1 MiB) TX bytes:781296412 (745.1
> > > MiB)
>
> > > sit0 Link encap:IPv6-in-IPv4
> > > NOARP MTU:1480 Metric:1
> > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:0
> > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> > Looks like the MAC and WYSE clients are able to pickup leases, but not
> > the XP home machines.
>
> more info:
>
> dhcpd.leases has multiple entries on the same client address, over 10.

FIXED:

Quit using and switched to "Dual DHCP DNS Server" @
http://sourceforge.net/project/showf...roup_id=132995

--tj