After reading your post I went in and looked at my server, and the [expletive deleted] McAfee Autoupdater hadn't successfully processed an update since the 19th when it pulled 4286. That meant that we were on 4286 DATs and not the current 4288. I forced an update manually, and it pulled these new definitions just fine, but I have two days worth of failed updates in the activity logs that just give me a sick feeling in the pit of my stomach. I am <finally> seeing both scanners picking it up.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bill Newberg Sent: Wednesday, 20 August 2003 6:55 PM To: [EMAIL PROTECTED] Subject: [Declude.Virus] McAfee Enterprise 7.0 not picking up Sobig.F I use two scanners, F-Prot and McAfee Enterprise 7.0. F-Prot is picking up Sobig.F, but McAfee is not. I have the latest definitions, 4288, and the latest engine 4.2.60. When I send the test eicar file as a zip, both scanners detect it, so I know both scanners are functioning. Does anyone have any ideas as to why my McAfee is not detecting Sobig.F? Bill --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
