If you want to point your v2 clients at your RA 2.0.x mirror, you will need to also point them at the "nod32v2" folder in the update path. If you don't, your clients will continue to update - and tell you they are updating successfully, even though they're not actually downloading the latest virus definitions! In my opinion this is a bug, and potentially a security issue if gone un-noticed. So, for example, if you're running your mirror as a HTTP server, on port 8090 (default), then your v2 client update path will be: http://<mirror_server>:8090/nod32v2/
Thanks for the info. I'm trying to setup a 3.0 and 2.7 update mirror in a Windows 2003 server with 2.7 client, is it possible?
Sure . It is possible. 1-st option Install NOD32 2.7 Standart edition on the server . Install ESET RAS and RAC v2. Configure ERA v2's Mirror for both v3 and v2 clients . 2-nd option Install NOD32 2.7 LanUpdate edition on the server . Install ESET RAS and RAC v2 . Configure NOD32 2.7 LanUpd 's Mirror so that it covers v2 users . Configure ERA v2's Mirror to handle the v3 users updates
I have many ideas . However , there are really many possible reasons - your clients' settings , your ERAS settings , your firewall settings , network temporary disability , etc. Read the help file(s) and double-check each and every setting