DCOM Client Cannot Establish CIS Session Using TCP/IP Address

This article was previously published under Q224595
This article has been archived. It is offered "as is" and will no longer be updated.
After you install Microsoft Component Object Model (COM) Internet Services (CIS) on a computer running Windows NT that is configured with multiple network adapters or with Microsoft Cluster Server, the computer cannot establish a communications link to another computer configured as a Component Object Model server.
To work around this problem, configure the Distributed Component Object Model (DCOM) client to use the cluster server's computer name instead of the TCP/IP address when attempting to establish a communications session between the two computers.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 224595 - Last Review: 02/21/2014 00:35:18 - Revision: 1.2

  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Cluster Server 1.1
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbnetwork kbnofix KB224595