Migration from Exchange 2003 to 2010 leads to block of all incoming e-mail after removal of Routing Group Connector

I recently came close to completing migration from Exchange 2003 to 2010, moving from a Windows 2003 platform to Windows 2012. After I had moved all of the mailboxes everything was working fine with the systems connected. Now I need to remove Exchange 2003 from the old server. However, as soon as I execute the [Get-RoutingGroupConnector | Remove-RoutingGroupConnector] command in PowerShell on the 2010 system, all incoming e-mail is blocked somehow. Outbound email is fine. Restoring the RGC fixes the problem, but I don't want to run the old server forever. I don't see any problems with SMTP or firewalls. MX points to the new server. Please help me cut the cord to my old server before it dies on its own.
JohnDoctorAsked:
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.

Alan HardistyCo-OwnerCommented:
Did you redirect Port 25 from the old Exchange 2003 server to the new Exchange 2010 server on your firewall?

Have you setup a Receive Connector on your new Exchange 2010 server with at least anonymous authentication enabled?

Alan
0
VB ITSSpecialist ConsultantCommented:
In the Exchange Management Console on the Exchange 2010 server > expand Server Configuration > click on Hub Transport  > click on the name of your Exchange 2010 server in the top pane > in the Receive Connectors tab underneath right click on the Default <EX2010 Server Name> > PropertiesPermissions Group tab > make sure the Anonymous users box is ticked.
Receive-Connector.jpg
0
JohnDoctorAuthor Commented:
Thanks, but anonymous user permission was enabled in default receive connector and the problem persisted.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

VB ITSSpecialist ConsultantCommented:
Did you update the port forwarding rule on your firewall as Alan suggested above to forward SMTP traffic (port 25) to the IP address of your new Exchange server?
0
JohnDoctorAuthor Commented:
Thank you, the firewall was already redirecting port 25 to the new server and we cannot get incoming email without the RGC.
0
VB ITSSpecialist ConsultantCommented:
Doesn't really make any sense. Just to confirm, emails sent to your company.com email address will reach your firewall > Exchange servers and that's it? Do you have anything else within your network that might handle SMTP traffic?
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
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.