[Dnsmasq-discuss] DHCPDECLINE from windows vista clients

[richardvoigt at gmail.com]

You probably have a device on the network doing proxy-arp incorrectly,
and making Vista think the offered address is already in use.

see http://puck.nether.net/pipermail/cisco-nsp/2007-February/038695.html

Then run a packet capture (e.g. wireshark) and find out what device is
replying to the g-arp packets.

On Thu, Nov 18, 2010 at 3:29 PM, Salatiel Filho
<salatiel.filho at gmail.com> wrote:
> I have dnsmasq serving dhcps for a small network, about 250 clients...
> Clients are migrating from windows xp to windows vista or windows 7
> and i started to get lots of problems where they just do not get the
> IP from dnsmasq....
>
> The log shows DHCPDECLINE...
>
> Nov 18 04:41:10 v2 daemon.info dnsmasq-dhcp[4446]:
> DHCPDISCOVER(br-lan) 00:26:82:0a:01:71
> Nov 18 04:41:10 v2 daemon.info dnsmasq-dhcp[4446]: DHCPOFFER(br-lan)
> 192.168.200.123 00:26:82:0a:01:71
> Nov 18 04:41:10 v2 daemon.info dnsmasq-dhcp[4446]: DHCPREQUEST(br-lan)
> 192.168.200.123 00:26:82:0a:01:71
> Nov 18 04:41:10 v2 daemon.info dnsmasq-dhcp[4446]: DHCPACK(br-lan)
> 192.168.200.123 00:26:82:0a:01:71 andre
> Nov 18 04:41:14 v2 daemon.info dnsmasq-dhcp[4446]: DHCPDECLINE(br-lan)
> 192.168.200.123 00:26:82:0a:01:71
> Nov 18 04:41:14 v2 daemon.warn dnsmasq-dhcp[4446]: disabling DHCP
> static address 192.168.200.123 for 10m
> Nov 18 04:41:24 v2 daemon.warn dnsmasq-dhcp[4446]: not using
> configured address 192.168.200.123 because it was previously declined
> Nov 18 04:41:24 v2 daemon.info dnsmasq-dhcp[4446]:
> DHCPDISCOVER(br-lan) 00:26:82:0a:01:71 no address available
> Nov 18 04:41:28 v2 daemon.warn dnsmasq-dhcp[4446]: not using
> configured address 192.168.200.123 because it was previously declined
> Nov 18 04:41:28 v2 daemon.info dnsmasq-dhcp[4446]:
> DHCPDISCOVER(br-lan) 00:26:82:0a:01:71 no address available
> Nov 18 04:41:37 v2 daemon.warn dnsmasq-dhcp[4446]: not using
> configured address 192.168.200.123 because it was previously declined
> Nov 18 04:41:37 v2 daemon.info dnsmasq-dhcp[4446]:
> DHCPDISCOVER(br-lan) 00:26:82:0a:01:71 no address available
>
>
> it appears to be related to  DHCP BROADCAST flag.
>
> http://support.microsoft.com/kb/928233/en-us/
>
> There is a workaround by editing a registry key but it is too
> complicated set registry keys on clients...
> We are not a domain  , so can not apply gpo policies...
>
> Is there a ways to make dnsmasq answer "correctly" to windows vista clients ?
>
>
>
> []'s
> Salatiel
>
> "O maior prazer do inteligente é bancar o  idiota
>    diante de um  idiota que banca o inteligente".
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>