none
Unable to send mail using outlook and OWA in exchange 2003 RRS feed

  • Question

  • Hi,

    We are unable to send mail to one of our remote site hosted on a child domain.

    Can send mail from telnet but unable to do so using outlook or OWA.

    I receive NDR 4.4.7 in outlook. DNS reverse lookup is fine.

    The exchange 2003 server is also an additional DC in this site.

    Regards

    Syed

    Monday, June 24, 2013 8:25 AM

Answers

  • Looks like its DNS issue. When I checked the queue the name of the queue of the server in question is just the name of the server and not FQDN.

    Whereas all the other queues for other exchnage servers in differnet sites is FQDN.

    When I do nslookup with the server name it does not resolve. When I added in TCP/IP settings the DNS suffix childdomain.parentdomain in the 

    DNS advanced settings in "Append these DNS suffixes(in order) I was able to send e-mail. I had to do these on all the exchange servers which needs to send mail to this server. Ofcourse this is just a workaround , looking for a correct solution.

    I appreciate your help.


    sa

    • Marked as answer by SAzzam Tuesday, July 9, 2013 5:56 AM
    Tuesday, July 9, 2013 5:56 AM

All replies

  • What is the exact error that you receive in NDR? Did you try to look in queue viewer?

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

    Sunday, July 7, 2013 8:29 PM
  • Thank you for responding.

    In outlook 2010 I get the following NDR:

    Your message did not reach some or all of the intended receipients. Could not deliver the message in the time limit specifed. Pl retry or contact administrator. <domain name #4.4.7>

    In queue viewer the message is still in retry state, i tried to force connection but did'nt help. In more information her it says" Destination server does not exist"

    This exchnage server is also a secondary DC and DNS server.

    Regards

    Syed


    sa

    Monday, July 8, 2013 5:26 AM
  • This is most likely a DNS issue. On the connector properties, can you try to manually assign DNS server addresses?

    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

    Monday, July 8, 2013 8:19 AM
  • Looks like its DNS issue. When I checked the queue the name of the queue of the server in question is just the name of the server and not FQDN.

    Whereas all the other queues for other exchnage servers in differnet sites is FQDN.

    When I do nslookup with the server name it does not resolve. When I added in TCP/IP settings the DNS suffix childdomain.parentdomain in the 

    DNS advanced settings in "Append these DNS suffixes(in order) I was able to send e-mail. I had to do these on all the exchange servers which needs to send mail to this server. Ofcourse this is just a workaround , looking for a correct solution.

    I appreciate your help.


    sa

    • Marked as answer by SAzzam Tuesday, July 9, 2013 5:56 AM
    Tuesday, July 9, 2013 5:56 AM