Microsoft KB Archive/324288

= NAT Clients Cannot View Web Sites After You Install SQL 2000 SP2 or SP3 on an RRAS Server =

Article ID: 324288

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 1, when used with:
 * Microsoft SQL Server 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 3, when used with:
 * Microsoft SQL Server 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2, when used with:
 * Microsoft SQL Server 2000 Service Pack 2

-



This article was previously published under Q324288



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



SYMPTOMS
After you install service pack 2 or service pack 3 for SQL Server 2000 on a Windows 2000 Server-based computer, only portions of a Web page may load on client computers. Note that the Windows 2000 Server-based computer must be running Routing and Remote Access with Network Address Translation (NAT) turned on, or only Internet Connection Sharing (ICS). In most cases, text is displayed, but images and embedded objects do not load properly. However, you can view Web pages from the Routing and Remote Access/NAT server. Another symptom of this problem occurs with FTP connections through NAT. To determine if this is the case, run Network Monitor traces on the WAN interface of Routing and Remote Access. You will see follow-on PORT commands are not edited correctly by the NAT FTP editor.



CAUSE
During the SQL Server 2000 Service Pack 2 (SP2) installation or the SQL Server 2000 Service Pack 3 (SP3) installation, the installation script sets a global TCP/IP parameter in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts

The script sets the value to 1433-1434. The Windows 2000 NAT driver reads this key and limits the outgoing NAT TCP/UDP source port mappings to this range. When this range is limited to two IP addresses, the symptoms that are listed earlier in this article occur.



RESOLUTION
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.

Start Registry Editor (Regedt32.exe), and then delete the ReservedPorts value in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Quit Registry Editor, and then restart the Windows 2000 RRAS server.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbenv kbnofix KB324288

-

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

© Microsoft Corporation. All rights reserved.