Mapi error when migrating from Exchange 2007 to Exchange 2013

I built 2 new Exchange 2013 servers at a site, I am trying to move a test account from Exchange 2007 to 2013 and I am getting this error.

All users in Exchange 2007 are fine no issues

EmailAddress      ErrorMessage
TTEXTEST1@nrc.gov
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 49064   dwParam: 0x1
    Lid: 37288   StoreEc: 0x6AB    
    Lid: 49064   dwParam: 0x2
    Lid: 49191   EMSMDBMT.EcDoConnectEx called [length=135]
    Lid: 65063   EMSMDBMT.EcDoConnectEx exception [rpc_status=0x6BA][latency=21016]
    Lid: 45169   StoreEc: 0x977    
    Lid: 50544   ClientVersion: 15.0.1044.29
    Lid: 52080   StoreEc: 0x977    
    Lid: 51152  
    Lid: 52465   StoreEc: 0x977    
    Lid: 60065  
    Lid: 33777   StoreEc: 0x977    
    Lid: 59805  
    Lid: 52487   StoreEc: 0x977    
    Lid: 19778  
    Lid: 27970   StoreEc: 0x977    
    Lid: 17730  
    Lid: 25922   StoreEc: 0x977      --> MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 49064   dwParam: 0x1
    Lid: 37288   StoreEc: 0x6AB    
    Lid: 49064   dwParam: 0x2
    Lid: 49191   EMSMDBMT.EcDoConnectEx called [length=135]
    Lid: 65063   EMSMDBMT.EcDoConnectEx exception [rpc_status=0x6BA][latency=21016]
    Lid: 45169   StoreEc: 0x977    
    Lid: 50544   ClientVersion: 15.0.1044.29
    Lid: 52080   StoreEc: 0x977    
    Lid: 51152  
    Lid: 52465   StoreEc: 0x977    
    Lid: 60065  
    Lid: 33777   StoreEc: 0x977    
    Lid: 59805  
    Lid: 52487   StoreEc: 0x977    
    Lid: 19778  
    Lid: 27970   StoreEc: 0x977    
    Lid: 17730  
    Lid: 25922   StoreEc: 0x977
nourbenAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Simon Butler (Sembee)ConsultantCommented:
Is the server configured correctly?
URL configured for Outlook Anywhere, which is unique - ie not the same as the URLs set on the Exchange 2007 server? How long after moving the mailbox did you wait before attempting to connect Outlook?
Does an Autodiscover test in Outlook return the correct information?

Simon.
nourbenAuthor Commented:
The move failed and the error was from EAC migration tab
Will SzymkowskiSenior Solution ArchitectCommented:
I have seen something similar happen when NIC's were not properly configured on the 2007 CAS server. Also see the link below for similar issue.
http://clintboessen.blogspot.ca/2012/07/mapiexceptionnetworkerror-unable-to.html

Will.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

nourbenAuthor Commented:
Thanks Will, but I can ping both NetBIOS and FQDN from Exchange 2013 to all Exchange 2007
Will SzymkowskiSenior Solution ArchitectCommented:
But do you have duel NIC's on your 2007 CAS servers?

Will.
nourbenAuthor Commented:
Yes, what do I need to check?
nourbenAuthor Commented:
Teamed
Will SzymkowskiSenior Solution ArchitectCommented:
are they 2 separate NIC's? Not Teamed.

Will.
nourbenAuthor Commented:
2 NICs Teamed
NICs.JPG
Will SzymkowskiSenior Solution ArchitectCommented:
Are you trying to move the mailboxes from the GUI or Powershell?

Will.
Moreno JackCommented:
Have a look on below given links which might be helps you to clarifies your concern in more depth and lets you to get this job done.

Checkout the below given informative resource that covers the deployment issues with their solutions which might be helps you to get this job done:
http://blogs.perficient.com/microsoft/2011/06/exchange-2010-mailbox-moves-require-netbios-name-resolution/


You may also take help from this - MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423): http://johanveldhuis.nl/error-mapiexceptionnetworkerror-unable-to-make-connection-to-the-server-hr0x80004005-ec2423/

http://msexchangetips.blogspot.in/2010/11/mapiexceptionnetworkerror-unable-to.html

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
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.