Scheduler: The Automatic update after dial-up connection doesn´t work.

The Automatic update after dial-up connection doesn´t work.



After I start the Computer he shows under Update:

Virus signature database update failed.


Then after I start the dial-up connection the Automatic update does not start.


I use ESET NOD32 Antivirus 5.0.93.18 on Windows XP Professional (SP3)

 

It fully depends on the oper. system how it notifies about established connections. It may also depend on the type of the Internet connection you use.

 

Greetings,

Windows XP Pro, SP3.

I have the same problem with the complete inability to update the definitions on establishing a dial-up connection. I get the impression that NOD32 v5 attempts to update before the dial-up connection is fully established, although I have no hard observational data to support that conclusion.

However, the update on dial-up connection worked perfectly on NOD32 v4 and earlier versions. Thus based upon the statement by Marcos quoted above, what has fundamentally changed with the new release that accounts for this problem?

Best regards,
RL

 

I'm using NOD32 5.0.94.0 with Win2k Pro and the scheduler doesn't launch the update after dial-up connection either; it was working fine before updating from v4 to v5.

Is there a way for NOD32 v5 to detect dial-up connections again? A command line parameter for launching updates from a batch file would be helpful.

 

The Automatic update after dial-up connetion in Ver. 5.0.95.0 dosen´t work.

Marcos - When will there be a working version.


In my opinion Ver. 5 do not detect dial-up connections, what worked well in version 4.

Why did ESET change something that works well?

 

ESET V5 5.94 still behaves like a BETA version

 

Then I suggest that you report this "beta behavior" to ESET so they can fix it