DCOM Clients Ping Server After Client Program Has Shut Down

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
After you run an unauthenticated distributed Component Object Model (COM) client that uses the CoSetProxBlanket COM API to set security on its remote interface and calls the remote server object, distributed COM (DCOM) pings may persist even though the client program has released the interface and shut down.
Cause
This fix is an update to the hotfix described in the following article:
184278 Server in One Domain May Disconnect Client in Another Domain
This hotfix addresses the case where an unsecure client activates securely by specifying credentials in the COAUTHINFO structure that it passes to CoCreateInstanceEx. The client may then make secure calls using CoSetProxyBlanket or it may simply make unsecure calls. Prior to the fix, the server object will be cleaned up in approximately six minutes by the COM process. Also, prior to the fix, the client computer will continue to send DCOM pings to the server indefinitely, even after the client and server process have exited. The fix resolves both these issue.
Resolution

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
Properties

Article ID: 224837 - Last Review: 01/09/2015 18:56:29 - Revision: 4.0

  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB224837
Feedback