The SMTP service does not come online on the node that is running Exchange Server 2003 after a failover in a cluster environment

After a failover in a cluster environment, the SMTP service does not come online on the node that is running Microsoft Exchange Server 2003.

When you use Event Viewer to view the Application log on the computer that is running Exchange Server 2003, you see an event that resembles the following:

Event ID : 1005
Record Nr. : 1867
Category : None
Source : MSExchangeCluster
Type : Error
Generated : DateTime
Machine : Computer_Name
Message : SMTP Virtual Server Instance 1 (EVS1): The IsAlive check for this resource failed. For more information, click http://www.microsoft.com/contentredirect.asp. Data: 45 27 00 00

This issue may occur if the following conditions are true:

�	McAfee Virus Scan version 8.0.0.251 from McAfee Inc. is installed on both nodes in the cluster.
�	The McAfee Access Protection settings are managed from a configuration server.

In this scenario, the passive node may have lost contact with the configuration server if the passive node has been offline for some time. If the passive node has lost contact with the configuration server, McAfee Virus Scan on the passive node reverts to the default settings.

By default, McAfee Access Protection blocks TCP port 25 to prevent mass mailer worms. The SMTP service cannot run if TCP port 25 is blocked.

To resolve this problem, turn off the Prevent Mass Mailing Worms from Sending Mail feature in McAfee Virus Scan. Do this on both nodes that are running Exchange Server 2003 in the cluster environment. For more information about how to turn off the Prevent Mass Mailing Worms from Sending Mail feature in McAfee Virus Scan, view the documentation that is provided with McAfee Virus Scan, or contact McAfee.

For information about how to contact McAfee, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

The information and the solution in this document represents the current view of Microsoft Corporation on these issues as of the date of publication. This solution is available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe. There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft. Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider.

Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information. In no event will Microsoft be liable for any third-party solution that this article mentions.