Exchange 2010- not receiving mail...new SBS2011 server

Just finished setting up the 2011SBS server, converted over from 2003 Standard and 2003 ExchangeSP2.
Internal and outbound mail work fine. outbound to inbound does not work.
I went through the troubleshooter and it did send an email to an internal user, but there was an error message. Mail submission failed: Error message: Server does not support secure connections.

Using the EMC under Organization Configuration/Hub Transport/Edge Subscriptions Tab there is nothing...should there be something there?

I looked at the receive connector (setup by default, I assume) and permissions does have Anonomous users ticked.
350ztnAsked:
Who is Participating?
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.

BAYCCSMSPCommented:
I am going to assume that you assigned the new server a new internal IP? if so did you change your access and nat rules to allow the inbound traffic to come to the server from the outside? I just want to rule that out.
0
BAYCCSMSPCommented:
Also is the old server still in on the network? Is their a connector between the two so that they can communicate? If their is a connector I am going the permissions on that connector may need to be adjusted.
0
350ztnAuthor Commented:
It was given the same ip address as the old server and the old server is offline.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

davorinCommented:
Have you tried to run BPA?
You can also try to run SMTP diagnostics test on http://www.mxtoolbox.com.
0
350ztnAuthor Commented:
what is BPA?
ran MXtoolbox... comes back with below results- looks okay other than reversedns not matching banner? is that a problem?

 OK - 64.18.4.13 resolves to s5b1.psmtp.com
 Warning - Reverse DNS does not match SMTP Banner
 Supports TLS.
 0 seconds - Good on Connection time
 Not an open relay.
 0.250 seconds - Good on Transaction time



Session Transcript:
EHLO please-read-policy.mxtoolbox.com
250-Postini says hello back
250-STARTTLS
250-8BITMIME
250 HELP [31 ms]
MAIL FROM: <supertool@mxtoolbox.com>
250 Ok [47 ms]
RCPT TO: <test@example.com>
554 No relaying allowed - psmtp [47 ms]
QUIT
221 Catch you later [31 ms]
0
davorinCommented:
BPA is Best practice analyzer - you can find it in Exchange management console -> tools
0
davorinCommented:
I guess you are using Postini as antispam. In SMTP test you should enter your public IP address of your mail server.
0
350ztnAuthor Commented:
well I did an Mx lookup for that address and it reports back 3 MX records... all through postini.
I'm an installer at the client site
0
350ztnAuthor Commented:
BPA, when I run the Connections option shows the new and the old exchange server. the old exchange server is disconnected. It had 3 errors relating to the old exchange server. Registy can't be accessed, Performance data can't be accessed, and WMI can't be accessed. all errors were regarding the OLD exchange server, not the new one.
0
350ztnAuthor Commented:
Is there some sort of process I can go through to create a new receive connector to get this working? outside email to internal is all that is not working...needs to be working by tomorrow....
0
davorinCommented:
If you are at clent site and you don't know public IP address this link will help you
http://www.whatismyip.com
0
350ztnAuthor Commented:
alright...here is that output... looks to be same error on banner

Object reference not set to an instance of an object. : Completed Got Banner

 OK - 64.61.15.250 resolves to mail.benefitstomarketing.com
 Warning - Reverse DNS does not match SMTP Banner
Does not support TLS.
 0 seconds - Good on Connection time
Not an open relay.
 0.109 seconds - Good on Transaction time
0
350ztnAuthor Commented:
noticed something in BPA scan Scope:
I have the Exchange administrative group with the new exchange server under it. Then I have a First Administrator Group with the OLD exchange server under it.

I do think that is why those errors were stated a couple comments up in the thread, was because I selected both systems.

Question is... Is how to get that first administrators group out of there, and is it causing the issue?
OLD exchange was 2003 running on 2003 StandardSP2
NEW exchange is 2010 running on SBS2011
0
davorinCommented:
Have you not followed any of exchange 2003 to exchange 2010 migration guides?
That group would be removed with proper procedure of removing exchange 2003 server from exchange organization. Look at the end of this document:
http://www.msexchangegeek.com/2010/01/30/rapid-transition-guide-from-exchange-2003-to-exchange-2010/
The other (by Microsoft unsupported procedure) is by using adsiedit.
Are you still capable of changing the configuration of SBS2011 in such way that it will be again capable of communicating with old exchange server? In that way could be able to finish properly the migration using the guide.

Have you transfered all FSMO roles from old domain controller to SBS 2011?
I guess the old domain controller will be demoted and removed from your network?

For troubleshoot SMTP receive connector try to enable SMTP logging an that receive connector and check the logs.

I'm sorry, but I'm not familiar with Postini, but maybe (I say not likely) you need to change some setting on their side?
0

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
350ztnAuthor Commented:
recreated the receive connector did the trick.
0
350ztnAuthor Commented:
new connector fixed the issue
0
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
Exchange

From novice to tech pro — start learning today.

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.