Microsoft KB Archive/241947

= BUG: Intel DmiRemoteRegister API Call May Hang on Windows 98 Second Edition =

PSS ID Number: 241947

Article Last Modified on 10/16/2002

-

The information in this article applies to:


 * Microsoft Windows 98

-



This article was previously published under Q241947



SYMPTOMS
The Intel API call DmiRemoteRegister may hang on Windows 98 Second Edition if the target node is a local computer and the protocol sequence used is TCP/IP (ncacn_ip_tcp).



CAUSE
The DmiRemoteRegister API calls the RPC (remote procedure call) layer, which in turn calls the socket layer. The failure is due to a code defect in the socket layer in which a packet is sent but it is never received by the server-side socket. As a result, the sending side is left waiting for the server to respond and the server is left waiting for the sender to send.



RESOLUTION
To work around the problem, you can use the local procedure call protocol sequence (ncalrpc) instead of TCP/IP protocol sequence (ncacn_ip_tcp).

For example, instead of using: DmiHandle_t handle; DmiNodeAddress_t* node = DmiNewNodeAddress("localhost", "dce", "ncacn_ip_tcp", NULL, NULL); DmiErrorStatus_t status = DmiRemoteRegister(&handle,node); DmiRemoteUnregister(handle); you can work around the hanging problem of DmiRemoteRegister call by using: DmiHandle_t handle; DmiNodeAddress_t* node = DmiNewNodeAddress("localhost", "dce", "ncalrpc", NULL, NULL); DmiErrorStatus_t status = DmiRemoteRegister(&handle,node); DmiRemoteUnregister(handle);



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbBug KB241947

Technology: kbWin98 kbWin98search

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.