Win 2k Server & Exchange problem

Hiya,

I

If you are not recieving incoming mail and nothing has changed within exchange it suggests some sort of firewall / routing problem.

First thing to check is are your mx records still available as you would expect via DNS from the internet.

Next try to telnet you email server from the internet using the smtp port. This will help test if your server is available over the internet. You should get some sort of response. If not then maybe you are now blocking incoming connections on that port.

Also check your routing coming in from the internet for your EMail system. It may need setting up again.

Another way of doing it is assume your Exchange server is OK and then go through the steps of setting everything else up from scratch but only check to see if anything is wrong or missing. Don't make any changes unless you are sure.

Hope that helps, I am bit tired so it may be a bit vauge

Thanks for the reply
ermmmm, this is a bit above my head, how do I
"First thing to check is are your mx records still available as you would expect via DNS from the internet."

I'm not very experienced with exchange.

I've done the telnet before so should be able to figure that one out

>First thing to check is are your mx records still available as you would expect via DNS from the internet.

Not sure what that means....

Thanks again,
Steve

From google :-

"An MX record or Mail exchanger record is a type of resource record in the Domain Name System (DNS) specifying how Internet e-mail should be routed. MX records point to the servers that should receive an e-mail, and their priority relative to each other."


Your emails will end in [email protected]

When an external system send emails you your mail server they get your public IP for the mail server by resolving the yourcompany.com against MX records that exist in DNS (internet) for your company. These will list in order of priority which of your mail servers to target first and then which is next if the first one does not respond. If the MX records are incorrect or no longer exist then no one can send you EMail.

Try any of the DNS websites like DNSstuff and they should show you you.

Hope that makes a but more sense

Thanks again for that, I forgot about the knowledge of google

I got this from doing an MX DNS lookup

How I am searching:
Searching for www.example.com MX record at c.root-servers.net [192.33.4.12]: Got referral to SUN.REDIRIS.es. (zone: es.) [took 25 ms]
Searching for www.example.com MX record at SUN.REDIRIS.es. [130.206.1.2]: Got referral to ns1.bb-online.net. (zone: example.com.) [took 152 ms]
Searching for www.example.com MX record at ns1.bb-online.net. [194.168.163.59]: Reports that no MX records exist. [took 122 ms]

Response:
No MX records exist for www.example.com, and www.example.com does not exist. [Neg TTL=86400 seconds]

Details:
ns1.bb-online.net. (an authoritative nameserver for example.com.) says that there are no MX records for www.example.com, and that the hostname www.example.com does not exist.
The E-mail address in charge of the example.com. zone is: [email protected].
I also got this as well by doing a DNS report

Getting MX record for www.example.com (from local DNS server, may be cached)... Received an NXDOMAIN response.
This means that the www.example.com domain does not exist! No mail can be sent to it

Am I right in syaing that something has gone wrong with the hosting of our domain?

Cheers,
Steve

Are you able to log into your domain providers website and check what has happened to the Domain?
Or if it's provided by your ISP, can you login to their website and find out what has happened?

Or log onto the domain registration website? Nominet covers UK registered domains.

Not sure yet, the domain name is handled by someone else, it is still registered til next year but we are now wondering if it briefly expired or the MX record has somehow been lost or corrupted. They are looking into it at the moment

Its a .es domain

Cheers,
Steve

Edited by deleted (Fri 01-Jun-07 23:14:24)

We're back up and running now, it was something to do with the people who look after the domain. What they had done or not done I am not sure, but its working!!!

Thanks for everyones help.