Re: Cannot connect with one machine but can with others

Tech-Archive recommends: Fix windows errors by optimizing your registry

Try using TCP/IP instead of Named Pipes. Enable them and use a TCP/IP
address. You can also add the prefix tcp: to denote that TCP/IP should be
used and also add the port address ( ,1433 is the default port if you're not
using dynamically allocated port and the sql-server is not hidden to the
browsing service).

There is also the situation where the remote instance is not the default
instance but a named instance. In this case, you should try adding its name
after the address; such as \\RemoteServer\SQLExpress2005.

It's possible that you might be blocked by a firewall. Can you ping the
remote machine from the windows server?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Joe" <jbassking@xxxxxxxxxxxxxxx> wrote in message
news:%23VMwRclTJHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I'm having a strange problem here. I'm trying to connect to a remote SQL
Server database but I keep getting this error:
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)

I can connect using other machine just not the one I want to. The machine
I'm trying to connect with is a Windows 2003 Server running SQL Server
2005.

I sort of think it may be getting confused and thinks I'm trying to
connect
locally.

I even tried to connect using the SQL Server Management Studio but I get
the
same error.

I set Named Pipes to enabled in the SQL Server Config.

I posted this same message in microsoft.public.dotnet.framework.adonet
yesterday. Unfortunately I'm didn't get an answer to fix the problem.

Any ideas?

Thanks,
Joe



.

Relevant Pages

  • Re: SQL 2008 vs 2005 performance issue
    ... Named Pipes is third in the order of network protocols. ... The SQL Server 2005 machine is using TCP/IP. ... The SQL Server 2008 machine is using Named Pipes. ... I installed SQL Server 2008 Enterprise Eval on my new Toshiba Centrino Duo ...
    (microsoft.public.sqlserver.setup)
  • RE: [ODBC SQL Server Driver][Shared Memory]ConnectionWrite (send()
    ... the ODBC source using named pipe, but I don't know how to enable named pipes ... If it is not working I am going to use ado to connect to sql server. ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.connect)
  • Re: Connect to SQL Sererv thru Named Pipes
    ... to acced SQL Server via Named Pipes from VB 6. ... The DBMSSOCN tell the OLEDB driver to use TCP/IP instead of the default ... There are pros and cons as normal for which protocol to use however IMO ...
    (microsoft.public.vb.general.discussion)
  • Re: Connect to SQL Sererv thru Named Pipes
    ... >> Ijust wanted to know how to configure the SQL Server to use Named Pipes ... In order to use TCP/IP protocols you need to ... > There are pros and cons as normal for which protocol to use however IMO ...
    (microsoft.public.vb.general.discussion)
  • Re: SQL 2005 Remote Connection Error
    ... Has the SQL Server service been stopped and restarted since you enabled TCP/IP or named pipes? ... Use the remote desktop and check the SQL Server error log. ... Configuration for Services And Connections for the Remote Connections setting ...
    (microsoft.public.sqlserver.connect)