BUG: Windows NT Version 4.0 Bug List - RPC Runtime
Article ID: 165821
Article Last Modified on 4/13/2004
APPLIES TO
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q165821
SUMMARY
This article lists the bugs in the implementation of the Win32 API on
Windows NT 4.0 that may be relevant to Application or Device Driver
developers (ISVs or IHVs). This article contains only those bugs that were
known at the time of the Windows NT 4.0 release.
MORE INFORMATION
Forcing datagram RPC to use the winsock interface causes ncadg_ipx
to fault occasionally.
RPC locator fails to start when configured as autostart.
RpcNsBindingInqEntryName with RPC_C_NS_SYNTAX_DEFAULT gives error
1736 when using DCE CDS.
RpcObjectInqType returns error instead of nil type uuid when passed
a nil object uuid.
RPC_C_PROFILE* values are inconsistent with DCE values.
A cancel on a connection-oriented transport may cause the following
call to fail.
Invalid pipe operation on server may result in RPC_S_CALL_FAILED_DNE
error on the client side.
RPC does not accept self-relative security descriptors for endpoint.
NT client does not send orphaned PDU on connection-oriented cancel
timeout.
NT server sends fault PDU for incorrect "maybe" connection-oriented
requests.
Sending garbage data to port 135 breaks the endpoint mapper.
Context handle rundown called on DCE server if NT client idles.
RPC does not handle long host names.
Keywords: kbbug kbapi kbrpc kbnetwork kblist KB165821