Question about DHCPLOC and our servers


hello, studying 70-291 cert exam , started playing around dhcploc.  have attached screenshot of portion of recorded.  aware .153 dhcp server, not rogue.  didn't out in server because testing things @ time.  anyway, noticed lot of ack (ip)0.0.0.0 in our logs , curious going on causes them appear.  also, if simple request/offer/acknowledgement procedure, why have have same ip address being acknowledged repeatedly.  1.149 best example of this.  there issue should when see ip hitting server repeatedly?  aware of each of these users are, , confident don't have rogue programs running.  our servers not setup , desperately need cleaned up.  i'm hoping can learn through , maybe clean process.

later in same log, started getting nack 0.0.0.0 also.    if give me quick pointers, i'd appreciate it, of resources have found have not yet addressed these questions.  have told me should see/should expect, don't cover out of normal...  thank in advance.

hi,

thank post.

why have the same ip address being acknowledged repeatedly.
client (like 1.149) ack dhcp packets when both obtain new dhcp lease , renew dhcp lease, please read dhcp architecture article.
0.0.0.0 ip, if specify dhcp server ip when running dhcploc, not show 0.0.0.0 ip record.(that mean it's local host , no need care.)

is there issue should when see ip hitting server repeatedly?
the dhcploc tool detects unauthorized dhcp server. if want know dhcp packets details(mac address/application), please use network monitor tool  to analyze network packets. 

if there more inquiries on issue, please feel free let know.

regards


rick tan

technet community support



Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS