XP Security Centre warning

[Biscuit]

I saw a red security centre warning today on a customer's pc. It claimed that Nod32 was out of date, however on checking it was right up to date & had sig file 2201. I "fixed" the red error by turning off the Security centre.

The event log read (UK time format):
{QUOTE-> Time Module Event User
17/03/2006 13:52:44 Kernel The virus signature database has been successfully updated to version 2201 (20070418). <-QUOTE}

This was after an update today (18/04/07)! Both the computer & server are displaying the correct date/time & none of the other 10 workstations are showing the error.

System: SBS2003 Premium & XP Pro workstations running Nod32 2.7 Enterprise, Nod32 RAS & RAC running on the server.

Has anyone else seen this?

[ASpace]

Hi !
If NOD is really updated , then it is simply WMI bug , not an ESET fault . Fix with this:
http://www.wilderssecurity.com/showpost.php?p=893101&postcount=7

;)

[Biscuit]

Thanks, that's a good tweak.

I have a feeling though that this is Nod's fault because of the incorrect date in the event log. I think the security centre just looked at the last update date & threw an alarm...?

[ASpace]

But NOD get the data for its log from the computer ... Check Windows's date again

[Biscuit]

I checked it twice Mr Hi-tech!

Both the computer & server are set to the correct date & time & are in the correct time-zone. ???

[ASpace]

{QUOTE-> I checked it twice Mr Hi-tech! <-QUOTE}
:lurking:

{QUOTE-> Both the computer & server are set to the correct date & time & are in the correct time-zone. ??? <-QUOTE}

If you insist on the fact they are correct , then you can try reinstalling NOD to see how it would act after that . I have never had such problem , if the system date/time is correct , NOD is correct , too . If system date is incorrect , NOD gets them and it is incorrect , too .

[Biscuit]

Thanks for your reply

I don't think the problem looks serious enough to reinstall Nod, I was sort of hoping that someone else had seen the same issue. :blink: