I only disabled the receive connectors for the new mailbox server (that only has the first test mailbox on it), while I was troubleshooting the DNS issue so that it didn't fill the queue with valid messages caught in retry. Doing so allowed the existing 2007 servers to process mail correctly.
Even though the DNS settings were correct on the card, and server set to use the card settings for DNS resolution - the solution was to add the FQDN and HOST name of the 2013 mailbox sever and the DNS servers to it's own host file. We were then re-enabled the connectors and mail flowed correctly. ________________________________ From: [email protected] [[email protected]] On Behalf Of Michael B. Smith [[email protected]] Sent: Thursday, August 21, 2014 2:55 PM To: [email protected] Subject: [Exchange] RE: Exchange Migration from 2007 to 2013 On-premise You cannot disable the receive connectors on the MB server. You need to fix the DNS problem. From: [email protected] [mailto:[email protected]] On Behalf Of Woody Blackman Sent: Thursday, August 21, 2014 2:15 PM To: [email protected] Subject: [Exchange] Exchange Migration from 2007 to 2013 On-premise Greetings all, I am in the middle of an Exchange migration from 2007 SP3 RU 13 to Exchange 2013 SP1 There are 3 MBX/CAS 2007 hosts and 1 2007 Edge server. 1 MBX/CAS and the edge are Server 2008, other two are 2008R2. I have installed 1 CAS, 1 MBX, 1 Edge 2013 into the Organization. All three are Hyperv guests installed 1 to 1 on Server 2012 R2 hosts. All the pre-req's are done - OAB check, Certs with legacy, Internal/external urls, ext DNS working with new CAS beofre legacy swap. IPv6 is on but disabled via registry parameter on all 2007 mailbox servers. I have disabled the Receive connectors on the mailbox server as all messages were getting that were processed by the new MBX server were getting caught in the Queue with a 451 4.4.0 DNS error I tried bringing up the Edge connector to see if it was just an issue with the MBX config, but it exhibits the same behavior. It is not a time sync problem. The history as far as I have been told is that it was a migration from Groupwise to Exchange 2003 then upgraded to 2007 about 3 years ago. Is there something with the old default routing group getting in the way or should I be looking somewhere else?
