My company has had a few problems with our Avast deployment, but never this one. Every user has the same Avast NetClient (currently 4.8.1005), but I’ve found that a new employee who works remotely from another city is a) not discoverable through a “Discover Computers on the Network” task, and b) is not communicating with the ADNM. For this reason, his Avast license has expired. I found another post that suggested changing the name of the Avast server from the computer name to the IP address, and we’re in the process of trying that. (With the security on the laptop, it’s difficult for me to manually delete/overwrite files remotely.) Some other details:
- His OS is WinXP SP2, the server is running Windows Server 2003 with ADNM 4.8.941.
- He’s connecting to the VPN server on the same box using the standard Windows VPN client.
- He can access the server for everything else (file sharing, email, etc.) and can also load the URL http://:5033/$$status$$_mirror .
- Another remote user who just started today, seemingly with the same settings, does not appear to have this problem.
If the server name trick fails, are there other suggestions? Changing the server name might help him contact us, but shouldn’t affect a Discovery task…
Thanks,
Todd