locked
Receive operation on the connection failed RRS feed

  • Question

  • Hello,

    I installed edge server in my environment while I try to connect remotely, I get the message: "Cannot sign in because the server is temporarily unavailabl. If the problem persists, Contact your system administrator"

     

    While I'm using the logging tool on the server I can see the following error message:

     

    TL_ERROR(TF_CONNECTION) [0]0500.013C::02/13/2008-14:13:24.406.00003d53 (SIPStack,SIPAdminLog::TraceConnectionRecord:1224.idx(157))$$begin_record

    LogType: connection

    Severity: error

    Text: Receive operation on the connection failed

    Local-IP: 10.10.50.229:1370

    Peer-IP: 10.10.50.226:5061

    Peer-FQDN: tm1ocs.tescom.net

    Peer-Name: tm1ocs.TESCOM.NET

    Connection-ID: 0xC501

    Transport: M-TLS

    Result-Code: 0x80072746 WSAECONNRESET

    $$end_record

     

     

     

    Please advice.

    Wednesday, February 13, 2008 2:32 PM

All replies

  • Are you using SRV records to locate your edge server or are you manually configuring the server name in the Communicator client?  If you are using SRV records, is the edge configured to listen on the same port configured within the SRV record?

     

    Wednesday, February 13, 2008 4:53 PM
  • I'm not using SRV record, I'm using manual configuration, and I can see that the client can reach the server but cannot succesfull login.

     

    thanks.

     

    Thursday, February 14, 2008 9:24 AM
  • At the remote client, do u have the root CA which has been used to get the cert configured on the edge server?

     

     

    Ram K Ojha
    MCSE 2003 (Messaging), MCTS - (LCS 2005, OCS 2007)
    http://www.ocspedia.com
    http://www.ITCentrics.com

    Friday, February 15, 2008 4:58 AM
  • You will also need to verify that the Edge server can communicate with the Front end server.  Try running a validation on the edge server that inclues a log on test.  You may want to check that the edge resolves the front end correctly through DNS.

    Saturday, February 16, 2008 8:24 AM