Networks

Ask something
Discussion Locked

Exchange MTA problem

0 helpful
3 replies

by tenceladmin

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an Exchange server whose MTA queue will backup about every 7 - 10 days. It is Exchange 5.5 SP4 on WinNT4 SP6a. The connector is an x.400 over a 56k frame relay to a bridgehead that is the same configuration. The bridgehead and the remote server get event IDs 289 (a connection with the remote exchange server could not be opened) and IDs 1293/1290 (a remote/local initiated association to the other server was refused with failure reason prider 0 and the reason was 0). This will go on for nearly the whole day that it happens, and will eventually start working again towards the end of the day. I have already ruled out network connectivity and bandwidth issues, and I have modified the MTA overrides according to MS TechNet with no success. I added a backup x.400 connector with a higher cost to another server, and now when it happens the queues will get stuck and swap between the two connectors. This is getting very frustrating. Any suggestions?

3 replies

by mostakim

As per my field experience you can install a WINS server service and it will work fine, I found this from field, your Exchange will need help from WINS this is the true.
SattaR

by tenceladmin

I already have WINS and DNS servers (with WINS to DNS translation) on both sites and they have static entries for each Exhange server. I also have lmhosts files on each server with entries for the Exchange servers in the orgainzation.

by maxwell edison

This behavior can occur when the data in the Remote Server Name box in the Dynamic RAS Connector dialog box differs from the data in the Local MTA Name box in the Message Transfer Agent property page. Note that data is case sensitive, and in this instance, the remote server name in the Dynamic RAS Connector dialog box was typed using a different case than in the Message Transfer Agent Properties dialog box.
To resolve this issue, confirm that the name of the server in the Remote Server Name box in the Dynamic RAS Connector Properties dialog box is identical to the name found in the Local MTA Name box in the remote Message Transfer Agent Properties dialog box.

If you find a discrepancy, type the name in the Remote Server Name box exactly as it appears in the Local MTA Name box, and then stop and restart the MTA.

Good luck,

Maxwell

This discussion is closed to new replies.