Darren Somthing
asked on
421 4.3.2 Service Not Available
I'm getting ready to migrate to Exchange 2010 from 2003. I have several virtual machines setup to test the installation.
I have a default install of Exchange 2003. I have a CAS, HT, and Mailbox servers. After the install all message are getting stuck in the following queue:
HTserver (Routing Group Connector)
The following error is logged: 421 4.3.2 Service Not Available.
Is there something that must be completed to allow mail flow between the two routing groups?
Thanks.
I have a default install of Exchange 2003. I have a CAS, HT, and Mailbox servers. After the install all message are getting stuck in the following queue:
HTserver (Routing Group Connector)
The following error is logged: 421 4.3.2 Service Not Available.
Is there something that must be completed to allow mail flow between the two routing groups?
Thanks.
Any firewalls on the server ?
Can you telnet to port 25 on the servers
ASKER
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?
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
http://social.technet.microsoft.com/Forums/ar/exchange2010/thread/ae845ae1-2773-4719-a2e8-f926e8f2cf14
ASKER
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.
I went through Microsoft's documentation on the migraton and I can't find anything.
Are these messages incoming and out going ?
ASKER
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.
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.
You can see it from ESM in exchange 2003.
Make sure you at all your domains to the accepted domains tab
ASKER
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-de aba38f5670
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 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-de
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?
ASKER
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
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/
ASKER
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 ?
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
ASKER
This is a default install. I do not have any forwarding setup. I've ran EXBPA. Nothing related to the problem is returned.
ASKER
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.
ASKER
I created a new internal receive connector for testing. Attached are the log file.
RECV20120214-1.LOG
RECV20120214-1.LOG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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 ?
ASKER
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
Thanks,
Ray