DHCP Server Monitoring Issue

[hsmith]

yes, you are right we are using windows 2008r2 std base dhcp server.

If you could post those logs, or search through them for some indication of what's going on that would help immensely.

Thank you.

[hsmith]

yes, you are right we are using windows 2008r2 std base dhcp server.

If you could post those logs, or search through them for some indication of what's going on that would help immensely.

Thank you.

Also, I've found that if you add the -i <IP ADDRESS OF DHCP SERVER> sometimes that makes this plugin behave better. I am not sure why, but you can try that.

[shailu2014]

I tried to run script with ./check_dhcp -i but got error which mentioned below ( I run this script in root)

./check_dhcp -i 192.168.0.4
Error: Could not bind socket to interface 192.168.0.4. Check your privileges...

sending the dhcp yesterday & today logs (attached).

Thanks & Appreciation in Advance.

[Box293]

These just seem to be an explanation of the Microsoft DHCP sever logs, not the actual logs.

[shailu2014]

Sending the logs again. (attached)

[jdalrymple]

Watch the network:

Code: Select all

[root@jrd-cent66-2 localhost]# tcpdump -i eth0 port 68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:03:44.207501 IP 10.0.2.70.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0c:29:f3:24:9e (oui Unknown), length 548
14:03:44.207850 IP 10.0.2.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300

Code: Select all

[root@localhost libexec]# ./check_dhcp -v
DHCP socket: 3
Hardware address: 00:0c:29:f3:24:9e
DHCPDISCOVER to 255.255.255.255 port 67
DHCPDISCOVER XID: 907300795 (0x36144FBB)
DHCDISCOVER ciaddr:  0.0.0.0
DHCDISCOVER yiaddr:  0.0.0.0
DHCDISCOVER siaddr:  0.0.0.0
DHCDISCOVER giaddr:  0.0.0.0
send_dhcp_packet result: 548




recv_result_1: 300
recv_result_2: 300
receive_dhcp_packet() result: 300
receive_dhcp_packet() source: 10.0.2.1
Result=OK
DHCPOFFER from IP address 10.0.2.1 via 10.0.2.1
DHCPOFFER XID: 907300795 (0x36144FBB)
DHCPOFFER chaddr: 000C29F3249E
DHCPOFFER ciaddr: 0.0.0.0
DHCPOFFER yiaddr: 10.0.2.75
DHCPOFFER siaddr: 0.0.0.0
DHCPOFFER giaddr: 0.0.0.0
Option: 53 (0x01)
Option: 54 (0x04)
Option: 51 (0x04)
Option: 1 (0x04)
Option: 3 (0x04)
Option: 6 (0x08)
Option: 15 (0x09)
Lease Time: 43200 seconds
Renewal Time: 0 seconds
Rebinding Time: 0 seconds
Added offer from server @ 10.0.2.1 of IP address 10.0.2.75


No (more) data received (nfound: 0)
Result=ERROR
Total responses seen on the wire: 1
Valid responses for this machine: 1
OK: Received 1 DHCPOFFER(s), max lease time = 43200 sec.

That's a working example. What does yours look like - particularly the tcpdump part?

9 times out of 10 this is a firewall issue. You shouldn't have to specify ANY arguments if you're on the same network segment.