Exchange 2010 Test Setup SMTP Problem


I have setup a test Exchange 2010 Domain as we are looking to move from Exchange 2003
in the future.  It has its own DC and is plugged directly into a Router with forwarding on port 25.

After the intial setup I can send emails but I do not receive any from external sources.

I have setup a "Internet Receive Connector" using the Exchange Server IP address and
selected "Anonymous" only for the permissions groups.

When I telnet into the server from "external and internal" on port 25 I receive the


220 EXCHANGETEST01.*******.CO.UK Microsoft ESMTP MAIL Service ready at Sat, 31 Mar
2012 07:22:49 +0100
421 4.4.1 Connection timed out

Connection to host lost.


The connection is open "until" I try to type any commands which causes it to disconnect immediatly.

Any help appreciated

Mongo PeckAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Check this for receive connector configuration from MS this may help.
Mongo PeckAuthor Commented:
Hello I used that for the setup.

But thank you
Make sure that on your router edge network allows port 25 and 110.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Your telnet output looks fine, port 25 is open.

Did you setup your Accepted Domain(s)?  See the following article:

Receive connectors are at the server level but Accepted Domains are at the Organizational level and should be setup first.

Let us know.

1. Open the cmd prompt on Hub Transport Server
2. Telnet localhost 25
3. Now type EHLO and see if it throws the same error.

Post the results and here and I'll tell you what to do next.

~ Singh
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.