Very Computer

I'm trying to connect from a client pc to the SQL server 6.5 on LAN.
this is what I got when trying to create a System DSN on the client to use
th ODBC:

Connection failed:
SQLState:'08001'
SQLServer Error:58
[Microsoft][ODBC SQL Server Driver][DBNMPNTW]ConnnectionOpen(CreateFile()).
Connection failed:
SQLState:'01000'
SQLServer Error:58
[Microsoft][ODBC SQL Server Driver][DBnMPNTW]ConnectionOpen(CreateFile()).

what can I do to connect/resolve this error?
I need DSN to connect through my web application build with VI  6.0 on the
client side.

anyone please help me here,

thanks a lot in advance,
 Steven

Hi Steve,

First be sure that the Server is up and running.

Check the network libraries on the client side DSN.  Try setting the network
libraries to Named Pipes/ TCP/IP and see what happens.  To set the Network
Libraries, on the 3rd page of the DSN wizard, select "Client Configuration"
and select "Named Pipes" there and see what happens.

Also, Check your logon permissions, if not trying to connect as SA

Btw, Server is not configured for trusted connections, right ?

thanks
* Madhu
All Opinions expressed are mine and only Mine.

my problem lies in the SQL server authetication...I fixed it there...not
matter with NT server or IIS server
:)

I'm trying to connect Access97 to a Sybase database on a Linux machine using
SQL Server v.3.60.0319 (file SQLSRV32.dll, updated 6/12/98).  I usually get
a connection timed out message (or the same message you got), and when I do
connect, Access hangs when opening a linked table that contains more than a
couple hundred records.  I also got a version incompatability message in the
error log.  I ran the instcat.sql script on the server to fix this and it
did not help.  Different computers seem to perform differently... one of
them never gets a connect failure message, although Access still hangs when
opening a linked table.  Another computer gets the failure message every
other time (alternating).  I am unable to open a recordset using Access VB,
although sometimes I can open small tables manually and edit their values.
I can open a recordset using MFC's CDatabase and CRecorset classes.
Sometimes I get the connect fail message, but it eventually works, and I can
open and traverse the recordset reliably with no errors.  However, I can
only open a read-only forward snapshot; otherwise, I get an error that the
ODBC driver does not support that kind of recordset (dynaset, dynamic, or
snapshot), which seems odd to me.  If you find anything out, please let me
know.

My advice is to try another computer.  Also, you may connect successfully 1
in every 30 tries or so. You might be able to retry in a loop, which is what
I do.

Search the Microsoft support for ASP by the keyword "80004005"

Hi, Check and see if this article is useful.
---------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft SQL Server version 6.5
 - Microsoft SQL Server, Enterprise Edition, version 6.5
---------------------------------------------------------------------------

SYMPTOMS
========

The following error message is returned from the ODBC Data Source
Administrator and/or an ODBC application while attempting to make a
connection to SQL Server:

   Connection failed:
   SQLState: '08001'
   SQL Server Error: 11
   [Microsoft][ODBC SQL Server Driver][DBMSSOCN] General Network error.
   Check your documentation.

   Connection failed:
   SQLState: '01000'
   SQL Server Error: 10061
   [Microsoft][ODBC SQL Server Driver][DBMSSOCN]ConnenctionOpen(connect())

CAUSE
=====

The most common reason that this connection attempt failed is that this DSN
or ODBC data source attempted to make a connection using the TCP/IP sockets
Net-Library, which is Dbmssocn.dll. Because the SQL Server is not listening
for incoming connections for TCP/IP sockets clients, the connection fails.
From ISQL/w, the second error message stated above would be returned. The
OS Error is 10061, and the function call that failed was
ConnectionOpen(connect()).

WORKAROUND
==========

By default, SQL Server will listen for incoming connections made by Named
Pipes clients. Named Pipes is the default IPC mechanism for clients to
connect to a SQL Server version 4.2, 6.0, and 6.5 server. The Named Pipes
DLL is Dbnmpntw.dll, and it should be located in the Windows\System or
Winnt\System32 directory. The most common resolution to this problem is to
configure the client computer to connect using Named Pipes.

Configuring Named Pipes
-----------------------

If the Microsoft Data Access Components (MDAC) ODBC drivers have been
installed on the computer, you can make this change in the second step of
the Create New Data Source wizard.

NOTE: You can download MDAC drivers from http://www.microsoft.com/data.

To configure the client, start the Create New Data Source wizard, click the
Client Configuration button, and perform the following steps, based on the
version of the SQL Server ODBC driver you are using:

   For SQL Server ODBC Driver version 3.50
   ---------------------------------------

   1. Click the Net Library tab and use the drop down list box to set the
      default network (Net Library) to Named Pipes.

   2. On the Advanced tab, remove any advanced entries that reference the
      server you are connecting to.

   3. Click Done.

   For SQL Server ODBC Driver version 3.70
   ---------------------------------------

   1. In the Network Libraries section of the Edit Network Library
      Configuration dialog box, select Named Pipes.

   2. Click OK.

If you do not have the MDAC ODBC drivers installed, you can use the SQL
Server Client Configuration Utility tool to set the default Net-Library to
Named Pipes. You can install the client utilities from the SQL Server CD
from the i386 directory.

MORE INFORMATION
================

This topic is also discussed in a troubleshooter available at the following
location:

   http://support.microsoft.com/support/tshoot/tshooterlist.asp?PR=sql

Additional query words: Win95 datasource open database connectivity netlib

Driver][DBNMPNTW]ConnnectionOpen(CreateFile()).

Quote:>> Connection failed:
>> SQLState:'01000'
>> SQLServer Error:58
>> [Microsoft][ODBC SQL Server

Driver][DBnMPNTW]ConnectionOpen(CreateFile()).