Business Edition on laptops

Hi,

we have NOD32 v3 business edition installed on a number of laptops and they are configured to update from our server.

Recently a user was on holidays and his laptop kept sending email alerts that NOD32 could not contact the server for updates.

So what I'd like to know is, can we configure nod32 to try local server first then fall back to eset's servers?

Also, we expected nod32 to fail when attempting to email alerts since we've configured it to connect to our internal smtp server and its FQDN would not resolve outside. Yet NOD32 was able to send us alerts. Is it falling back to MX records for the email domain and can we stop that?

Thanks
Vic.

 

yes,
configure a profile that updates from local servers then a second profile that updates from eset's servers.
when you schedule an update job you can set a default profile and a secondary/backup/fallback/etc profile.

 

how to create dual profile...

 

thanks for the link nonoise.

I created a new configuration and like the kb article suggested, setup the primary to be our LAN server profile and the secondary direct to the internet.

I manually run the scheduled task and at first a pop up appeared saying that it couldnt find server but when I checked the update screen it was downloading the latest updates.

Went back to my desk and found an error message in my inbox:

During execution of Update on the computer XXXX, the following warning occurred: Server not found.

 

One approach is to create a different config file for laptop users...so that they update from Esets public servers.

I also open/forward the management ports on the firewall..pointing to the LAN IP of the RAS/RAC server. And set the laptop client management to go to that external dns alias or IP address.

Another method I often do, is open/foward the ports for the LAN mirror update...to the LAN IP address of the server. Laptops have a config file set to get updates from the external dns alias. So they still get their updates from the main networks update server regardless of if they're inside or out. I do this for clients that have faster bandwidth connections obviously...not a good idea of the upload of the main networks is wee slow.

 

Make sure you use the authenication methods (NTLM authentication on mirror, password on RAS) so you don't accidentally start serving updates to the warez community off a publically exposed RAS.

 

And custom ports of course..I don't have a single one on the default 8081.