You receive an “An HTTPS or TCP connection could not be made” error message when you use Windows Messenger to try to connect to an Office Live Communications Server 2003 Home Server or to an Office Live Communications Server 2005 pool
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
When you use Microsoft Windows Messenger to try to connect to a Microsoft Office Live Communications Server 2003 Home Server or to a Microsoft Office Live Communications Server 2005 pool, you receive the following error message:
An HTTPS or TCP connection could not be made. Please wait for your network administrator to correct this problem, and try again later.
The error message that is mentioned in the "Symptoms" section indicates that Windows Messenger cannot successfully connect to a computer that is running Live Communications Server. This issue may occur if one or more of the following conditions are true:
An incorrect IP address is configured in the Domain Name System (DNS) for the Live Communications 2003 Home Server or for the Live Communications Server 2005 pool.
An incorrect host name is configured in the DNS for the Live Communications 2003 Home Server or for the Live Communications Server 2005 pool.
Note This issue may also occur if you have an incorrect IP address or incorrect host name information in the Hosts file on the client computer. Windows examines the Hosts file to resolve host names before Windows contacts DNS to resolve host names.
The Live Communications Server service is not running on the Live Communications Server 2003 Home Server when you try to sign in.
The ports that Live Communications Server uses are not enabled for connections. Live Communications Server uses Transmission Control Protocol (TCP) port 5060 and TCP port 5061.
Your domain is not populated in Live Communications Server.
To troubleshoot this issue, follow these steps.
Step 1: Verify the DNS settings on the client computer
Examine the IP address that appears in the Preferred DNS Server box on the client computer that is running Windows Messenger. This IP address must be the IP address of the DNS server that hosts the forward lookup zone of the correct Active Directory directory service domain. The correct Active Directory domain is the domain of which the Live Communications Server 2003 Home Server or the Live Communications Server 2005 pool is a member. To view the DNS information on a Microsoft Windows XP-based client computer, follow these steps:
Click Start, click Run, type ncpa.cpl, and then click OK.
Right-click the local area connection, and then click Properties.
Double-click Internet Protocol (TCP/IP), and then examine the IP address that appears in the Preferred DNS Server box.
Step 2: Verify the service location records for SIP automatic detection in DNS
Locate the forward lookup zone for the Active Directory domain of which the Windows Messenger client is a member. Make sure that the forward lookup zone contains the correct service location (SRV) records for Session Initiation Protocol (SIP) automatic detection. For SIP automatic detection to work correctly, one or both of the following service location records must exist in DNS, depending on the protocol or protocols that you use for Live Communications Server.
Host offering this service
The new DNS SRV records for SIP that were added in Live Communications Server 2005 Service Pack 1 (SP1) are as follows:
In the previous table, replace the placeholders as follows:
Replace example.com with the name of your Active Directory domain.
Replace hostname.example.com with the fully qualified domain name (FQDN) of your Live Communications Server 2003 Home Server or with the FQDN of your Live Communications Server 2005 pool.
To determine whether the service location record is available, follow these steps:
On the client computer, click Start, click Run, type cmd, and then click OK.
At the command prompt, type nslookup, and then press ENTER.
Type set type-srv, and then press ENTER.
Type _sip._tls.example.com, and then press ENTER. If the service location record is available, the following information is displayed:
Server: <dns server>.example.comAddress: <IP address of DNS server>Non-authoritative answer:_sip._tls.example.com SRV service location: priority = 0 weight = 0 port = 5061 svr hostname = sip.example.com
Type _sip._tcp.example.com, and then press ENTER. If the service location record is available, the following information is displayed:
Server: <dns server>.example.comAddress: <IP address of DNS server>Non-authoritative answer:_sip._tcp.example.com SRV service location: priority = 0 weight = 0 port = 5060 svr hostname = sip.example.com
To add the service location records, follow these steps:
On the DNS server, click Start, click Run, type dnsmgmt.msc, and then click OK.
Expand your DNS server, expand Forward Lookup Zones, right-click your domain, and then click Other New Records.
In the Select a resource record type list, click Service Location (SRV), and then click Create Record.
In the Service list, type _sip.
Use one of the following procedures:
If you want to deploy Transport Layer Security (TLS), type _tls in the Protocol list, and then type 5061 in the Port number box.
If you want to deploy TCP, type _tcp in the Protocol list, and then type 5060 in the Port number box.
In the Host offering this service box, type one of the following:
For Live Communications Server 2003, type the FQDN of the Live Communications Server 2003 Home Server.
For Live Communications Server 2005 Standard Edition, type the FQDN of the Live Communications Server 2005 computer.
For Live Communications Server 2005 Enterprise Edition, type the FQDN of the Live Communications Server 2005 pool.
Click OK, and then click Done.
After you add these service location records, flush the DNS resolver cache on the client computer that is running Windows Messenger. Then, make sure that Windows Messenger is configured to use automatic detection. To do this, follow these steps:
On the client computer that is running Windows Messenger, click Start, click Run, type cmd, and then click OK.
Type ipconfig /flushdns, and then press ENTER.
Type ipconfig /registerdns, and then press ENTER.
Start Windows Messenger.
On the Tools menu, click Options.
Click the Accounts tab, and then click Advanced next to the My contacts include users of a SIP Communications Service check box.
Click Automatic configuration, and then click OK two times.
Step 3: Verify that the Windows Messenger client program is not configured to use a single-label domain suffix
Windows Messenger does not currently support the use of a single-label domain suffix. For example, Windows Messenger does not currently support a user name such as user@example. Windows Messenger does not create DNS service location queries for an alias that uses a single-label domain suffix. Therefore, Windows Messenger cannot locate the Live Communications Server computer or pool.
To resolve this issue, use a SIP Uniform Resource Identifier (URI) that has a domain suffix such as example.com. In this scenario, you may have to create a new DNS zone for the new DNS name. However, you can configure the service location record in this new DNS zone to point to a host in a domain that has a single-label DNS name. We recommend that you do not use single-label domain names in your organization.
To obtain more information to help you troubleshoot client connection issues in Live Communications Server, obtain network traces of the traffic that is sent from the Windows Messenger client computer. To do this, use tools such as Microsoft Network Monitor or a third-party network capture program such as Ethereal. Additionally, enable client-side tracing on the computer that is running Windows Messenger. To do this, enable the following two registry settings.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Value name: EnableFileTracing Value type: REG_DWORD Value data: 1
When you enable tracing by using these registry settings, trace information is stored in the root folder of the operating system drive. For example, tracing information is stored in C:\. For more information about how to configure tracing in Live Communications Server, click the following article number to view the article in the Microsoft Knowledge Base:
871023 How to enable diagnostic logging for Office Communicator and for Windows Messenger
To enable Communicator logging, use the following registry settings:
Value name: EnableFileTracing Value type: REG_DWORD Value data: 1
Note the FileDirectory value. By default, the FileDirectory value should be set to %USERPROFILE%\Tracing. After you configure these registry values, stop the Communicator process in Task Manager and then restart it . When you restart Task Manager, the client picks up the new registry values. Then, logging is turned on. See the Live Communications Server Planning & Deployment Guide for more information and for session-specific tracing settings.
The Rtcdll registry setting implements the Real-Time Communications (RTC) Client API. For more information about the RTC Client API, visit the following Microsoft Web site:
The Rtcimsp registry setting represents the Instant Messaging Service Provider. In this case, the Instant Messaging Service Provider is Windows Messenger. By examining the Rtcimsp*.log files, you can see data that is specific to the Windows Messenger client program.