Suggestions:
1. You didn't specifically say that the SQL Server Browser Service was
running on the SQL Server Express computer. SQL Server Express Setup
configures it to start by default but who knows. Maybe the password expired
or something.
2. Since your error says DBNetLib, I infer that your clients are using the
SQL Server 2000 client network library. Consider upgrading them to the SQL
Server 2005 "SQL Server Native Client". The SQL Server Native Client knows
all about the SQL Server Browser Service which provides the connection point
(ie. port number or named pipe) back to the client.
3. Since you are connecting using DBNetLib, check the Client Configuration
Tools on one of the clients. What protocol is it using? You probably want
TCP. Then test a connection using the connection string tcp:<computername>,
<fixed port number>
If that's not working, then either the server is not listening on TCP (which
really can't be the case since you set a fixed port) or maybe the IP Address
can't be resolved. Try connecting to: tcp:<ipaddress>, <portnumber>
If your clients are trying to connect using named pipes, then maybe name
resolution isn't working.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Klerman Gutierrez" wrote in message
> Using OSQL or SQLCMD now I can connect to the SQL Server Express in the
> same machine where de SQL Server Express is installed, but it fails trying
> to connect to it from any other machine in my network.
> The error message I get is:
> [DBNetLib] Not valid connection
> [DBNetLib]ConnectionOpen InvalidInstance()
> I have SQL Server 2000 installed in another computer, and I can connect to
> it from any other machine including the one where the SQL Server Express
> is installed.
> Any suggestion where to check, please ?
>
> TVMIA,
>
> Klerman Gutierrez
>
>
> >> Stay informed about: SQLCMD can't connect to SQL Server Express SP2 
FAQ
Search
Profile
Private Messages
Log in
