Exchange Hub Transport not communicating with Edge Tansport server EBS 2008
- I have an Essential Business Server 2008 Environment.
Currently Inbound email flow is fine with all messages being received. Outbound is however sitting in the mail queue waiting to be delivered.
Next to the Edgesync queue the error is
"451 4.4.0 Primary target IP address reponded with: "421 4.4.2 Connection dropped." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts."
If i restart the HubTransport service then the queue clears and all messages get delivered, however i am then left with the same problem of the mail queue filling once more.
I enabled connection logging but this does not give any clearer indication of the problem (attached partial log below)
#Software: Microsoft Exchange Server
#Version: 8.0.0.0
#Log-type: Transport Connectivity Log
#Date: 2009-10-23T11:56:08.035Z
#Fields: date-time,session,source,Destination,direction,description
2009-10-23T11:56:08.035Z,08CC21DF1E376504,SMTP,edgesync - default-first-site-name to internet,>,EBS-Security.hcllp.local[192.168.1.1]
2009-10-23T11:56:08.035Z,08CC21DF1E376504,SMTP,edgesync - default-first-site-name to internet,>,Established connection to 192.168.1.1
2009-10-23T11:56:59.341Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T11:56:59.497Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 536915
2009-10-23T11:57:09.061Z,08CC21DF1E376504,SMTP,edgesync - default-first-site-name to internet,-,Retry
2009-10-23T11:58:01.172Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T11:58:01.219Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 13922
2009-10-23T11:58:01.391Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T11:58:01.469Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 22440
2009-10-23T11:58:57.611Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T11:58:58.189Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 31596
2009-10-23T11:59:21.627Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T11:59:45.237Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 59659367
2009-10-23T11:59:58.191Z,08CC21DF1E376508,SMTP,edgesync - default-first-site-name to internet,+,b55e86af-10a5-4165-b46e-0301f08a5698
2009-10-23T11:59:58.191Z,08CC21DF1E376508,SMTP,edgesync - default-first-site-name to internet,>,EBS-Security.hcllp.local[192.168.1.1]
2009-10-23T11:59:58.191Z,08CC21DF1E376508,SMTP,edgesync - default-first-site-name to internet,>,Established connection to 192.168.1.1
2009-10-23T12:00:01.409Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:00:01.566Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 13922
2009-10-23T12:00:01.566Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:00:01.644Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 22440
2009-10-23T12:00:59.114Z,08CC21DF1E376508,SMTP,edgesync - default-first-site-name to internet,-,Retry
2009-10-23T12:03:02.539Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:03:02.601Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 13922
2009-10-23T12:03:02.648Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:03:02.726Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 22440
2009-10-23T12:07:10.936Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:07:11.077Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 64714
2009-10-23T12:08:01.578Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:08:01.672Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 13922
2009-10-23T12:08:01.797Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:08:01.906Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 22440
2009-10-23T12:09:15.861Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:09:15.939Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 30773
2009-10-23T12:10:01.581Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:10:01.628Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 13922
2009-10-23T12:10:01.690Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:10:01.768Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 22440
2009-10-23T12:10:10.550Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:10:10.628Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 34384
2009-10-23T12:10:11.534Z,,MAPI,ebs-messaging.hcllp.local,+,
2009-10-23T12:10:11.597Z,,MAPI,ebs-messaging.hcllp.local,-,Messages: 2 Bytes: 12125
2009-10-23T12:10:59.145Z,08CC21DF1E37650B,SMTP,edgesync - default-first-site-name to internet,+,b55e86af-10a5-4165-b46e-0301f08a5698
2009-10-23T12:10:59.145Z,08CC21DF1E37650B,SMTP,edgesync - default-first-site-name to internet,>,EBS-Security.hcllp.local[192.168.1.1]
2009-10-23T12:10:59.145Z,08CC21DF1E37650B,SMTP,edgesync - default-first-site-name to internet,>,Established connection to 192.168.1.1
2009-10-23T12:11:59.646Z,08CC21DF1E37650B,SMTP,edgesync - default-first-site-name to internet,-,Retry
2009-10-23T12:13:01.507Z,,MAPI,ebs-messaging.hcllp.local,+,
The only system changes recently that may have affected this, is the installation of Microsoft DPM 2007. The agent has been installed on the Messaging and Security servers but has not been used to backup up yet.
This was installed per the technet guide at http://technet.microsoft.com/en-us/library/cc512491(WS.10).aspx
Answers
Check info:
1. Please describe the exchange topology
2. Does the issue exist permanently?
3. Is there any error event in the application on the both edge and hub when the issue was reproduced?
4. Please try to ping the edge from hub with the FQDN of hub, and the same from edge
5. Is there anything between edge and hub? Please disable all 3rd party software and try to reproduce the issue
6. Please try to telnet from hub to edge, do a test mail delivery procedure, and check the output
7. Please use “Get-SendConnector | fl” cmdlet to check the settings of Edgesync connectors
8. Please refer my post in this thread to re-subscribe the edge, and monitor the issue
Notes: This forum is for issues on the pure exchange environment, for the issues about EBS server please use “EBS 2008” newsgroup which would be the best place for the question
~~~~~~~~~~~~~~
James Luo
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
~~~~~~~~~~~~~~
- Proposed As Answer byJames-LuoMSFT, ModeratorWednesday, October 28, 2009 1:12 AM
- Marked As Answer byJames-LuoMSFT, ModeratorWednesday, November 04, 2009 1:12 AM
All Replies
Check info:
1. Please describe the exchange topology
2. Does the issue exist permanently?
3. Is there any error event in the application on the both edge and hub when the issue was reproduced?
4. Please try to ping the edge from hub with the FQDN of hub, and the same from edge
5. Is there anything between edge and hub? Please disable all 3rd party software and try to reproduce the issue
6. Please try to telnet from hub to edge, do a test mail delivery procedure, and check the output
7. Please use “Get-SendConnector | fl” cmdlet to check the settings of Edgesync connectors
8. Please refer my post in this thread to re-subscribe the edge, and monitor the issue
Notes: This forum is for issues on the pure exchange environment, for the issues about EBS server please use “EBS 2008” newsgroup which would be the best place for the question
~~~~~~~~~~~~~~
James Luo
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
~~~~~~~~~~~~~~
- Proposed As Answer byJames-LuoMSFT, ModeratorWednesday, October 28, 2009 1:12 AM
- Marked As Answer byJames-LuoMSFT, ModeratorWednesday, November 04, 2009 1:12 AM
- Any update?


