why suddenly need to change option "remote connection" from off to on?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

i installed sql server express 2005. Everything worked good until yesterday
...
Indeed, since yesterday and for an unknown reason, i get this error when
attempting to login via Management Studio:

An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 28 - Server doesn't support
requested protocol) (Microsoft SQL Server, Error: -1)

Now, i know how to solve this: putting the option 'Remote connections'.
But i want to know why i suddenly has to change that option in order to get
in Management Studio.
Here are the settings:

- i login with authentification mode.
- The sql browsing service is started
- following sql client native protocols are enabled: shared memory, tcp/ip,
named pipes
- following sqlexpress protocol is enabled: shared memory

I still can login in with sqlcmd (i mean with remote connections off).

Thanks for help
Mark


.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... connections need to be returned to the pool to be ... Enterprise version of SQL Server 2000. ... server user login to be sure that it is not mixed with other running clients). ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... an Access database in former times this was a lot of work which took me ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... client for programming easy, fast and good applications. ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... communication between ODBC (OLEDB and Native Client, ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL server connection problem
    ... I've tried to change the user connections to 0, ... "SQL server connection time out. ... The following message appears when restart the server and before login ... I receive Error message: “A connection could not be established to ...
    (microsoft.public.sqlserver.clients)