Joe: this one appears to be very hard to eradicate other than wiping the hard drive. Affects security s/w from even booting, just hanging up the machine. ESET has a file that is supposed to fix it, but believe me, it does not. Went to the malware center and didn't see it posted. Are you aware of: Win32/IRCBot.ANR?
Does Prevx see it when you do a scan? If not I think it would be best to have a Prevx engineer analyze your PC remotely to correct this issue as they guarantee clean up. http://info.prevx.com/service.asp TH
NO TH, nothing was caught. Dunno if it was missed or not, thus the post. I won a 2 computer, 2 year license during their annual sweepstakes for NOD32 ver 4. Been running ESS for almost two years and tried to install NOD Sunday. It went in ok, but after the very first reboot, both computers just hung up. ESETs site says "this is probably the problem". ONLY happens right after install of NOD. Glad I had a couple of images to restore to get my back operating. Waiting for their support to get back w/me, but thought I ask here also.
Are you running ESS & EAV at the same time? Not sure what you mean by installing Nod32. Upgrading versions tends to cause problems with Eset. best to uninstall Eset, then (if Vista/W7) delete the Eset directory in "\program data", reboot, then install Eset. For the rootkit check, run a full scan with Malwarebytes & then Prevx.
No, am not running both at the same time. Uninstalled ESS using their uninstall tool, then installed NOD. Their uninstall tool takes it all out and have done ESS upgrades every time one has been available, no problem. I would suspect something else if it wasn't for the fact that both computers are doing the same thing and that was the ONLY change in the two. Full scan w/Prevx, MB, SuperAntispyware, and IS360, nothing found. Problem is, after installation of NOD and on the very FIRST boot, it hangs and computer is inoperable.
And there lays the problem, I know. BUT...as stated in previous post, it only occurs when trying to execute NOD and computer hangs.
'fraid not A router (NAT) will stop incoming that has not been requested/initiated from the 'inside' so to speak. However malware that has got in can initiate a call.
After giving that some thought, power cycled the modem/router. My laptop is in the den, desktop is in the back of the house. Laptop is hard wired to the router, so thought that may be the problem. After recycling and disconnecting the internet cable from laptop to desktop, tried again. No joy.
It doesn't sound like the router, but having said that a power recycle will not 'clean' router software, just flushes the cache etc in case of a 'stale session'. A hard reset back to factory settings might. Have a copy of your current router setup saved somewhere! There is malware that targets Linux based routers and modifies the s/w. It sounds like Eset to me - ducks quickly.
David, take a look at this thread, my last post for a boot comparison. The looping is very apparent, but don't know the fix, if there is one. https://www.wilderssecurity.com/showthread.php?t=266029
I have 3 unused Eset licences (til Sept 2010) for that and similar issues. I do remember someone finding/posting a change to boot sequence of an Eset driver?
Have a ticket w/ESET and think the mod of the forum will forward the boot pics comparisons to the powers that be. Feel like they would know what to do about correcting the problem. If you hear of something that works, please let me know.
