Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Local Machine User Account ODBC Connection Problem

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-01-03 : 12:01:01
Paul Brandon writes "We've created a System DSN ODBC connection to our SQL Server that works fine when we're logged onto the box with a domain account. When we log in with a local machine account, however, the connection fails (and we really need people to be able to log in this way---they won't all have domain accounts). We've tried all of what seems like the obvious troubleshooting things with no change:

1. Log in with a local machine Administrator account.
2. Use the SA account for the DSN login info.
3. Checked the "client connections" tab (TCP/IP & named pipes).
4. Ping the server, use a fully qualified name for the server, use the I.P. address of the server, etc....

The exact error message is:

Connection failed:
SQLState: '01000'
SQL Server Error: 1326
[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect())
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

(Note: Same message with TCP instead of Named Pipes)

*** NOTE: This does not appear to be a SYSTEM problem (i.e. some boxes (same O/S, etc...) CAN connect this way but others don't). We just can't seem to nail down what is the common thread on the non-working ones.

Any ideas??? Thanks.

Paul."

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-01-03 : 12:34:47
This is not an account issue. The error message that you are getting means that the client machine can not even get to the SQL Server. To fix this, you could create an alias in the Client Network Utility. If the client machine does not have this utility, then it can be done on the second screen of the DSN configuration. Just click on client configuration and fill out the necessary fields.

Go to Top of Page
   

- Advertisement -