Hi All,

I am facing strange issue.

My DHCP server working fine till yesterday. But from today morning my Windows machines are not getting IP from DHCP server while Linux machines are getting. Please find the below logs from /var/log/messages.

Dec 12 10:50:34 sonic dhcpd: DHCPOFFER on 192.168.181.140 to f0:4d:a2:6d:80:d1 (Support-8) via eth0
Dec 12 10:50:34 sonic dhcpd: DHCPREQUEST for 192.168.181.140 (192.168.184.11) from f0:4d:a2:6d:80:d1 (Support-8) via eth0
Dec 12 10:50:34 sonic dhcpd: DHCPACK on 192.168.181.140 to f0:4d:a2:6d:80:d1 (Support-8) via eth0
Dec 12 10:50:34 sonic dhcpd: Abandoning IP address 192.168.181.140: declined.
Dec 12 10:50:34 sonic dhcpd: DHCPDECLINE of 192.168.181.140 from f0:4d:a2:6d:80:d1 (Support-8) via eth0: abandoned
Dec 12 10:50:39 sonic dhcpd: DHCPDISCOVER from d4:be:d9:85:31:x1 via eth0
Dec 12 10:50:40 sonic dhcpd: DHCPOFFER on 192.168.181.141 to d4:be:d9:85:31:x1 (testing01) via eth0
Dec 12 10:50:40 sonic dhcpd: DHCPREQUEST for 192.168.181.141 (192.168.184.11) from d4:be:d9:85:31:x1 (testing01) via eth0
Dec 12 10:50:40 sonic dhcpd: DHCPACK on 192.168.181.141 to d4:be:d9:85:31:x1 (testing01) via eth0
Dec 12 10:50:40 sonic dhcpd: Abandoning IP address 192.168.181.141: declined.
Dec 12 10:50:40 sonic dhcpd: DHCPDECLINE of 192.168.181.141 from d4:be:d9:85:31:x1 (testing01) via eth0: abandoned


Please help me to resolve this issue.

A similar issue was solved on Linuxquestions three years ago. The broadcast address was wrongly configured on the DHCP server.

Also, do your Windows clients say anything when they decline the address?

I saw that thread and tried but it doesn't worked for me.

No, windows client doesn't say anything when they decline the address. My Linux client is working fine with same configuration.

From RFC 2131, which describes DHCP:
The RFC encourages DHCP clients to find out, e.g. by an ARP request, if the address they were given by the DHCP server are already in use. Why only the Windows clients have the problem, I can't tell, but perhaps the address ranges configured for them in the DHCP server happen to overlap with other addresses?

To find out what went wrong, then, you may want to

• check if somebody has already the IP address that the DHCP server is offering
• look at the clients' ARP caches (there is an arp command in Windows)
• rething your DHCP address structure

I checked IP address that DHCP is offering is free.

I tried with changing the range also but still no luck.

FYI below is my dhcpd.conf

#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
option subnet-mask 255.255.255.0;
authoritative ;
default-lease-time 14400;
ddns-update-style interim;
ignore client-updates;
ddns-updates off;
subnet 192.168.181.0 netmask 255.255.255.0 {
range 192.168.181.101 192.168.181.150;
option domain-name "XXXXXXX.com";
option domain-search "XXXXXXXX.com";
option domain-name-servers 192.168.181.10, 192.168.143.3 ;
option smtp-server mail.XXXX.com;
option routers 192.168.181.1;
option broadcast-address 192.168.181.255;
option subnet-mask 255.255.255.0;
default-lease-time 14400;
max-lease-time 172800;
next-server 192.168.181.11;
filename "pxelinux.0";
}

Regards,
Yogesh

Do you mean that whatever addresses are offered, the Windows clients keep on rejecting them?

If you can, see what the clients have in their ARP cache. The cache should contain the address they refuse, and the MAC address of the system that (in the client's opinion) has this address. You would have to check very soon after they send their DHCPDECLINE, to minimise cache updates.

I'd say it's a case for a Windows forum

Yes, your Windows machine does "say something, somewhere," and that "somewhere" is its Event Viewer application, probably squirreled-away under Utilities or Administrative Tools. In this respect, all operating systems are the same. They put on a good front for the end-user, but somewhere, they jabber-away incessantly. When the Windows machine declines the offer, it will record the reason why (not). But it will not tell the server, and in fact it has no means to do so.

Hi All,

I found the issue. I connected the OpenSuse 13.1 due to which this issue happen. I am not sure why it is happening but yes this is the cause.

Simply I disconnected the system and the issue resolved. But whenever I am connecting it to the network the issue coming. Can anybody suggest why this is happening? I am very new to OpenSuse. I check the DHCP service on it its not running. Also can you guide me how to set static IP in OpenSuse.


Regards,
Yogesh