Microsoft KB Archive/252942
Article ID: 252942
Article Last Modified on 10/31/2006
- Microsoft Windows 2000 Server
This article was previously published under Q252942
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
If you install Microsoft Proxy Server 2.0 on a Windows 2000-based server, you may receive the following error message after rebooting the computer:
The following data is displayed in the Data box in Words view:
This data translates to error code 59 ("An unexpected network error occurred").
Examining the Internet Service Manager console or Event Viewer reveals that the Web and Socks Proxy services did not start. This problem typically occurs on servers that are acting as domain controllers in an Active Directory environment. The problem may not always be reproducible with successive reboots.
When it starts, Windows 2000 allocates Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) ports and hands them to services that request them. When Active Directory is installed, more ports are needed by different services; TCP port 1080 may be allocated for use before Socks Proxy is able to claim it.
Because a service is already bound to port 1080, the Socks Proxy service that listens on port 1080 by default does not bind to the socket. The result is that the Web Proxy service is also not initialized, causing event ID 127 to be logged.
Note that several different issues can cause the described event to occur. If the Data box contains "0x0000003b" as described in the "Symptoms" section, the port 1080 issue is one known cause. See the "More Information" section for other articles in the Microsoft Knowledge Base that describe similar issues.
If you set a port reservation for port 1080, Windows 2000 does not use port 1080 for dynamic allocation and Socks Proxy can use it.
There are two different way to resolve the problem:
Method 1 (Recommended)
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.
If you need to run the Socks Proxy service, make the following change, and then restart the server:
- Start Registry Editor (Regedt32.exe).
- Locate the following key in the registry:
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: ReservedPorts
Data Type: REG_MULTI_SZ
The string uses the format
xxxx-yyyy. It looks like this for just a single port: "1080-1080".
- Quit Registry Editor.
This registry setting prevents Windows 2000 from dynamically allocating port 1080. The port is reserved for Socks Proxy to use.
If you do not use the Socks Proxy services, you can disable the Socks Proxy service. For additional information, see the following article or articles in the Microsoft Knowledge Base:
173961 How to Disable the Proxy Socks Service by Modifying the Registry
After you disable the Socks Proxy service and restart the computer, verify that the Web Proxy service is started successfully.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
244223 Troubleshooting and Resolving Web Proxy Event ID 127
220978 Err Msg: Web Proxy Service Failed to Start. Please Check the Server Event Log for Further Details
248476 Error Message: Event ID 127: The Web Proxy Failed to Initialize
253131 How to Install Proxy 2.0 on Windows 2000
Keywords: kbbug kbenv kberrmsg kbpending KB252942