Solved

Exchange 2003, 2010, breaking the connector

Posted on 2010-09-13
5
235 Views
Last Modified: 2012-06-27
my exchange 2010 server is up and running along side my exchange 2003.  I've moved the OAB, Public Folders, etc and I'm ready to edit my firewall.  When I point all my port 25 traffic to my new IP, i get an error (#530 5.7.1 Client was not authenticated ##).  I'm thinking its becasue I still have my 2003 server up and the connector is routing all traffic thru that old server.

thoughts?  will simply breaking the connector work?  Or must I do more?

Thanks

Cliff
0
Comment
Question by:crp0499
5 Comments
 
LVL 28

Expert Comment

by:sunnyc7
ID: 33665298
how have you planned the co-existence ?

For a 2003/2010 co-existence, let Exchange 2010 receive emails (port forward to exchange 2010) lan IP - and then route emails from 2010 to exchange 2003
0
 
LVL 32

Accepted Solution

by:
endital1097 earned 500 total points
ID: 33665301
you need to update your "Default Server" receive connector adding the anonymous permission group
0
 

Author Comment

by:crp0499
ID: 33665357
the exchange 2003 existed previously.  I added the 2010 server with the intention of taking down the 2003.  I'm at the point where i think I'm ready to take the 2003 out of the loop and send all mail to the new server.  So, I edited my router and sent all 25 traffic to the new server and I got the error.  I was thinking of now deleting the connector from the 2010 to the 2003 server.
0
 
LVL 32

Expert Comment

by:endital1097
ID: 33665378
check your receive connector, internet connection are anonymous
0
 
LVL 19

Expert Comment

by:R--R
ID: 33665400
Disable the firewall rule which points to 2003.
Create a new rule pointing to 2010 and check.
0

Featured Post

Does Powershell have you tied up in knots?

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

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Exchange 2010 internal URLs 2 40
ESX 6.0 Best Practices for datastore size 5 75
exchange powershell question 5 34
Exchange 2013 Update 4 26
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Read this checklist to learn more about the 15 things you should never include in an email signature.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question