Windows clients unable to obtain DHCP lease after server move. - Networking

This is a discussion on Windows clients unable to obtain DHCP lease after server move. - Networking ; 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 ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: Windows clients unable to obtain DHCP lease after server move.

  1. 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

  2. Re: Windows clients unable to obtain DHCP lease after server move.

    On Fri, 02 May 2008 08:42:36 -0700, techjohnny@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

  3. Re: Windows clients unable to obtain DHCP lease after server move.

    On May 2, 11:41 am, Joachim Mæland 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

  4. Re: Windows clients unable to obtain DHCP lease after server move.

    On Fri, 16 May 2008 12:40:10 -0700, techjohnny@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

  5. Re: Windows clients unable to obtain DHCP lease after server move.

    On May 17, 2:46 am, Joachim Mæland 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)


  6. Re: Windows clients unable to obtain DHCP lease after server move.

    On May 28, 11:59 am, "techjoh...@gmail.com"
    wrote:
    > On May 17, 2:46 am, Joachim Mæland 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.

  7. Re: Windows clients unable to obtain DHCP lease after server move.

    On May 29, 10:06 am, "techjoh...@gmail.com"
    wrote:
    > On May 28, 11:59 am, "techjoh...@gmail.com"
    > wrote:
    >
    >
    >
    > > On May 17, 2:46 am, Joachim Mæland 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.

  8. Re: Windows clients unable to obtain DHCP lease after server move.

    On Jun 3, 9:23 am, "techjoh...@gmail.com"
    wrote:
    > On May 29, 10:06 am, "techjoh...@gmail.com"
    > wrote:
    >
    >
    >
    > > On May 28, 11:59 am, "techjoh...@gmail.com"
    > > wrote:

    >
    > > > On May 17, 2:46 am, Joachim Mæland 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

+ Reply to Thread