Hi to all, in my company we have ADNM and 380 licenses, and suddenly avast started removing our Remote Administrator Server 3.0 installations throughout all the clients/servers because it recognizes it as a trojan.
The old installations that still use Radmin Server 2.2 ARE NOT affected, and neither the Radmin Viewer 3.0 is affected.
Obviously it is not, so I’m asking here to have Radmin Server 3.0 removed from the list of trojans in the next definition updates.
Please let me know as soon as the problem is corrected.
Hi, I’m unable to upload the file to the ftp server you provided.
It keeps telling me I’m not allowed to upload files.
I tried to upload in the root “/” , into “/pub” and into “incoming”.
Into “/incoming” it seems to upload ok but then at the end the file disappears.
I tried with the .exe file and also by zipping it with password (to avoid content filtering).
I tried through proxy and directly through a machine with direct connectivity to internet.
Also having this problem. I have temporarily disabled the scanning of c:\windows\system32\rserver30*. Would appreciate a solution asap. The file has been uploaded to te incoming folder of your FTP site.
How did you manage to upload the file???
Which ftp client did you use? To me it keeps disappearing, I even tried here at home but nothing changes, the file disappears after the transfer.
By the way, the uploaded files are two: rserver3.exe and rserver3.zip (zipped with “avast” password).
There is write only access to this folder, so after upload you’ll not see uploaded file - we’ve received all radmin3.exe and radmin3.zip files, however avast! is not detecting any of those files as trojan-gen.
Ah, I see, it is a write-only folder!
Well, the important thing is that you did receive the files.
I’ve noticed that now , with the 080125-3 (dated 25-01-2008)definitions it doesn’t recognize the files any longer as trojans.
The version that wrongly identified the files as trojans was the 23-01-2008 definition (I don’t remember the number, maybe it was the 080125-2 but I’m not sure).
Funny! The problem has now gone away. I removed the exclusion from RSERVER3.EXE expecting it to fail and bobs your uncle it ran OK! I guess the new definition fixed the problem.