Exchange Server TechCenter > Exchange Server Forums > Transport > Application relaying via Exchange 2007 receive connector fails randomly
Ask a questionAsk a question
 

QuestionApplication relaying via Exchange 2007 receive connector fails randomly

  • Wednesday, November 04, 2009 2:05 PMJackwNDS Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Our web servers relay notifications through Receive connectors.  Each web server has its own receive connector.

    At random times, the application send will fail.  Error below. 

    I have noticed that if I set the connector timeout to 1 day and leave a telnet session over port 25 open, the failure does NOT occur.  (telent session does NOT have to originate from the web server, either). 

    It seems like the SMTP service is going to sleep and will not wake up for the application to use.

    The error is as follows:

    Error Message:   A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.15.21:25

     

    Stack Trace:      at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

All Replies

  • Wednesday, November 04, 2009 8:24 PMAndyD_MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Any A/V or anti spam installed on the Exchange side?
    ANy other errors in the event logs?

    Which server does that ip address refer to?
  • Friday, November 06, 2009 2:58 AMMike ShenMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

     

    In addition to Andy, I also suggest you enable Protocol logging on the Receive Connector. After that, please reproduce the issue and post related SMTP protocol logging here for further research.

     

    Thanks,

    Mike