Re: RES: RE: RES: RE: RES: RE: RES: RE: RES: Could not connect to smtp host : 10053

  • From: "Medeiros, Jose" <jmedeiros@xxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 26 May 2005 09:23:39 -0700

Hi Mark, 

I found this article on McAfee's web site:

On a Microsoft Exchange 2000 server running both GroupShield 5.x for Exchange 
2000 and NetShield 4.5 or VirusScan Enterprise 7.0, the following exclusions 
must be added to the NetShield\VirusScan configuration:
---------------------------------------------------
Exclude the following GroupShield directories:
For GroupShield 5.0 for Exchange 2000:

..\Program Files\Network Associates\GroupShield Exchange\i386\qtinewrk 
(the quarantine work directory)

..\Program Files\Network Associates\GroupShield Exchange\i386\qtineext

..\Program Files\Network Associates\GroupShield Exchange\i386\Quarantine 
(QTINE.MDB resides here; exclude for performance reasons)

..\Program Files\Network Associates\GroupShield Exchange\i386\Log 
(LOGFILE.MDB resides here; exclude for performance reasons)

For GroupShield 5.2 for Exchange 2000:

..\Program Files\McAfee\GroupShield Exchange\i386\qtinewrk 
(the quarantine work directory)

..\Program Files\McAfee\GroupShield Exchange\i386\qtineext

..\Program Files\McAfee\GroupShield Exchange\i386\Quarantine 
(QTINE.MDB resides here; exclude for performance reasons)

..\Program Files\McAfee\GroupShield Exchange\i386\Log 
(LOGFILE.MDB resides here; exclude for performance reasons)



Exclude the following Exchange server directories:

NOTE: NetShield\VirusScan may cause performance and other issues with scanning 
of database files and transaction logs.

..\exchsrvr\mdbdata 
(Information Store data)

..\exchsrvr\mtadata 
(Message Transfer Agent data)

..\exchsrvr\mailroot 
(STMP service work directories)

..\exchsrvr\srsdata 
(site replication service data)

..\exchsrvr\ServerName.log\*.log 
(exclude if message tracking is enabled; do not exclude the directory since it 
is shared)

M:\

Regards, 

Jose Medeiros

------------------------------------------------------
-----Original Message-----
From: Medeiros, Jose 
Sent: Wednesday, May 25, 2005 10:12 AM
To: [ExchangeList]
Subject: [exchangelist] Re: RES: RE: RES: RE: RES: RE: RES: RE: RES:
Could not connect to smtp host : 10053


http://www.MSExchange.org/

Hi Mark, 

If I am understanding you correctly, are you using a standard version on McAfee 
Corporate on your Exchange server? You do know that you have to exclude the 
transaction logs and exchange database scanning on most client based antivirus 
programs, including Symantec so that you do not corrupt them.  

Both Symantec, McAfee and Trend Micro have an Exchange anti-virus scanning 
engine designed specifically to scan an Exchange Information Store.

Personally I prefer to have a Mail Gateway server scanning email for Virus's 
before they are delivered to the Exchange system. 
http://www.mirapoint.com/products/razorgate_100.shtml

Postini and Bright Mail also offer hosted solutions that work well for small to 
medium business.

Jose

-----Original Message-----
From: Mark Meelhuysen [mailto:m.meelhuysen@xxxxxx]
Sent: Wednesday, May 25, 2005 9:45 AM
To: [ExchangeList]
Subject: [exchangelist] Re: RES: RE: RES: RE: RES: RE: RES: RE: RES:
Could not connect to smtp host : 10053


http://www.MSExchange.org/

WHAAAAAAAAAAAAHHHH!!!!!!!!!!!!! You never guess what the problem was.. and
so stupid of me that I did not think of it. It means that the problem was
there for a longer time than I thought. It was McAfee v8.01 Enterprise
that was the bottleneck!!! I uninstalled my Symantec Corporate Edition
9.0, and installed McAfee after many people told me that it was much
better than Symantec. What is your opinioun about this?

I thought of it after I found the next article on the web:

http://kbase.pscs.co.uk/index.php?page=index_v2&id=242&c=1

------------------------------------------------------




Other related posts: