Article ID: 823492 - Last Review: October 26, 2006 - Revision: 4.4 "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.0On This PageSYMPTOMSWhen you connect to a Windows NT 4.0-based computer that is running either Microsoft SQL Server 2000 or Microsoft SQL Server 7.0, you may receive an error message that is similar to one of the following: Connection could not be established. SQL Server does not exist. -or- Connection could not be established. Access is denied. CAUSEThis problem may occur if all the following conditions are true:
RESOLUTIONUpdate InformationDownload InformationThe following file is available for download from the Microsoft Download Center:Windows NT 4.0 ServerCollapse this image ![]() Windows NT 4.0 Terminal Server EditionCollapse this image ![]() 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: 119591
(http://support.microsoft.com/kb/119591/EN-US/
)
How to Obtain Microsoft Support Files from Online Services
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.
PrerequisitesThis update requires Windows NT 4.0 Service Pack 6 (SP6) or Windows NT 4.0 Service Pack 6a (SP6a).Update Replacement InformationThis update does not replace any other updates.File InformationThe 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 ServerDate Time Version Size File name ---------------------------------------------------- 25-Jun-2003 09:03 4.0.1381.7220 38,736 Npfs.sys Windows NT 4.0 Terminal Server EditionDate Time Version Size File name ---------------------------------------------------- 25-Jun-2003 09:06 4.0.1381.33548 38,608 Npfs.sys To Activate the UpdateAfter 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:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager To do so, follow these steps.Important 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 Windows
STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. APPLIES TO
| Article Translations
|
Back to the top

