BAD_ADDRESS in DHCP Leases W2K3 R2 Server - Wireshark
Posted on 2014-03-18
We are still seeing this issue and are baffled as to how to determine where the issue is actually coming from.
Does anyone know where to set the filters in Wireshark to find where the issue is coming from? The thought was to set the filters in wireshark and clear out the BAD_ADDRESS from the DHCP lease on the DHCP server and do a /release , /renew and determine what is going on.
My skill set with wireshark is unfortunately very limited and would appreciate some expert advise on this.
Thanks in advance for taking the time to respond back, it is greatly appreciated.