Event ID - 1705

Event Id1705
DescriptionAn unexpected error is forcing EXPS to close the SMTP connection to "%1". "%2" called "%3" which failed with error code %4 ( %5@%6 ).
Event Information"According To Microsoft:
This Error event indicates that Microsoft® Exchange Server is closing an X-EXPS connection to another server in the Exchange Server organization. The X-EXPS command is a command that Exchange uses to implements SMTP server-to-server authentication.
The following are some common causes of this event:

1. Exchange is trying to connect to a remote server that advertises X-EXPS. However, the connection cannot be made because a valid FQDN is not provided. A valid FQDN may be required if you are using a third-party application that must use a Host file. See User Action.

2. An Exchange server is trying to connect to another Exchange server in the same organization that is not configured to enable relay between servers.

To resolve this event, do one or more of the following:

1. If the remote server requires a valid FQDN, check to see whether the Host file is configured to resolve the NetBIOS name of the server to an IP address. If that is the way the Host file is configured, configure the Host file to resolve the FQDN to an IP address.

2. If Exchange is trying to connect to another Exchange server in the same organization that is not configured to enable relay between servers, do the following:
a. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
b. In System Manager, click Servers, click <Exchange server name>, click Protocols, and then click SMTP.
c. Right-click Default Virtual SMTP Server, and then click Properties.
d. On the Access tab, click Relay.
d. Make sure that the Allow all computers which successfully authenticate to relay, regardless of the list above check box is selected.

3. In Event Viewer, examine the Application log for related events that are logged before of after this event message to determine. These related events may provide additional information about the cause for why the se
Reference LinksMicrosoft product: Exchange Version: 6.5.7596.0 Event Source: MSExchangeTransport Event ID: 1705

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.