MTA IS GROWING UP & UP

You have a corrupted WINS database. Removing corruption is difficult, so when this happens on our WAN we simply delete the WINS databases and let them recreate themselves. I don't know how your network is set up, but we have a primary and secondary WINS server. From the primary WINS server (which is local to us), we stop the WINS server service on the secondary WINS server (if you stop the local WINS server first, you won't be able to find the second WINS server). We then delete \\winnt\system32\wins\wins.mdb from the secondary WINS server. Then we stop the primary WINS server service and delete wins.mdb from that server. We then restart the WINS server on the primary server, and then on the secondary server. If you are going to go this route, do it off-hours because you will have browsing problems until WINS rebuilds.

There are several factors that can cause this. One easy fix is to put the IP address in the x400 connector property "Stack" tab. Exchange relies heavily on DNS for name resolution. Are you using internal DNS servers? If you are you may want to make sure there are static entries in the DNS table. Or if you already have the IP address in the stack tab, change it to a fully qualified domain name. This helped our queue problem. WINS did not cause this problem.

3 things may be happening.

1.- Links are down! or slow
2.- Set manulally the PORT to send and receive in the mta properties (on both). Do not ask my why, but fixing the port number, resolves many comms isuues.
3.- DNS or LMHOST files corrupted.Use nslookup.exe in order to debug the correct name resolution.

Good luck

This question was auto closed due to inactivity