Article ID: 898150 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
After you configure Microsoft Windows Messenger to connect to a computer that is running Microsoft Office Live Communications Server 2005 Enterprise Edition, you experience all the following symptoms:
Live Communications Server 2005 introduces the concept of a pool. A pool is a logical collection of front-end and back-end Live Communications Server computers. When you configure Live Communications Server, you must manually add a host record to the Domain Name System (DNS) for your Live Communications Server pool.
This issue that is described in the "Symptoms" section occurs if Windows Messenger is not configured to communicate with the Live Communications Server 2005 Enterprise Edition pool. For example, this issue occurs if you specify that the Live Communications Server host name or IP address in the Server name or IP address box of the SIP Communications Service Connection Configuration dialog box in Windows Messenger.
When users communicate with other users in Live Communications Server 2005 Enterprise Edition, Live Communications Server includes the name of the pool in the Record-Route field of the Live Communications Server network traffic. If the client computer that is running Windows Messenger cannot resolve this pool name in DNS, the Windows Messenger communications are not successful.
Note This issue only occurs in Live Communications Server 2005 Enterprise Edition. You do not experience this issue with Live Communications Server 2005 Standard Edition or with Microsoft Office Live Communications Server 2003.
To resolve this issue, add a host record for the Live Communications Server Enterprise Edition pool to DNS, and then configure Windows Messenger to connect to that pool. To do this, follow these steps:
Step1: Add a host record to DNS
Step 2: Configure Windows Messenger to connect to the pool
(https://support.microsoft.com/kb/898153/ )"An HTTPS or TCP connection could not be made” error message when you try to connect to an Office Live Communications Server 2003 Home Server or to an Office Live Communications Server 2005 pool by using Windows Messenger
You can view the contents of the Record-Route field if you enable client-side tracing. For more information about how to enable client-side tracing in Windows Messenger, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/871023/ )How to enable diagnostic logging for Office Communicator and for Windows Messenger