February 6, 2006 at 10:10 am
I have a domain.
I have a SQL Server on the domain.
I have create a local user account on a domain computer.
When I log into that local user account, I cannot connect to the SQL Server.
When I log into the computer with a domain account, I can connect to the SQL Server.
In each case, I'm trying to connect via ODBC or BDE with a SQL Server authenticated user.
Why?
February 6, 2006 at 10:16 am
Because the local user accounts aren't validated by the domain controller -> untrusted.
February 6, 2006 at 10:55 am
Even if I'm trying to use a SQL Authenticated login.
This doesn't make sense to me.
February 6, 2006 at 10:59 am
That can be the case when SQL Server is set to Windows Authentication only.
In mixed mode you can login with a userid/password.
February 6, 2006 at 11:05 am
SQL Server is set to 'SQL Server and Windows' authentication.
Also, I just re-tested the ODBC connection and that works fine. It is just the BDE that won't connect.
February 6, 2006 at 12:18 pm
I have also made the local account part of the local administrators group and I will can't connect via BDE.
This is really starting to bother me, it shouldn't be this difficult.
Matt
Edited to add:
I was able to switch the connection to ADO and that is now working.
I would just like to figure out why I couldn't connect via the BDE. It doesn't make sense.
February 6, 2006 at 1:32 pm
What is BDE you are talking about?
So Ado works with sql authentication?
February 6, 2006 at 2:35 pm
Yes, ADO works w/ SQL Authentication when logged in with a local acct.
And ODBC works w/ SQL Authentication when logged in with a local acct.
BDE is Borland Database Engine. Application was written using Delphi and connects to the database via the BDE.
February 7, 2006 at 1:54 am
First some questions.
1. What version of SQL Server?
2. What error message(s) are you getting?
3. Are you connecting to a default or named instance of SQL Server?
4 What does the connect string look like for this BDE connection?
February 7, 2006 at 3:40 pm
1. SQL Server 2000
2. 'Cannot locate or connect to SQL Server...'
3. Default instance
4. Local user and domain user are using the same BDE setup. Entered Database name and database server (have created named pipes and tcp/ip aliases in cliconfg and it didn't help, also tried no alias in cliconfg, all of which works as a domain user)
February 7, 2006 at 5:13 pm
ok so to clarify further,
1. From the same server as the failed BDE attempted connections you can connect via ODBC when logged on as either trusted or domain login?
2. Can you connect via ODBC as sql auth login? Have you tried sql auth connection via BDE?
Try setting audit option via EM in sql server properties, security, audit all. Then check in SQL log if your attempts at connecting via BDE generates any failed login attempt messages. This may help in determining if you are even knocking at SQL servers door or in fact failing to find the server at all. The error seems to imply that you are not locating the default instance but this may be an erroneous error message.
I have never used BDE to connect but what about supplying the SQL port to the DBE connection in case it requires it to be specifically supplied.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply