"Connection Could Not Be Established" Error Message When You Connect to a Windows NT 4.0-Based Computer That Is Running SQL Server 2000 or SQL Server 7.0 (823492)

RESOLUTION

Update Information

Download Information

The following file is available for download from the Microsoft Download Center:
Windows NT 4.0 ServerDownload the 823492 package now.Windows NT 4.0 Terminal Server EditionDownload the 823492 package now.

Release Date: July 23, 2003

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Prerequisites

This update requires Windows NT 4.0 Service Pack 6 (SP6) or Windows NT 4.0 Service Pack 6a (SP6a).

Update Replacement Information

This update does not replace any other updates.

File Information

The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Windows NT 4.0 Server

Date         Time   Version        Size    File name
----------------------------------------------------
25-Jun-2003  09:03  4.0.1381.7220  38,736  Npfs.sys

Windows NT 4.0 Terminal Server Edition

Date         Time   Version        Size    File name
----------------------------------------------------
25-Jun-2003  09:06  4.0.1381.33548 38,608  Npfs.sys

To Activate the Update

After you install the update on the server, you must edit the registry to activate the update. After you do so, users can connect to the server by using named pipes. To activate the update, add the EnhancedSecurityLevelNamedPipes registry value to the following registry key, and then set the value to 1:To do so, 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.

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry entry:

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager

   Note Look at the key carefully. There may be a key named SessionManager (no space) rather than Session Manager (with a space). Do not use the SessionManager key; only use the Session Manager key.
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type EnhancedSecurityLevelNamedPipes, and then press ENTER.
6. On the Edit menu, click Modify.
7. In the Value data box, type 1, and then click OK.
8. Quit Registry Editor.
9. Restart the server.