Article ID: 841394
Article Last Modified on 12/1/2005
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2000 Desktop Engine (Windows), when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 7.0 Standard Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2005 Developer Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2005 Enterprise Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2005 Express Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2005 Standard Edition, when used with:
- Microsoft Windows XP Service Pack 2
- Microsoft SQL Server 2005 Workgroup Edition, when used with:
- Microsoft Windows XP Service Pack 2
SYMPTOMS
You may not be able to connect to an instance of Microsoft SQL Server 7.0, to an instance of Microsoft SQL Server 2000, to an instance of Microsoft SQL Server 2000 Desktop Engine (also known as MSDE 2000), to an instance of Microsoft SQL Server 2005, or to an instance of Microsoft SQL Server 2005 Express Edition, and you may receive one of the following error messages.
Error message 1
Error message 2
This behavior occurs when all the following conditions are true:
- You try to connect to an instance of SQL Server or to an instance of MSDE 2000 that is installed on a computer that is running Microsoft Windows XP Service Pack 2 (SP2).
- You try to connect to an instance of SQL Server that is configured to listen on the TCP/IP server network library only.
CAUSE
By default, Windows Firewall is turned on when you install Microsoft Windows XP Service Pack 2. Because Windows Firewall blocks the TCP/IP ports that allow network connections to an instance of SQL Server or to an instance of MSDE 2000, you may not be able to connect to an instance of SQL Server when SQL Server is configured to listen on the TCP/IP server network library only.
WORKAROUND
To work around this problem, you must explicitly enable TCP/IP connectivity for SQL Server.
For additional information about how to enable SQL Server connectivity over TCP/IP manually, click the following article numbers to view the articles in the Microsoft Knowledge Base:
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server 2000
841823 How to manually enable TCP/IP for SQL Server 7.0 on a computer that is running Windows XP Service Pack 2
For additional information about how to enable SQL Server connectivity over TCP/IP programmatically, click the following article number to view the article in the Microsoft Knowledge Base:
839980 How to use a script to programmatically open ports for SQL Server to use on systems that are running Windows XP Service Pack 2
841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
STATUS
This behavior is by design.
REFERENCES
For additional information about dynamic and static port allocation in SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
823938 How to use static and dynamic port allocation in SQL Server 2000
For additional information about Internet firewalls, click the following article number to view the article in the Microsoft Knowledge Base:
308127 How to manually open ports in Internet Connection Firewall in Windows XP
For additional information about configuring SQL Server 2000 and Windows XP SP2, click the following article number to view the article in the Microsoft Knowledge Base:
841249 How to configure Windows XP Service Pack 2 (S) for use with SQL Server
Additional query words: Springboard TCP/IP connectivity client connections ICF
Keywords: kbfirewall kbconnectivity kbsqlclient kbnetwork kbclientserver kberrmsg kbprb KB841394
