Select the product you need help with
DCOM port range configuration problemsArticle ID: 217351 - View products that this article applies to. This article was previously published under Q217351 SYMPTOMS
You may notice the following symptoms:
CAUSE
This problem occurs because of improper configuration of the port range settings in the HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet registry key or because the port restrictions for a protocol are configured through the DCOMCNFG protocol property page.
RESOLUTIONImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in WindowsTo resolve this problem, use one of the following methods:
MORE INFORMATION
Configuring the computer to use a range of ports can break other applications on the system. On systems that are running Microsoft Windows NT 4.0 Service Pack 4 and later, the best alternative is to configure the DCOM application to use the static endpoint by using the AppId key. To configure the DCOM application to use a static port by using TCP/IP as the DCOM protocol, follow these steps: On the Client Computer:
REFERENCES
For more information regarding the mapping for the .exe name, click the following article number to view the article in the Microsoft Knowledge Base:
216051
(http://support.microsoft.com/kb/216051/
)
FIX: DCOMCNFG NT 4.0 SP4 Does Not Write .exe Name under HKCR\APPID
Properties | Article Translations
|


Back to the top








