Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 304
  • Last Modified:

W32.Netsky.Q@mm.enc in Microsoft Small Business Server, Exchange Queue Location: How to remove?

I have a Windows Small Business Server 2003 SR2 that has an infection from W32.Netsky.Q@mm.enc virus that has been found by Symantec Antivirus Corporate Edition. The virus can't be deleted is the problem. Antivirus attempts to delete or quarentine the infected file and both fail due to "access is denied".

The virus is in the following location:
C:\Program Files\Exchsrvr\Mailroot\vsi1\Queue\

The infected file is:
C:\Program Files\Exchsrvr\Mailroot\vsi1\Queue\NTFS_c728f24201c8cdf0000024ff.EML

Here's Symantec information about this.

http://www.symantec.com/security_response/writeup.jsp?docid=2004-033015-2404-99&tabid=1

I've followed all the instructions but in rescanning the virus does not later appear. Then a few days later it will appear as a new Symantec virus alert. It's driving me crazy that I can't seem to permanently remove and protect the server from these virus. Why isn't Symantec able to delete this... anyway.

I've also run programs like Spybot but it isn't detected in that version.

Any suggestions on what I can do to remove this virus would be really helpful.



Symantec-Notices.jpg
0
tedjpclark
Asked:
tedjpclark
  • 4
  • 2
1 Solution
 
kieran_bCommented:
Step one, uninstall symantec anti-virus from the exchange server.
Step two, get an exchange aware anti-virus program.
0
 
tedjpclarkAuthor Commented:
What do you recommend I use as an Exchange Aware Anti-Virus?
0
 
kieran_bCommented:
If you must use Symantec, get Symantec Mail Security for Microsoft Exchange - Personally, I think most of their stuff is rubbish, and remove it everywhere i can.  That said, I think any client AV on an exchange server (non-exchange aware) has no place.

Other options are Trend Micro's suite, which I have heard a lot of good things about.

Personally, I don't use AV on Exchange servers at all - I block it at the gateway and at the client.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
tedjpclarkAuthor Commented:
OK Thanks. I'm of like mind with Symantec, but with this server I'm unfortunately picking up what somebody else built. The office I'm supporting believes "we've got AntiVirus, we paid for Symantec", when I initially reviewed things and provided recommendations last fall. Nothing better than eventually being able to say "told you so", of course after I've had to spend hours and hours fixing this server, problem by problem.

So I'm now going through and cleaning this computer up. I'm curious, since it would help me resolve so many potential issues with this system, what do you do specifically to block virus/malware at the gateway and client? Any links or suggested reading would be appreciated. Thanks.
0
 
kieran_bCommented:
On the gateway, I will install something like GFI MailSecurity on/or an application device/server or use only an SPI compliant router which can actually catch it at the router - Sonicwalls do it, FortiGates do it - depending on the site, budget, etc.

On the client, I always use something - personally, I don't use AV, but I think it is irresponsible to expect users to get along with out it.  I have used and like AVG from GRISoft.com, I have heard good reports of McAfee and Trend Micro.
0
 
kieran_bCommented:
I will clarify a bit more about the problem as well;

What is happening is that AV infected emails are coming into your server bound for your users.  Symantec is misconfigured, but any AV app misconfigured on an Exchange server will do the same thing (particularly if it is no Exchange aware) - it is seeing the messages in the queue and trying to clean them.  Now, Exchange is working with them, and Exchange doesn't take crap from AV software, so it just locks the files and Symantec has a teary.

The real problem is, with Symantec doing that, it is only a matter of time before it upsets Exchange so much that it either corrupts messages or worse, the information store (which I have actually seen...)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now