You are currently offline, waiting for your internet to reconnect

RPC UseWinsockForIP Is Only Applicable to UDP and IPX

This article was previously published under Q186357
This article has been archived. It is offered "as is" and will no longer be updated.


IMPORTANT: This article contains information about editing the registry.Before you edit the registry, make sure you understand how to restore it ifa problem occurs. For information about how to do this, view the "Restoringthe Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"Help topic in Regedt32.exe.
SYMPTOMS
Winsock Proxy lets a Windows Sockets application, running on a privatenetwork client, behave as if it were directly connected to a remoteInternet server application when, in fact, the Microsoft Proxy Server isthe host for this connection. This means that all application-levelcommunications are channeled through a single secured computer -- thegateway computer running Microsoft Proxy Server.

Ordinarily, for datagram packet transfers, the RPC transport DLL bypassesthe sendto( ) and recvfrom( ) functions provided in Wsock32.dll, andcommunicates directly with the underlying device driver. This improves thespeed of packet transfers but makes Winsock Proxy features unavailable tothe application.

Effective with Windows NT 4.0 with Service Pack 2, the RPC transport checksthe registry to see whether to use the function calls provided inWsock32.dll or to talk directly with the device driver.

NOTE: To use RPC with Winsock Proxy, you must add the following informationto the registry:

WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys AndValues" Help topic in Registry Editor (Regedit.exe) or the "Add and DeleteInformation in the Registry" and "Edit Registry Data" Help topics inRegedt32.exe. Note that you should back up the registry before you edit it.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\UseWinsockForIP REG_DWORD "1"
CAUSE
RPC on Windows NT uses optimization for connection oriented traffic. Thisoptimization includes calling the TDI transport. As a result, RPC bypassesthe Winsock proxy.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or 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

After you obtain the latest service pack, perform the following steps:

WARNING: Using Registry Editor incorrectly can cause serious problems thatmay require you to reinstall your operating system. Microsoft cannotguarantee that problems resulting from the incorrect use of Registry Editorcan be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys AndValues" Help topic in Registry Editor (Regedit.exe) or the "Add and DeleteInformation in the Registry" and "Edit Registry Data" Help topics inRegedt32.exe. Note that you should back up the registry before you edit it.

  1. Apply Windows NT 4.0 Service Pack 4.

    NOTE: The third-party application must also be a Winsock 2.1 LSP(layered service provider).
  2. Copy the %SystemRoot%\System32\Rpcltscm.dll file to another name (forexample, Rpclts13.dll).
  3. For the protocol that is being implemented by the LSP (for example,TCP/IP), replace the reference to Rpcltscm.dll in the registry with theabove name. For example,

    change:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ServerProtocols\ncacn_ip_tcp=rpcltscm.d


    to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ServerProtocols\ncacn_ip_tcp=rpclts13.d
  4. Shut down and restart your computer.
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Properties

Article ID: 186357 - Last Review: 10/08/2013 02:52:48 - Revision: 3.1

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT 4.0 Service Pack 2, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbinfo kbfea KB186357
Feedback