@CoolAcid -
That's the method we have been using to track down the infected host. It's pretty work-intensive since our network is physically very spread out, but it gets the job done, eventually.
I've been tracking a similar issue at the University I work for. We could not find any obvious infection with hijackThis, malware scans, or our other usual tools.
I started up Aport and saw that a system process was listening on port 67, and generating the fraudulent DHCP responses. After...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.