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, 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

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, techjohnny@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