• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1677
  • Last Modified:

Exchange 2003 Event ID: 4000 MSExchange Transport Error. Destination server does not exist.

I have an Exchange 2003 Server running on Windows Server 2003.  Both are Enterprise Edition.  Exchange is SP2 and 2003 is SP1.  I have 3 servers at remote locations that are part of the administrative group.  I have mail sitting in the queues for 2 of the 3 remote servers.  We will call the three servers Remote1, Remote2 and Remote3.  I verified I can send mail to Remote3.  Mail is stuck in the queues of Remote1 and Remote2 on the  bridgehead server which I will call Server1.  I tried forcing the connection of the queues and it does not work.  I am getting Event ID: 4000 Source:  MSExchange Transport Category:  Connection Manager.  Message Delivery to the remote domain "mydomain.com" failed for the following reason:  Destination server does not exist.  I can ping both servers Remote1 and Remote2.  NSLOOKUP is correct for forward and reverse lookup resolution.  I tried RPCPing and it was successful.  I enabled diagnostic logging and Event ID: 4000 is the only error I receive.  I have seen this before and I am pretty sure if I reboot it would fix it but I would like to know if there is another fix and I can't reboot until 8 hours from now.  DCDIag and Netdiag both passed without any failures.  

Any help would be appreciated.
0
SOCCSUPPORT
Asked:
SOCCSUPPORT
1 Solution
 
ksharma4Commented:
Are you running PIX Software?

Are you getting NDR 5.5.0?

Thnx
0
 
SOCCSUPPORTAuthor Commented:
We are not running PIX Software.  We are not getting NDR 5.5.0.  None of the users are getting NDR messages.
0
 
LeeDerbyshireCommented:
Anything to do with this?:

http://www.eventid.net/display.asp?eventid=4000&eventno=2172&source=MSExchangeTransport&phase=1

I think it's suggesting that Remote1 and Remote2 have the 'perform reverse DNS lookup' enabled on the Default SMTP Virtual Server (Delivery tab/Advanced button), but you have no RDNS configured for your domain.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
SOCCSUPPORTAuthor Commented:
I checked and I do not have 'perform reverse DNS lookup' enabled on default SMTP Virtual Server.  I checked eventid.net's web site earlier today and it did not help.  

0
 
LeeDerbyshireCommented:
Can you telnet to Remote1 or Remote2 on port 25 and successfully send a test message?
0
 
SOCCSUPPORTAuthor Commented:
I could not from my workstation but I think that is due to FW settings.  I do have the problem resolved.  I had to reboot the computer.  I could not spend any more time TS the problem.  I am uneasy about this becasue I know it will probably reappear at some point.  
0
 
LeeDerbyshireCommented:
Ah well, sometimes a reboot fixes something that just can't be explained.  It would have been a good test to do the telnet from the server itself (since that is what is trying to connect).  Let's see if it continues to work okay.
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0
 
SOCCSUPPORTAuthor Commented:
I would like to post a follow up on this one.  This error came back yesterday.  I was able to telnet and send an SMTP message from Remote 2 to Server 1.  I could not SMTP a message from Server 1 to Remote 2.  THe messae would sit in the QUEUE for Remote 2 on Server 1 which is my Bridgehead server.  I used NSLOOKUP to resolve the names of Remote 2 and Server 1 using forward and reverse lookups and they were successful.  I did not think it was a DNS problem.  At a loss and coming this close to calling Microsoft a co-worker recommended I create a local host file on Server 1 with the DC and Exchange server for Remote 2.  I put in the IP and host name, performed a IPCONFIG /FLUSHNDS and it did not work.  I then added the IP and the FQDN of the DC and Remote 2, performed a IPCONFIG /FLUSHDNS and it worked.  I was a bit shocked.  Everything in DNS looked sound but I guess I have a DNS problem after all.
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now