421 4.3.2 Service Not Available

Any firewalls on the server ?

Can you telnet to port 25 on the servers

The Windows firewall is disabled on the HT server. When I telnet into port 25 on the HT server I get up to the MAIL verb and then receive the same error message:

4214.3.2 Service not available

These are both new default installations.  I've re installed 3 times and get the same results each time.

Does TLS have to be enabled on Exchange 2003 servers?

I think TLS needs to be on..  I have done the course and have not doen my migration yet.

http://social.technet.microsoft.com/Forums/ar/exchange2010/thread/ae845ae1-2773-4719-a2e8-f926e8f2cf14

The link above is for the Edge Transport server.  I use a Linux MTA and no Edge Transport server.  My problem is with the Hub Transport role.  

I went through Microsoft's documentation on the migraton and I can't find anything.

Are these messages incoming and out going ?

After the installation I noticed that Public Folder replication message where stuck in the queue.

Outgoing messages appear to be working correctly.  Only message using the routing group connectors are having problems.

Have a look at this article http://social.technet.microsoft.com/Forums/en/exchange2010/thread/7dba17e6-fab1-492e-9e56-9f597dc5d0e2

Check if there are routing group connector on both the servers.
You can see it from ESM in exchange 2003.

Make sure you at all your domains to the accepted domains tab

Thanks for all of the replies.  

I've gone over the links.  Connectivity and name resolution is not my issues.  Everything resolves correctly.

The Get-RoutingGroupConnector cmdlet shows both routing groups.  They where created by default when I installed Exchange.

Following is the output from the Get-RoutingGroupConnector cmdlet:
2010 - 2003  "Exchange Routing Group"   "First Routing Group"
2003 - 2010  "First Routing Group"  "Exchange Routing Group"

The following is the output from the Test-Mailflow cmdlet:

RunspaceId             : 85a1dd0a-034b-44af-a42e-deaba38f5670
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest: False
Identity:
IsValid : True

How would I determine the cause of the failure from the Test-Mailflow cmdlet?

I've been doing a log of testing the following is where i'm at:

Exchange 2003 to Exchange 2003: OK
Exchange 2010 to Exchange 2010: OK

Exchange 2003 to Exchange 2010: Failed
Exchange 2010 to Exchange 2003: OK


Exchange 2003 to Exchange 2010 fails with the following message:
421 4.3.2 Service not available

Take a look at this article http://blog.onlinehelpboard.com/2011/04/18/exchange-2003-server-to-exchange-2010-mail-flow-issue/

Thanks for the link but no luck.  The link contained the same information as the rest of the links did.

Do you have any SMTP forwarding setup on Exchange 2003 ?
Ie Smart host configure don your SMTP 2003 environment the "Default SMTP Virtual Server"

Acn you run EXBPA see what it comes back with please ?

Have a look at this also http://t-solve.blogspot.com/2011/09/421-432-service-not-available-closing.html

This is a default install.  I do not have any forwarding setup.  I've ran EXBPA.  Nothing related to the problem is returned.

Thanks for the link but again this link contains the same information as the others.  By default the connectors are created.  I've verified they exist and put the information above.

I created a new internal receive connector for testing.  Attached are the log file.
RECV20120214-1.LOG

have you got  the recieve connector setting set range set as below.

receive range 0.0.0.0/255.255.255.255 to the receive connector

One more thing do you have Network Load balancing setup on any of the servers ?

No NLB.  Yes the receive range.  I have over 50% of my disk space free. No related events logged in the application log.

Thanks,
Ray