NOD32 v2.50.25: updates at user logon - not working properly for me

Hi peeps. I am currently trialling NOD32 v2.50.25 on a laptop that has wireless networking for internet access. When the laptop boots into Windows XP, the wireless connection takes about 10secs, from the point of the desktop showing, to connect with my router and have a authenticated / active connection. A hard wired PC usually has the network connection straight away as soon as you log into Windows. I think that it is the time lag for the wireless connecting that is causing NOD32 not to update upon login into Windows XP user account. So, I would either have to update manually, or wait until one hour passes when the hourly update is due. In McAfee VirusScan v8.0i Enterprise, there is an option of delaying the update process by user specified time after user logon. I had set one or two minutes for this setting when I was using McAfee. What do you guys think? Is there a quick fix to get around this?

 

Try switching your connection for Nod32 to Dialup, I think that will resolve the issue. Further instructions from post number 64 onwards.

Let us know how you go...

Cheers

 

Thanks Blackspear. I have tried this, and it seems to not help. NOD still justs sits there without updating after booting into Windows and wireless connecting within 10secs. Even if I load up a web page to stimulate internet activity it still doesn't update itself. In the shedule/planner it states that the logon update was last run at a time when I had boot into Windows (when no internet was available), but nothing updated. Any other tricks I can try? In the advanced settings post I see nothing that is relevent to my problem. What I need is something to initiate a update check a few minutes after logon to Windows. Ideally I would like NOD32 to include the function of delaying a sheduled task (after an event trigger), like McAfee VirusScan v8.0i Enterprise does.

 

You could try repairing Winsock

Let us know how you go...

Cheers

 

But my connection isn't broken. This is a new install of Windows XP as well.

 

It doesn't need to be broken, one of the issues fixed by repairing winsock is a slow connection. I have found this many many times, particularly after installing ZoneAlarm.

Cheers

 

OK I have just run WinSockFix 1.2. Will wait later on for next update, as I have just manually updated to latest definitions. I think there's a "slight" improvement in connection time, however I don't think its quick enough to beat NOD in initiating logon update.

 

The Winsock fix didn't help my particular problem, neither will it help the people who set their wireless connectivity to OFF by default when they start their laptops. I may have found a solution though. I have changed the update task to run from "user logon" to "Everytime computer starts", then set it to "run as soon as possible" if this sheduled task could not complete at last sheduled time. Using these settings my laptop has managed to update itself within 3 minutes of booting into Windows. Once last night, then once again this afternoon. Marvellous. NOD32 internet setting is still set at dial up, I'm wondering if I should put that back to LAN/Fixed.

 

You could try that but I am not sure that it will help you or not. I hope you have also setup your NOD32 to the settings mentioned in Blackspear's thread. https://www.wilderssecurity.com/showthread.php?t=37509

 

Good to see, and thanks for letting us know, as it will help someone in the future.

Try it and see how you go...

Cheers