Solved

Exchange 5 "Host not found" error

Posted on 1998-04-16
5
182 Views
Last Modified: 2013-12-23
I'm using Exchange Server 5 (w/ SP2) on NT 4.0. Sometimes users cannot send messages  and get an " Host
Unknown" error. We run our Primary DNS (NT's DNS Manager), Exchange and NT on the same server. We have tested the DNS server which did not give any errors.

> > -----Original Message-----
> > From:      System Administrator
> > Sent:      Wednesday, March 25, 1998 4:45 PM
> > To:      Dan Goldberg; Ed Dougherty
> > Subject:      Undeliverable: RE: BOM Items Issue-4
> >
> > Your message did not reach some or all of the intended recipients.
> >
> >       Subject:      RE: BOM Items Issue-4
> >       Sent:      3/25/98 4:45 PM
> >
> > The following recipient(s) could not be reached:
> >
> >       Dan Goldberg on 3/25/98 4:45 PM
> >             The recipient name is not recognized
> >             MSEXCH:IMS:kinergy pte ltd:KINERGY:S1 3902 (000B0981) Host
> > Unknown
> >
> >       Ed Dougherty on 3/25/98 4:45 PM
> >             The recipient name is not recognized
> >             MSEXCH:IMS:kinergy pte ltd:KINERGY:S1 3902 (000B0981) Host
> > Unknown
> >

0
Comment
Question by:chewfh
  • 4
5 Comments
 
LVL 3

Accepted Solution

by:
mpopal earned 100 total points
ID: 1571832
The error that your getting from the Non Delivery Report is due to either the domain name for the recipient is not correct or the recipient does not exist on that domain's mail server.
The Internet has "Global" Domain Name Servers that resolve Domain Names to systems. If this domain name is not found, it cannot be routed any further.
An NDR on a message with the correct domain name but the incorrect user name looks like the following:


   Your message did not reach some or all of the intended recipients.

      To: 'hello@cibc.ca'
      Subject: test
      Sent: 3/27/97 11:21:30 AM

   The following recipient(s) could not be reached:

      hello@cibc.ca on 3/27/97 11:21:30 AM
            Recipient Not Found
            MSEXCH:IMC:CIBC:SCCB:NT70177PDC

This error is a "Recipient Not Found" error. The mail got to the other system, but the username (Hello, in this example) did not exist. This error is again most likely due to a sender's addressing error. Check the address again, and resend.

You can also read the article at knowledge base. Navigate to http://support.microsoft.com/support/kb/articles/q168/5/57.asp.

Good luck.
0
 

Author Comment

by:chewfh
ID: 1571833
The domain name for the recipient IS correct an the recipient DOES exist on that domain's mail server. The sender has been using the same e-mail addresses all along. When I use NSLOOKUP to check the destination server, it is working fine. The DNS Manager on our NT server is also set up by a Microsoft SOlution Provider. Could it be the address book's use of 'Display Name' is having a problem?
0
 

Author Comment

by:chewfh
ID: 1571834
The domain name for the recipient IS correct an the recipient DOES exist on that domain's mail server. The sender has been using the same e-mail addresses all along. When I use NSLOOKUP to check the destination server, it is working fine. The DNS Manager on our NT server is also set up by a Microsoft SOlution Provider. Could it be the address book's use of 'Display Name' is having a problem?
0
 

Author Comment

by:chewfh
ID: 1571835
The domain name for the recipient IS correct an the recipient DOES exist on that domain's mail server. The sender has been using the same e-mail addresses all along. When I use NSLOOKUP to check the destination server, it is working fine. The DNS Manager on our NT server is also set up by a Microsoft SOlution Provider. Could it be the address book's use of 'Display Name' is having a problem?
0
 

Author Comment

by:chewfh
ID: 1571836
The domain name for the recipient IS correct an the recipient DOES exist on that domain's mail server. The sender has been using the same e-mail addresses all along. When I use NSLOOKUP to check the destination server, it is working fine. The DNS Manager on our NT server is also set up by a Microsoft SOlution Provider. Could it be the address book's use of 'Display Name' is having a problem?
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Nslookup is a command line driven utility supplied as part of most Windows operating systems that can reveal information related to domain names and the Internet Protocol (IP) addresses associated with them. In simple terms, it is a tool that can …
This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

807 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question