Microsoft KB Archive/826382

= How to Disable DCOM Support in RPC over HTTP =

Article ID: 826382

Article Last Modified on 9/5/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition

-



Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
Windows Server 2003 provides support for implementing the remote procedure call (RPC) protocol over HTTP, known as &quot;RPC over HTTP.&quot; By default, RPC over HTTP support is not installed when you install Windows Server 2003, but you can enable it by using Add/Remove Programs.

To determine if you have support for RPC over HTTP enabled on servers running Windows Server 2003, follow these steps:
 * 1) In Control Panel, click Add/Remove Programs
 * 2) Click '''Add/Remove Windows Components

This will start the Windows Components Wizard'''
 * 1) Click Networking Services, and then click Details.

If the RPC over HTTP Proxy check box is selected, RPC over HTTP support is enabled on the server.

DCOM is a protocol that can be used on top of the RPC protocol by client / server applications. By default, a server running Windows Server that is configured to support RPC over HTTP will also accept DCOM requests using this protocol. These DCOM requests are then sent to a local port on the server implementing RPC over HTTP (TCP port 593).

Security best practices recommend disabling or removing all nonessential components and services.

If DCOM support is not required on your RPC over HTTP servers, you can remove DCOM support by modifying the registry. To use RPC over HTTP to remove DCOM support, follow these steps:WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.  Click Start, click Run, type Regedit.exe, and then click OK. Locate the following registry entry:

Note Entries in the &quot;ValidPorts&quot; REG_SZ string value are separated by a semicolon. By default, Windows Server 2003 has the following entry:

This entry allows RPC over HTTP to use ports 100-5000. Change the default entry that is listed in the note in step 2 to the following:

Doing this disables support for DCOM. Remove any entries or any other port ranges that explicitly contain “:593”. For example, remove the following entry:

 Remove any entries or any other port ranges that implicitly contain &quot;593&quot;. For example, remove the following entry:

and replace it with:

.

When you remove entries for port 593, you prevent DCOM from being used through the RPC over HTTP protocol, but RPC programs (like the Outlook 2003 client) are permitted to connect to the RPC server (Exchange 2003 Server) through RPC over HTTP.

When you use RPC over HTTP to remove DCOM support, you can help mitigate the vulnerabilities that are addressed in security bulletin MS03-026 for servers that expose RPC services over HTTP ports 80,443.



MORE INFORMATION
For more information about securing RPC over HTTP, visit the following Microsoft Web site:http://msdn2.microsoft.com/en-us/library/aa378642.aspx

Additional query words: How to secure DCOM RPC over HTTP MS03-026

Keywords: kbhowto KB826382

-

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

© Microsoft Corporation. All rights reserved.