connection error

  • I am trying to connect to another sql server from one sql server getting below error

    TITLE: Connect to Server

    ------------------------------

    Cannot connect to server.

    ------------------------------

    ADDITIONAL INFORMATION:

    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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

  • It's a connection issue as stated. Can you connect from another workstation/client? Are you allowing connections remotely? What protocol are you using, and how are you connecting from the SQL Server?

  • Steve Jones - Editor (11/12/2009)


    It's a connection issue as stated. Can you connect from another workstation/client? Are you allowing connections remotely? What protocol are you using, and how are you connecting from the SQL Server?

    no

    allowed remote connections

    tcp/ip

    connecting thru SSMS

  • OK, if you are using SSMS, you are not connecting from one SQL Server to another. SSMS is a client.

    How are you putting in the connection string and are you sure that service is running? If you log onto the host running SQL Server, can you connect with SSMS from there using "(local)" or "127.0.0.1" as the server name?

  • We have two servers

    production and DR server(planning to set up logshipping)

    In both servers sql server std edition is installed, both are in same workgroup and no firewall and all ports are open

    I am trying connect DR server from Prod server thru SSMS. Getting below error

    DR server ip is pinging in prod server and

    1433 port is connected

    Remote connections are allowed in DR server and network ports are enabled. In both servers SQL Server services running under local system account.

    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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

  • HOW are you connecting? SQL Auth, Windows Auth, what are you typing in SSMS? That is some of the information we need to help you solve this.

    The windows machine you are using is a client when you connect to SQL Server. If you say "I'm connecting from one SQL Server to another" that implies a Linked Server, which configures differently. That's the reason for the questioning. So we can speak the same language.

    The connections are fairly simple. Can you log onto the DR server and connect to the DR SQL Server instance?

  • Steve Jones - Editor (11/13/2009)


    HOW are you connecting? SQL Auth, Windows Auth, what are you typing in SSMS? That is some of the information we need to help you solve this.

    The windows machine you are using is a client when you connect to SQL Server. If you say "I'm connecting from one SQL Server to another" that implies a Linked Server, which configures differently. That's the reason for the questioning. So we can speak the same language.

    The connections are fairly simple. Can you log onto the DR server and connect to the DR SQL Server instance?

    trying connect thru windows authentication

    tried with servername

    ip

    ip,1433

    servername.1433

    I am able to connect to DRSSMS in DR server with window auth

  • The error shows you are connecting with named pipes. You might have something changed in your SSMS connection dialog. Double check all settings that you are using TCPIP.

    Also, the name and password must exist on both Windows machines if you are in a workgroup. It must be the same for Windows Auth to work. I'd use a SQL Auth account to test a connection as well to eliminate Windows issues.

  • Steve Jones - Editor (11/13/2009)


    The error shows you are connecting with named pipes. You might have something changed in your SSMS connection dialog. Double check all settings that you are using TCPIP.

    Also, the name and password must exist on both Windows machines if you are in a workgroup. It must be the same for Windows Auth to work. I'd use a SQL Auth account to test a connection as well to eliminate Windows issues.

    I will double check tcp/ip settings and let you know

    I found one strange thing.....In prod server ssms i tried to connect dr sql server using DR server ip, it connected but servername is prod servername...same thing happens in DR server also

    DR IP(sql server 9.00.1399-prod servername\adminstrator)

    and it is not in started symbol(green)

  • chk2009 (11/13/2009)


    Steve Jones - Editor (11/13/2009)


    The error shows you are connecting with named pipes. You might have something changed in your SSMS connection dialog. Double check all settings that you are using TCPIP.

    Also, the name and password must exist on both Windows machines if you are in a workgroup. It must be the same for Windows Auth to work. I'd use a SQL Auth account to test a connection as well to eliminate Windows issues.

    I will double check tcp/ip settings and let you know

    I found one strange thing.....In prod server ssms i tried to connect dr sql server using DR server ip, it connected but servername is prod servername...same thing happens in DR server also

    DR IP(sql server 9.00.1399-prod servername\adminstrator)

    and it is not in started symbol(green)

    TCP/IP port is enable and 1433 is listening

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply