RE: Problems connecting to MSDE server

From: Rob Beene [MSFT] (rbeene_at_online.microsoft.com)
Date: 02/28/04 

Date: Sat, 28 Feb 2004 10:52:53 GMT

Hey,

Thank you for your post regarding unable to connect to SQL Server. As Ed
mentioned in his response, the most likely cause is because the protocols
are disabled by default for security reasons. However, even though you
didn't specify to enable protocols when installing, you do not necessarily
have to reinstall MSDE in order to make this change. You can optionally
run svrnetcn.exe which will bring up the Server Network configuration
utility and you can enable the appropriate protocols such as TCP/IP and/or
Named Pipes. Once you do this, you also need to enable the client
configuration to also use the same protocols. You do that by running
cliconfg.exe.

You may or may not have these programs on your machine. If you do not have
them, then you will likely need to uninstall and reinstall using the
Disableprotocols=0 as Ed suggested or optionally install the client tools.
The client tools ship with a full copy of SQL Server, if you have access to
the cd or you can get them from the evaluation cd by going to
http://www.microsoft.com/sql/evaluation/trial/default.asp.

I hope this helps.

Sincerely,

Rob Beene, MCSD, MCDBA
Microsoft SQL Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • TCP/IP and security
    ... I need to change the protocols settings during installation or, ... is selected as the default port instead ... - whatever port I say to SQL Server to use, ... STILL do not use it!(errorlog after service start lists the protocols used, ...
    (microsoft.public.sqlserver.security)
  • Re: Can I Upgrade
    ... I installed MSDE and configured it as I told you previously and I'm able to connect to that instance from another machine. ... Last guess is you are configuring this port setting for another instance of SQL Server. ... First and foremost is the fact that MSDE2000 will not start the protocols TCP/IP or Named Pipes. ...
    (microsoft.public.sqlserver.setup)
  • Re: Can I Upgrade
    ... Yes I am using the program svrnetcn to configure the protocols. ... As you can see SQL server is only listening on Shared Memory ... So the big question of the day is why is Named Pipes and TCP/IP not ... Microsoft SQL Server 2000 Developer Edition. ...
    (microsoft.public.sqlserver.setup)
  • Re: Cant connect
    ... choose your SQL Server 2000 instance from the list and ensure that TCP/IP or Named Pipes protocol are in the Enabled protocols list. ... Then you can use this info to connect to this instance and to add this port to the exception list of Windows Firewall or any other firewall utility if there is any. ... Open up this utility where you SQL Server instance is installed and then go to SQL Server Network Configuration and choose your instance name then enable protocols accordingly. ...
    (microsoft.public.sqlserver.connect)
  • Re: error on conn.open()
    ... ugg helps when i have the; in the connection string... ... and i did not find the "Protocols for MSSQLSERVER" then enable the ... SQL Server 2005 Open SQL Server Configuration Manager. ... 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the ...
    (microsoft.public.dotnet.languages.csharp)