The information in this article applies to:
SYMPTOMSAfter 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. CAUSEThis fix is an update to the hotfix described in the following article: Q184278 Server in One Domain May Disconnect Client in Another DomainThis 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. RESOLUTIONTo 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:
-or- http://www.microsoft.com/support/supportnet/overview/overview.asp STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Service Pack 6. Additional query words:
Keywords : kbbug4.00 kbfix4.00 |
Last Reviewed: October 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |