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.