Solved

Mail does not flow from Exchange 2010 to Exchange 2003- Error 421 4.2.2 Socket Error

Posted on 2010-11-18
8
1,180 Views
Last Modified: 2012-05-10
I am unable to route email from an Exchange 2010 box to my Exchange 2003 server.  Messages sit in the queue on the 2010 server, and I finally get an error 421 4.2.2 and something about a Socket error.  I have not been able to get the exact message because it only appears when the queue goes into Retry mode (as opposed to Active) which is not very often.  Users on the Exchange 2003 server can send to a user on Exchange 2010.  Everyone can send and receive Internet email (Exchange 2003 is receiving inbound SMTP).  The issue is strictly one way from Exchange 2010 to Exchange 2003.

I worked with Microsoft Tech support yesterday, but they have not been able to solve.  I am waiting for a call back from their Level 2 support.

More details:
-Exchange 2010 running on Windows 2008 R2 configured as DC
-Exchange 2003 running Windows 2003 R2, configured as DC
-There are two other Exchange 2003 servers in the organization, not being used, will be retired


0
Comment
Question by:stschoppe
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 20

Expert Comment

by:EndureKona
ID: 34165617
Not sure what help this will be since I believe MS support would cover all this what I would do.

Have you recreated the Routing Group Connector between Exchange 2003 and Exchange 2010?   Delete the current connectors and create a new one.

New-RoutingGroupConnector -Name “Interop Exchange 2003” -SourceTransportServers “exchange2003.localdomain.local” -TargetTransportServers “exchange2010.localdomain.local” -Cost 1 -Bidirectional $true -PublicFolderReferralsEnabled $true

If this does not work run Exchange BPA for both servers and look for any type of security permission issues.   I have seen a lot where permissions are changed and don't inheret
0
 

Accepted Solution

by:
stschoppe earned 0 total points
ID: 34167488
The issue was resolved by unloading the Trend Micro client from the computer.  I had removed the Trend Messaging Agents early on in the troubleshooting process.  However, I did not realize that a Trend Agent was installed.

Glad it was an easy fix, but I wish I would have figured it out 24 hours ago.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34869529
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
0
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

 

Expert Comment

by:frank1976
ID: 35151525
I ran into this error after our firewall was updated. The issue for us was ESMTP inpsection by the f/w. Once we turned ESMTP inspection off the quques dumped out all the mail.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 35151849
Cisco firewall by any chance?
0
 

Expert Comment

by:frank1976
ID: 35151895
Yes! why do u ask?
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 35151956
It's typical for a Cisco device and it messes up the flow of Exchange communications.

It will cause you sending mail problems (with it enabled) and it actually causes more problems that it solves!  A great feature (I think not)!

It basically restricts the SMTP Verbs being used and also disguises the FQDN of the server, so that other servers see your server as:

220 **********************************************************************

Which makes it very tricky for the receiving server to check the FQDN which it would normally be sending to verify the server is a valid mail server.

This, however, is not related to the above problem in the question - that is a separate issue as the mail-flow is internal not external.
0

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question