Re: Error while connecting remote SQL server

I suggest reading my whitepaper on connecting. See www.betav.com/blog/billva http://betav.com/blog/billva/2006/06/getting_and_staying_connected_1.html
While it looks like you've been working through the issues, the paper might help identify a few more.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Gujju............" <Gujju............@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:BD15121C-6646-41A4-8E58-5B67D70E0455@xxxxxxxxxxxxxxxx
I faced the same problem. I wasted almost a week. Finally I got the solution.
There are so many reasons behind the same problem.
One of then is as below.

There might be possoble you have defined aliases for the SQL server in your
machine.

To check the alias :

Go to Control Panel -> Administrative Tools -> Computer Management : Open It

Expand Services And Application-> SQL Server Configuration Manager->SQL
Native Client Configuration

Check Aliases Option Under.

If you find any aliases for the SQL Server that you are getting problem.
Delete it for time being and test it.

For me it works hope that will help you too. Thanks.



"shivaranjaniadimulam21@xxxxxxxxx" wrote:

hi all,
I trying to connect remote sql server from my machine. but
it giving me some errors

Here are few errors listed,
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
connection to SQL Server))

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, Error: -1)

A connection was successfully established with the server, but then
an error occurred during the pre-login handshake. 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: 0 - No process is on the other
end of the pipe.) (Microsoft SQL Server, Error: 233)

A connection was successfully established with the server, but then
an error occurred during the login process.(provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.)

To solve this problem I did following changes in SQL server

Enable the TCP/IP protocol using the Surface Area Configuration
Utility
Make sure the TCP/IP protocol is enabled in the SQL Server
Configuration Utility
start SQL Server browser
Exceptions are added in Firewall
Restart the computer

But still I am getting same errors.
Please give me some solution for this problem....
Thanks in advance.



.

Relevant Pages

  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... remote connection. ... should I just check named pipes only or both TCP/IP and ... I understand that you encountered the ODBC error message on your ecommerce ... TCP/IP protocol to your SQL Server instance by calling conn.Open, ...
    (microsoft.public.sqlserver.connect)
  • Re: Classic ASP connectionstring to SQL Server 2005
    ... So this connection string is in the VB6 dll? ... What is the error message? ... Provider cannot be found. ... can you ping the sql server? ...
    (microsoft.public.inetserver.asp.db)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Express slow when connecting from client on network.
    ... connection to Named Pipes, ... Perhaps your SQL Server Native Client on the XP computer is ...
    (microsoft.public.sqlserver.clients)