cohabitation exchange 2010 sp3 and 2013 sp1

HI,
I want to upgrade my exchange serv 2010 sp3 to a dag of exchange 2013 sp1.
For now three servers are in cohabitation mode (2 exch 2013 and 1 exch2010).
Everything look fine except the communicaion between a mailbox on a 2013 database and mailboxs still on exchange 2010 database. The other way work fine.
All mails from the exchange 2013 mbx to an exchange 2010 mbx are in state waiting and never deliver.

Can you help me?
Regards
Jérémy
WaycomAsked:
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.

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Make sure your connectivity is not blocking port 25.
Make sure firewall is off.
Make sure "Exchange server authentication" is ticked in Default Receive connector properties

Try to send a test email using the below site and post the error if any.

Please post the error from queue viewer as well
0
WaycomAuthor Commented:
Exchange server authenticatication is enable on both exchange server 2013, not in my exch 2010.
When I try to enable this feature on this server i get this error:

"f the AuthMechanism attribute on a receive connector contains the value ExchangeServer, you must set the FQDN parameter on the receive connector to one of the following values: the FQDN of the transport server "exchange box.*************.***", the NetBIOS name of the transport server "exchange box", or $null."

But i don't know where i can change this, i try to change the name of the receive connector but it didn't work.

All communication from or to external address of my company work well.

Regards
0
Gareth GudgerCommented:
Most likely it is an issue with the Receive Connector on the 2010 box.

Do you have just the default receive connectors? Or did you create any additional receive connectors on 2010 for relay for applications for example?

One of the big issues I have seen is when an additional Receive Connector is created for application relay and is scoped for a network range that includes the IP address of other Exchange servers (the 2013 server).

If you go into the Queue Viewer in Exchange 2013 (its the Toolbox) and look at the queue. What is the error message of the last time it sent? Is it a permissions error? If so, it is likely the above issue.
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

WaycomAuthor Commented:
Thanks for your help,
I create a new receive connector as an internal connector with a subnet of my new exchange servers and the communication works between my 2013 user and 2010.
When i activate the new connector all my linux user came to say me that mail didn't go out of their soft with an error on starttls.
I copied all parameters of the other connector and still connexion doesn't work with starttls parameter.
Do you know what can i search to solve this problem?
I attach all parameters of my receive connecter and it still doesn't work.

Thanks
Regards
bug-exch.jpg
0
Gareth GudgerCommented:
Hmm you shouldn't have had to create a dedicated receive connector for 2010 and 2013 to talk. But glad it is working.

Was the Linux mail working prior to this new receive connector? If so, make sure your new receive connector does NOT include the IP address of the Linux server.
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
WaycomAuthor Commented:
I talk about linux client and their ip is not in the range of the receive connector.
Can I configure which computer use this or another receive connector?

Thanks
Regards
0
Gareth GudgerCommented:
How you have the IP scope configured will determines who uses the Receive Connector. I don't know anything about Linux but if you feel the settings for the Receive Connector would work for Linux mail then you can try adding its IP as well.

To confirm though. Is this a Linux mail server or Linux clients with email software? If Linux clients, how were they sending mail through Exchange before.
0
WaycomAuthor Commented:
I talk about Linux client with email software.
They are configured with imap with starttls.

In the new connector I specified only my exchange server ip addres, so I don't understand why what I did change anything about users.
0
Gareth GudgerCommented:
Right. Your Linux users should not be using the new Receive Connector you just created. Make sure the Scoping in the new receive connector does not include the IPs of the Linux clients.
0
WaycomAuthor Commented:
Finally I put all of my exchange 2013 ip in /32 and it works.
You shouldn't put a subnet because it doesn't work.

Thanks for your help

regards
0
Gareth GudgerCommented:
You can use a subnet, but it can cause problems like this. So I always recommend using /32. Glad its working.
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.