locked
Office Communication Server 2007 - Certificate Error RRS feed

  • Question

  • I am pasting few error messages from Eventlog of the Client in this context.

     

    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 7
    Date:  7/13/2008
    Time:  6:56:06 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator failed to connect to server 192.168.0.2 (192.168.0.2) on port 5060 due to error 10061.  The server is not listening on the port in question, the service is not running on this machine, the service is not responsive, or network connectivity doesn't exist.
     
     Resolution:
     Please make sure that your workstation has network connectivity.  If you are using manual configuration, please double-check the configuration.  The network administrator should make sure that the service is running on port 5060 on server 192.168.0.2 (192.168.0.2).

    ************************************************

    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 4
    Date:  7/13/2008
    Time:  6:09:22 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator could not connect securely to server 192.168.0.2 because the certificate presented by the server did not match the expected hostname (192.168.0.2).
     
     Resolution:
     If you are using manual configuration with an IP address or a NetBIOS shortened server name, a fully-qualified server name will be required.  If you are using automatic configuration, the network administrator will need to make sure that the published server name in DNS is supported by the server certificate.


    **************************************************

    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 5
    Date:  7/13/2008
    Time:  6:04:54 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator could not connect securely to server 192.168.0.2 because the certificate presented by the server was not trusted due to validation error 0x80090325.  The issuing certificate authority (CA) for the server's certificate may not be locally trusted by the client, the certificate may be revoked, or the certificate may have expired.
     
     Resolution:
     A tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit can be used in order to interpret the error code listed above.  If you trust the server certificate, the issuing certificate authority (CA) certificate can be placed in the local trusted root certificate authorities certificate store.  If you have logged into the server before without issues the network administrator should carefully examine the certificate if no known configuration changes have been made.

    ****************************************************


    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 5
    Date:  7/13/2008
    Time:  6:04:13 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator could not connect securely to server 192.168.0.2 because the certificate presented by the server was not trusted due to validation error 0x80090325.  The issuing certificate authority (CA) for the server's certificate may not be locally trusted by the client, the certificate may be revoked, or the certificate may have expired.
     
     Resolution:
     A tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit can be used in order to interpret the error code listed above.  If you trust the server certificate, the issuing certificate authority (CA) certificate can be placed in the local trusted root certificate authorities certificate store.  If you have logged into the server before without issues the network administrator should carefully examine the certificate if no known configuration changes have been made.

     

    ************************************

    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 7
    Date:  7/13/2008
    Time:  6:02:47 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator failed to connect to server 192.168.0.2 (192.168.0.2) on port 5061 due to error 10060.  The server is not listening on the port in question, the service is not running on this machine, the service is not responsive, or network connectivity doesn't exist.
     
     Resolution:
     Please make sure that your workstation has network connectivity.  If you are using manual configuration, please double-check the configuration.  The network administrator should make sure that the service is running on port 5061 on server 192.168.0.2 (192.168.0.2).

     

     

    Please suggest some remedy.

    Thursday, July 17, 2008 7:17 AM

All replies

  • It sounds like you have 2 problems.  First you need to configure Communicator to connect using the FQDN of the OCS server or pool.  Second, the PC from which you are connecting needs to trust the CA certificate.  If you do a quick search on this forum you should find assistance with how to do this.

    Friday, July 18, 2008 2:41 PM
    Moderator
  • Dear mike
     i am getting the same error message
    Event Type: Error
    Event Source: Communicator
    Event Category: None
    Event ID: 5
    Date:  7/13/2008
    Time:  6:04:13 PM
    User:  N/A
    Computer: TEST2
    Description:
    Communicator could not connect securely to server 192.168.0.2 because the certificate presented by the server was not trusted due to validation error 0x80090325.  The issuing certificate authority (CA) for the server's certificate may not be locally trusted by the client, the certificate may be revoked, or the certificate may have expired.
     
     Resolution:
     A tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit can be used in order to interpret the error code listed above.  If you trust the server certificate, the issuing certificate authority (CA) certificate can be placed in the local trusted root certificate authorities certificate store.  If you have logged into the server before without issues the network administrator should carefully examine the certificate if no known configuration changes have been

    Can you plese heplp me.  feroz1020@rediffmail.com
    Monday, September 21, 2009 1:42 PM
  • There is no need to post this question 5 times in 5 different threads.  See the responses posted in this other thread:
    http://social.microsoft.com/Forums/en-US/communicationsserveredgeservers/thread/124cf304-662a-4d1a-abac-33d5f3fc46e2
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Thursday, September 24, 2009 12:48 PM
    Moderator