Exchange 2010 won't receive internet emails

Hi all,

I'm putting my head through the wall here trying to get Exchange 2010 to receive internet emails. Yes I did check the "anonimous users" in the Hub Transport under "receive connectors".

I launched a telnet session form a laptop outside the network, and this is the reply I get:

"421 4.3.2 Service not available"
"Connection to host lost"

Can anybody get me unstuck?? please!!
Who is Participating?
Alex_McGyverAuthor Commented:
Exchagne geek,

than kyou for your quick reply. I just found the culprint (and of course it happened just 2 minutes after I posted the question.

I deleted the "receive connector" and recreated it from scratch (to be on the safe side) and changed the the local IP address(es) to "All available IPv4) instead of the local IP of the server (, and then changed the Receive mail from remote servers that have these IP addresses:

Apparently, and I don't know why, the IP was setup as thte local IP of Exchange server instead of the

I do appreciate your quick reply though my friend.
Kent DyerIT Security Analyst SeniorCommented:
Are you in a corporate environment?  Look in your change control system for any changes that networking may have done for anonymous access?  Are you using a SPAM Service like IronMail or like tool and they applied a new signature file?  Did you update your antivirus and there is a new signature in place?  Do you need to go into ePO (ePolicy Orchestrator) and relax the rules for your Exchange Server?

Some things to think about.


Which box is your MX record pointing to?

Secondly, what happens when you telnet locally on the hub server?

Any AV installed?

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Alan HardistyCo-OwnerCommented:
Is port 25 open and forwarded to your Exchange Server on your firewall?

Visit on your server and test port 25 to see.  You should see SUCCESS if all is happy.

If it is, go to and see if the IP Address you see if the one you are expecting to see.

If it is - please post the output of the following Exchange Management Shell command:

get-receiveconnector | fl
Ah i get to read and experience this a lot of times, when we take over certain stuff from someone - they would always screw it up and gift us more headaches than my wife would offer.

Glad that we were there - I'd always ask telnet local and internal works good before lookign outside on internet world.

Alex_McGyverAuthor Commented:
As I explained i was able to find the solution 2 minutes after I posted the question. I solved the problem myself but I do appreciate the prompt replies from these guys
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.