Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

2013 SP1  -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR

I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included

I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:

2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"

The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110

I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.

But I still can't send mail. Any suggestions where next to check?


April 1st, 2014 9:10pm

Hi Tony 

Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013

First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.

You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.

Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results

Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work 

Also try disabling the firewall and see if it helps.

Free Windows Admin Tool Kit Click here and download it now
April 2nd, 2014 12:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics