Event error log

[DavidCo]

My event log shows many errors of the type
Update Error connecting to server u7.eset.com.

These amount to 200+ per month.
I boot up about 9 times per week.
Nod tries 6 servers each time on boot.
Go figure.

I have a wireless setup (wireless router + PCI wireless cards)
My wireless connection is not instantaneous.
So Nod loads before the connection (wireless) is made and tries to update.

I have not been able to find a way to put a "wait" on the update on startup.
I would like to have my event logs meaningfull.
Any ideas.
Thanks

[NOD32 user]

HI DavidCO,
You may wish to try setting the internet connection to 'other (e.g. portable computer) in IMON --> Setup --> Advanced
You may also wish to un-tick the 'User Logon' update task in the scheduler/planner if the IMON setting isn't enough.

I'd love to hear back if that makes any difference.

Cheers :)

[DavidCo]

NOD32 user
Hi
I do not have IMON --> Setup --> Advanced?
'User Logon' update task is already unticked.
The update I have is the regular (every hour)

Hmm
Why is Nod trying to update on start up???

[NOD32 user]

-{ Quote: "... I do not have IMON --> Setup --> Advanced?..." }-:ouch:
Sorry, my mistake - should have said Update --> Setup --> Advanced :-[

[DavidCo]

I think that the change to 'other' has worked8)
I shut down and re-started and no update attempt showed in the log.

Thank you.
;D

p.s. I do not understand why. Why did it try to update when the user logon was not checked etc and what has happened now (other)
As long as Nod is not compromised.

[NOD32 user]

-{ Quote: "I think that the change to 'other' has worked8)
I shut down and re-started and no update attempt showed in the log.

Thank you.
;D

p.s. I do not understand why. Why did it try to update when the user logon was not checked etc and what has happened now (other)
As long as Nod is not compromised." }-You're welcome :)

Not 100% certain but I beleive that setting changes how NOD32 decides if it should run the update on dial-up connection task.

Cheers :)

[DavidCo]

Drat
This morning all is back to update on start up.
Must be something to do with 'every 24hrs'
Thanks for trying.

I am on 8Mb BB

My log showed that over the period 25/7 to 28/8 there were 293 errors of the type stated.
This makes the log almost useless. I may turn it off.

[NOD32 user]

I guess that would be a bit frustrating then - 12+ error entries per hour.
It is normal to have some entries anyway as the update servers deflect or for load balancing etc. or as different parts of the internet do their thing, which is something outside any of our control.
But the important things are that you do get the updates when they're available and that you are able to diagnose a problem if there is one.

Maybe you could leave the logs on and only refer to them if you have an issue? - You can tell usually if you're getting updates by the date code of the update signature ;)

Cheers :)

[DavidCo]

12+ error entries per hour.
:o
With approx 720 hours in a month that would give, err - lots.
No, it's just that firing up once a day and Nod trying to check 6 servers gives 30 (days) x 6 = 180 errors.

But you are right I do get the updates (sometimes the same one twice)
I did download the latest and uninstall/re-install just in case.

I had dumped the log (out of curiosity) into NotePad++ and extracted 'like blocks' and what I saw made me post.
;D

[NOD32 user]

-{ Quote: "12+ error entries per hour.
:o
With approx 720 hours in a month that would give, err - lots.
No, it's just that firing up once a day and Nod trying to check 6 servers gives 30 (days) x 6 = 180 errors." }-lol - don't know what I was thinking ???
It was only about 8 entries per day.
-{ Quote: "But you are right I do get the updates (sometimes the same one twice)
I did download the latest and uninstall/re-install just in case.

I had dumped the log (out of curiosity) into NotePad++ and extracted 'like blocks' and what I saw made me post.
;D" }-Glad you asked.

Cheers :)