Re: Cannot connect with one machine but can with others

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

Most likely a firewall problem on the Windows Server. It's also possible
that you have defined an alias or an ODBC DSN on the machines that do work
but that you forgot to do the same on this machine.

There is also the possibility that the driver that you are trying to use is
not installed on this particular Windows server. For example, installing
SQL-Server 2005 will install the Native ODBC driver for SQL-Server and the
Native OLEDB Provider for SQL-Server. However, I'm not sure that you would
receive this error message if this was the case here.

What parameters are you using for connecting?

--
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:u9D4G7lTJHA.5812@xxxxxxxxxxxxxxxxxxxxxxx
Here's some more info:
The database server is not local so all our connections have to go out of
our network. I cannot make any changes to the server since it's not ours.

I can ping by name the database server from all computers even the one
that doesn't work.

I can also telnet the server from the machines that do work but cannot
telnet from the machine that doesn't work. I tried both the name and the
IP.

The server I'm trying to connect to is 2000. I have 2005 installed on the
server that I'm trying to connect with. I don't know if this makes any
difference but I think it's the only difference between all the computers
that can connect and this one that cannot.

I'm able to connect with a XP machine and a 2003 server. The machine that
cannot connect is also a 2003 server.

I hope this extra info helps some.

"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:%23NIxA2lTJHA.1332@xxxxxxxxxxxxxxxxxxxxxxx
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: how to find "step by step" articles to learn windows 2003 AD?
    ... Sites by Using ISA Server in Windows 2000 and Windows 2003" ... Additional Help Files for Windows Server 2003" ... http://support.microsoft.com?kbid=323360 "How to install and configure a DHCP ... http://support.microsoft.com?kbid=323381 "HOW TO Allow Remote Users to Access ...
    (microsoft.public.win2000.advanced_server)
  • RE: SQL Connection with ASP.net
    ... in the same machine, but when connectiong to another server error msg occure, ... Remote connections are not the same as ... Once you have that out of the way, connecting to the remote ... Computer name 'Server' and its already installed sql server 2005, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Installation Failure - Error Code 0x80244018
    ... You experience problems when you access the Windows Update Version 6 Web site through a server that is running ISA Server ... .101 is pruned out due to potential supersedence ... [CallerId = MicrosoftUpdate] ...
    (microsoft.public.windowsupdate)
  • RE: Backups, VSS and SBS2003 HELP NEEDED!!!
    ... suggest customers Only install Windows Server 2003 SP1 on their server. ...
    (microsoft.public.windows.server.sbs)
  • VPN TCP/IP CP reported error cp 31
    ... I am running a Windows Server 2000 - SP4. ... be setup properly - clients can happily connect, ... Error Connecting to ...
    (microsoft.public.win2000.ras_routing)