Exchange Server 2003 – Inbound Mail Issue

15 pts.
Tags:
Exchange security
Microsoft Exchange
I am running Exchange Server 2003 on a MS 2003 Server SP1. Today all of a sudden we stop receiving inbound mail it just stop. I have checked everything no error messages. I can ping via the IP address of the mail server but not via domain name this is true also with our website. When trying to access OWA I can only gain access if I place the external IP of the server but not the domain name. I tried sending an email from the outside, after a few hours I received a 451 error indicating "Name Server Timeout" Please help...mail has been down since this morning and I cannot figure out why...
ASKED: January 30, 2006  2:59 PM
UPDATED: January 31, 2006  9:04 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello

Try telnet ip 25 and telnet domain_name 25. If you can establish conection by ip and not domain name you have a problem in resolutaion name.

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Lirria
    You might also want to try and do a dns lookup from who ever host's your dns and make sure it's pointing correctly for your mail server - sounds like something is broken so it's not pointing to your server anymore. The name server seems to indicate that your dns host is not broadcasting your information anymore - depending on their size, once the problem is fixed it could take several hours to several days to fully fix itself (it may be sooner - it's been awhile since I've had to deal with dns records) Lirria
    0 pointsBadges:
    report
  • adanbluearc
    try from an outside host: There's a dns problem somewhere. Probably from outside, but could be somewhere inside as well if you have a firewall and an external host (spam filter) receiving mail. The possibilities are too many to give extensive troubleshooting guideline, but here's a few. Check for mx records, make sure they exist. Test from both outside and inside. If you're having problems getting a response, make sure your domain registration is up to date. Look for a whois server in google and do a search on your domain. nslookup set type=mx your_domain.com Also, try to see what host is giving the failure in the bounce message. Is it outside your network or inside?
    0 pointsBadges:
    report
  • Develish
    Boss You have a DNS Name Server issue. From your mail I cannot gather your experience level with DNS, so I will give you a long answer. My apologies in advance for going below your knowledge level. :) For your domain name you have a registrar. Your registrar will have your domain records which include a name server (NS). Many registrars or even your web site host will provide you free DNS hosting. So when anybody on the internet types your name, they are first sent to your registrar who then says, this is the NS for your domain. Then your NS will tell the whole internet the IP addresses of all the Hosts that you have listed. Such as your web server, the MX (Mail eXchanger), your OWA, etc. This, normally, is the broken link. Somewhere either your Name Server is down or the DNS record in your name server is corrupted. Do a WHOIS search on your domain name. If it is a US domain name like .COM, .NET, etc., go to www.internic.net, otherwise go to the respective country's top level registrar. Get your NS IP address. Normally there will be a primary and a secondary. Try and ping your name servers. If that is up, then you need to visit your name server host and look in to the DNS records and see if that exists or is it corrupted, erased etc. You will have to get your DNS record correctly restored, or put a new one in, and get it refreshed. However, remember, the normal refresh period for your DNS records to start getting re-populated on the Internet can be more than 24 hours. So start working fast. If your name servers are down, contact the ISP hosting the NS immediately. Another option, is your domain name up and registered ? In case you have contracted it out to some provider and have not renewed your registration, your registrar may have deleted your registration, in which case, the WHOIS will not work and give you a NS. I hope this helps. Kind regards
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Since your using Exchange 2003 I assume you have an AD domain which lives on DNS. First look at the obvious, can you send mail internally over your network? Are you seeing any other internal DNS symptoms such as slow logons, failed name resolution between client and servers? These items would indicate a problem with your AD DNS structure. If your internal network is working and your problem is limited to internet mail, start looking at your external DNS. You may want to contact your ISP as there could be problems at their end. Make sure you can see the servers hosting your external domain records and confirm you have an MX record published with your external provider. You haven't made any changes to your addressing scheme or renamed / added any mail servers have you? One other thing to think about if you have confirmed internal connectivity and ruled out external DNS as a culprit, is check that your domain has not landed on one or more public blacklists. Blacklisting will cause all sorts of internet mail problems. Here a couple websites that offer free tools for checking DNS as well as blacklist membership. www.dnsreport.com, www.checkdns.net - DNS tools www.spamhaus.org - provides list of various blacklists Good luck!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following