smtp relay in active directory site to edge transport server

All my mail stays in queue with the following error message:

<451 4.4.0 Primary target IP address responded 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.>

Receiving mail is no problem.

Situation: exchange server [hub+mail role] , edge [edge role] both have Exchange SP1 installed.
Servers are both replying with "220" on port 25 so this is not a problem.

HELP!




nbommeljeAsked:
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.

nbommeljeAuthor Commented:
After reboot the systeem sends out the compleer Queue. Al new mails then are again being Queued.
0
Vadim RappCommented:
Maybe your firewall is blocking outbound connections. Try to telnet from this machine to some smtp host on port 25.
0
nbommeljeAuthor Commented:
All communication from and to any port 25 is working. I can setup smtp from the exchange server 2 edge en from edge 2 internet. I've tried to check what is happening with the smtp communication between the exhange and the edge by adding a new send connector that resides on the exchange.

When I look at the logs on both side I see the following.

On the exchange side sendlog:
 
"220 edge.domain2.com Microsoft ESMTP MAIL Service ready at Fri, 15 Feb 2008 07:49:32 +0100",
>,EHLO exchangeserver.domain1.com,
<,250-edge.domain2.com Hello [x.x.x.x],
<,250-SIZE 10485760,
<,250-PIPELINING,
<,250-DSN,
<,250-ENHANCEDSTATUSCODES,
<,250-STARTTLS,
<,250-X-ANONYMOUSTLS,
<,250-AUTH,
<,250-X-EXPS NTLM,
<,250-8BITMIME,
<,250-BINARYMIME,
<,250-CHUNKING,
<,250 XEXCH50,
>,STARTTLS,
<,220 2.0.0 SMTP server ready,
*,,Sending certificate
*,CN=exchangeserver.domain1.com,Certificate subject
*,"CN=CertServer, DC=domain1, DC=com",Certificate issuer name
*,**********************,Certificate serial number
*,*******************************************,Certificate thumbprint
*,exchangeserver.domain1.com,Certificate alternate names
,Remote
 
On the edge side rec. log:
 
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
,>,"220 edge.domain2.com Microsoft ESMTP MAIL Service ready at Fri, 15 Feb 2008 08:00:33 +0100",
,<,EHLO exchangeserver.domain1.com,
,>,250-edge.domain2.com Hello [x.x.x.x],
,>,250-SIZE 10485760,
,>,250-PIPELINING,
,>,250-DSN,
,>,250-ENHANCEDSTATUSCODES,
,>,250-STARTTLS,
,>,250-X-ANONYMOUSTLS,
,>,250-AUTH,
,>,250-X-EXPS NTLM,
,>,250-8BITMIME,
,>,250-BINARYMIME,
,>,250-CHUNKING,
,>,250 XEXCH50,
,<,STARTTLS,
,>,220 2.0.0 SMTP server ready,
,*,,Sending certificate
,*,CN=edge,Certificate subject
,*,CN=edge,Certificate issuer name
,*,********************************,Certificate serial number
,*,****************************************,Certificate thumbprint
,*,edge;edge.domain2.com,Certificate alternate names
,-,,Local

Open in new window

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tim HolmanCommented:
So when you reboot, all the mails send themselves without problems?  Is rebooting your current workaround?  
The message you're getting is saying your SMTP connection was established, but dropped, probably as things were getting too busy.
You could try this - not sure if it's the same with Exch 2007 but worth a try:

http://technet.microsoft.com/en-us/library/aa998772.aspx

0
nbommeljeAuthor Commented:
I don't think the server is to busy with only 2 test email adresses. And only one or 3 mails stuck in the queue. I think I have to search the problem some where in certificates.
0
nbommeljeAuthor Commented:
SMTP was not working properly, Solution was removing Exchange, Windows server 2003 and the partition and installing everything new.
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
Email Protocols

From novice to tech pro — start learning today.