Re: Connecting to a SQL Server 2005 Instance

When I connect to the default instance from a remote client using SQL
Server 2005 Management Studio it is:

Server type: Database Engine
Server name: Server1
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Works as expected

Whn I connect to the named instance from the same remote client using
SQL Server 2005 Management Studio it is:

Server type: Database Engine
Server name: Server1\server1test
Authentication: SQL Server Authentication
Login: sa
Password: mypassword
Result: Fails





On Jan 25, 12:12 pm, "William \(Bill\) Vaughn"
<billvaRemoveT...@xxxxxxxxxx> wrote:
Let's see your ConnectString.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speakerwww.betav.com/blog/billvawww.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visitwww.hitchhikerguides.netto get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
---------------------------------------------------------------------------­--------------------------------------------

"robboll" <robb...@xxxxxxxxxxx> wrote in messagenews:1169744212.563385.41730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



I completed a default install that uses the server name: Server1
and completed an instance install on Server1 called Server1test with
the same users, etc.

I can connect remotely to Server1 using SQL Server 2005 Management
Studio, but when I try to connect to Server1\Server1test I get:

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: 26 - Error
Locating Server/Instance Specified) (Microsoft SQL Server)

If I can connect to Server1 using the SA account why is it not allowing
the named instance (i.e., Server1\Server1test) to connect? While at
Server1 I can connect to Server1\Server1test using the SA account.

Thanks for any suggestions.

RBollinger- Hide quoted text -- Show quoted text -

.

Relevant Pages

  • RE: Confusion on standard security methodologies.
    ... Application will talk to a back-end SQL ... By "back-end," I assume you mean on a different box from IIS? ... If SQL is on a separate box, you won't be able to use NT authentication ... impersonations (meaning that once passed to the IIS server, ...
    (microsoft.public.inetserver.iis.security)
  • Re: IIS6 Authentication Problem with SQL Server 2000
    ... They're not accessing SQL directly right? ... > a) if you are using a Windows 2000 Domain, ... > backend SQL Server. ... You need to use Kerberos authentication for this (not ...
    (microsoft.public.inetserver.iis.security)
  • Re: Security Update for SQL Server 2000 Service Pack 4 (KB948110)
    ... log into SQL Server. ... Authentication) The other is SQL Authentication where, ... the 948110 hotfix will not work on a database server ...
    (microsoft.public.windowsupdate)
  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)
Loading