locked
Edge Transport 2007 not communicating with Exhcange 2010 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have an Exchange 2007 Edge Transport server that is queuing inbound emails from the internet and is not passing them on to the Exhcange 2010 server we have. All outbound email is working and all internal email is working.  This is the 2nd time in 3 days that this has happened.  The first time it happened, I just restarted the transport service on the Edge server.

    The servers can ping each other by IP and by computer name.  I have restarted the Trasport Services on each server as well but inbound email is still being queued.  My clietns are getting message delay emails from their providers with an error:

    Action: delayed
    Status: 4.4.7
    Diagnostic-Code: smtp;400 4.4.7 Message delayed

    When I telnet to the Exchange Server from the Edge server I get:

    250-CHIPBC10MBX01 Hello [10.20.1.45]
    250-SIZE
    250-PIPELINING
    250-DSN
    250-ENHANCEDSTATUSCODES
    250-STARTTLS
    250-X-ANONYMOUSTLS
    250-AUTH NTLM
    250-X-EXPS GSSAPI NTLM
    250-8BITMIME
    250-BINARYMIME
    250-CHUNKING
    250-XEXCH50
    250-XRDST
    250 XSHADOW

    Ideas?

    Thanks!!!
    Randy

     


    • Edited by RSN023 Sunday, July 3, 2011 9:30 PM added telnet info
    Sunday, July 3, 2011 9:13 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Seems the problem was that there was not enough free disk space on teh Exchange Server.  I cleared up the free disk space on the Edge server and the system was still not sending email to the Exhcange server.  I then sent an email via a telnet session and receieved the "not enough resources" error.  I loked the the Exchange server's queue disk and noticede there was only 3GB free, I cleaned the disk up to 6GB free and all the mail came from the Edge server to the Exchange server.  It is still working now.

     

    Randy

     

    • Marked as answer by emma.yoyo Tuesday, July 5, 2011 8:25 AM
    Monday, July 4, 2011 6:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You have encountered the back pressure function, read more about it here:

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

     

    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    • Marked as answer by emma.yoyo Tuesday, July 5, 2011 8:25 AM
    Tuesday, July 5, 2011 5:53 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    Are you using Edgesync?

    What about the connectors?

    On the HUB server, is there any limitation by IP addresses configured by which that can connect?

    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    Monday, July 4, 2011 12:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Seems the problem was that there was not enough free disk space on teh Exchange Server.  I cleared up the free disk space on the Edge server and the system was still not sending email to the Exhcange server.  I then sent an email via a telnet session and receieved the "not enough resources" error.  I loked the the Exchange server's queue disk and noticede there was only 3GB free, I cleaned the disk up to 6GB free and all the mail came from the Edge server to the Exchange server.  It is still working now.

     

    Randy

     

    • Marked as answer by emma.yoyo Tuesday, July 5, 2011 8:25 AM
    Monday, July 4, 2011 6:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You have encountered the back pressure function, read more about it here:

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

     

    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82
    • Marked as answer by emma.yoyo Tuesday, July 5, 2011 8:25 AM
    Tuesday, July 5, 2011 5:53 AM