Hi NickGolovko,

The ZA is 6.5.737.000. The truth of the matter is that there was a conflict between that ZA version and the Torpark browser I was using at that moment. Why I cannot imagine but after using Torpark for a while the ZA client closes down and must be restored through reboot, very irritating behaviour of ZA. After that experience I have given up on that Torpark version (checked the checksum on downloading, but there are more experiencing strange ZA client behavior using Torpark and ZA at the same time. (Some had to install ZA anew after downloading Torpark). Then I had the Nmap null alert from the av. Why ZA conflicts with the Torpark (firefox with tor-router browser)?

polonus