Exchange 2013 migration

In the process of migrating from Exchange 2010 to 2013. So far ok. I'm at the point of migrating mailboxes so the first mailbox was a test mailbox. Migrated easy but when testing I can receive email from internal and external ok but I cannot send to any other receipent either internal or external. I followed the best practices etc. but one thing I didn't see is do I need to create a send connector to the Exchange 2010 box?
RichardPWolfAsked:
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.

davorinCommented:
Is the section "Configuring Exchange 2013 and network" from http://msexchangeguru.com/2013/05/10/exchange2013-migration/ of any help?
(4th underlined address)
0
RichardPWolfAuthor Commented:
That's a document I haven't seen before. Let me try that and I'll get back shortly.
0
Simon Butler (Sembee)ConsultantCommented:
You should already have a Send Connector.
Primary reason for this not working is the Receive Connectors are not default and are refusing the email. Do you see anything in the queues?

Simon.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

RichardPWolfAuthor Commented:
I see under queues site;wales;version:14 SMTP Relay to Mailbox Delivery Group, Status->Retry, Message count ->207

Submission , Undefined, Ready , 0
0
Simon Butler (Sembee)ConsultantCommented:
Confirm if you can connect to the other server using telnet to port 25:

telnet ip.add.re.ss 25
telnet servername 25
telnet server.domain.local 25

You should get a response on all three.

Also check any antivirus - that can block port 25 traffic - McAfee is notorious for it.

Simon.
0
RichardPWolfAuthor Commented:
I was able to telnet to the Exch 2010 server ok.
I was able to telnet to the Exch 2013 server ok.

No antivirus on servers. Firewall turned off in domain
0
George SasIT EngineerCommented:
Enable connectivity logging and dig trough the logs.
See why it does not want to connect.

What permissions you have set on the connector ? What IP ranges ? Are they limited somehow by IP range or permissions ?
0
RichardPWolfAuthor Commented:
How do I enable connectivity logging?
0
George SasIT EngineerCommented:
Server Configuration > Hub Transport .
Upper right tab you have your CAS servers. Properties and Log Settings.

Also on the lower tab check the Receive Connectors and check any limitations there.
0
RichardPWolfAuthor Commented:
OK, appears all logging is turned on.
Attached the exchange 2013 connectivity log. Appears that there is an authentication problem.
CONNECTLOG20131022-1.LOG
0
davorinCommented:
Do you have enabled exchange authentification on receive connector?

http://support.microsoft.com/kb/979175
0
RichardPWolfAuthor Commented:
Out of the 5 transport roles on the Exch 2013 all but the frontend client has it enabled.
0
RichardPWolfAuthor Commented:
I did an upgrade to CU2 V2 but that didn't help much. I'm getting a message that the email will be delayed now.
0
RichardPWolfAuthor Commented:
OK, found out the apparent problem. Ran accross an article talking about in a coexistence enviroment that a "separate" receive connector needed to be created on the 2010 box. After that mail started flowing internally. Email started flowing to the internet after I found some Exchange services  that weren't running. But for now all looks good.
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
RichardPWolfAuthor Commented:
Davorin - Thank you. You provided the most information but I felt I needed to give myself a little credit for digging out the rest of the puzzle. As I mentioned what I found was that I needed to create a "separate" receive connector on the Exchange 2010 box to get internal mail flowing. And for some oddball reason I "assumed" that all services were running and that may be a problem to still deal with. More testing next week on that. but for now all seems right with the world.

Thank you again.
0
davorinCommented:
Most important thing is that you have solved your problem. And thanks also for your feedback.
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.