RE: Connet to MS SQL Express

Hi Peter,
I understand that you could not connect to your SQL Server 2005 Express
instance from SSMS due to the pre-login handshake error.
If I have misunderstood, please let me know.

Generally regarding the pre-login handshake connection error, it is often
caused by either of the following two conditions:
1. SQL Server 2005 is not configured to accept remote connections.
2. The necessary protocols for SQL Server 2005 are not enabled on either
the SQL Server 2005 computer or the SQL Server 2005 client computer.

For server side, I recommend that you check the following:
1. Use the SQL Server Surface Area Configuration tool to enable remote
connections for SQL Server 2005 on the SQL Server 2005 computer:
Click Start, point to Programs, point to Microsoft SQL Server 2005, point
to Configuration Tools, and then click SQL Server Surface Area
Configuration.
Click Surface Area Configuration for Services and Connections.
Click to expand MSSQLSERVER, click to expand Database Engine, and then
click Remote Connections.
Click to select Local and Remote Connections, click to select Using both
TCP/IP and named pipes, and then click OK.
Close the SQL Server Surface Area Configuration tool.

2. Use the SQL Server Configuration Manager tool to enable the TCP/IP and
the Named Pipes protocols on the SQL Server 2005 computer:
Click Start, point to Programs, point to Microsoft SQL Server 2005, point
to Configuration Tools, and then click SQL Server Configuration Manager.
Click to expand SQL Server 2005 Network Configuration and then click
Protocols for MSSQLSERVER.
Right click the TCP/IP protocol and then click Enable.
Right click the Named Pipes protocol and then click Enable.
Close the SQL Server Configuration Manager tool.

For client side, I recommend that you open SQL Server Configuration Manager
to enable TCP/IP and Named Pipes protocols on your SQL Server 2005 client
computer:
Click Start, point to Programs, point to Microsoft SQL Server 2005, point
to Configuration Tools, and then click SQL Server Configuration Manager.
Click to expand SQL Server 2005 Network Configuration and then click Client
Protocols.
Right click the TCP/IP protocol and then click Enable.
Right click the Named Pipes protocol and then click Enable.
Close the SQL Server Configuration Manager tool.

If the above methods do not work, I recommend that you check if Firewall
was enabled on your server, you can check it via running firewall.cpl from
command prompt. You may disable the firewall or add your SQL Server program
name and SQL Server Browser program name to the exception list. Please also
ensure that SQL Server Browser service was started. You can check your SQL
Server process path and SQL Server Browser path by double clicking the
services in Services list. You may also refer to this article:
How to: Start and Stop the SQL Server Browser Service (SQL Server Express)
http://msdn.microsoft.com/en-us/library/ms165734.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
=========================================================










.

Relevant Pages

  • RE: Enable remote connections without Management Studio
    ... connection. ... sql server configuration manager can do this task for you. ...
    (microsoft.public.sqlserver.connect)
  • RE: Cannot connect to remote Sql Server 2005
    ... Start SQL Server Configuration Manager in the Start Menu -> Microsoft ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.clients)
  • Re: Udpate KB948109
    ... request as suggested but got an email back suggesting I look on this ... incorrectly in SQL Server. ... with SQL Server Configuration Manager. ...
    (microsoft.public.windowsupdate)
  • Re: Connecting to an instance in a cluster
    ... I am in SQL Server Configuration Manager, ... You cannot use port 1434 or 1433. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Connet to MS SQL Express
    ... I understand that you could not connect to your SQL Server 2005 Express ... to Configuration Tools, and then click SQL Server Configuration Manager. ...
    (microsoft.public.sqlserver.connect)
Loading