Connect from WIN2000 TO WINNT/SQL2000 using WIndows authentication

Hello,

we develop on Powerbuilder 7.03. We want to use WIndows authentication to connect to a SQL server 2000 with WIN NT 4.0. as OS.
When I want to connect from my PC WIN2000 to SQL2000 with WINNT operating system, I can't ( login failed ).
but when I connect to my PC win2000 to a sql server 2000 with WIN 2000 OS, the connection goes well. ??
Someone encountered the same problem ?? and found a solution ??

Any help will be appreciate.
Thanks in advance.Try this - talks about Windows NT and SQL Server Security

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/modadmin/html/deconwindowsntsqlserverlogins.asp|||Originally posted by ascollins
Try this - talks about Windows NT and SQL Server Security

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/modadmin/html/deconwindowsntsqlserverlogins.asp

Thanks for your reply.
My connection from NT to WIN2000/SQL SRV2000 is OK. my problem is I can't connect from WIN2000 to WIN2000/SQL SRV2000 using windows authentication with PowerBuilder 7.03.

connect error with Windows Security

My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain.
My Win2000 client logs in to AD, not the NT4 domain. I am getting sql conne
ct errors 123 and 53 when I try to create a DSN and add my NT4 domain creden
tials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win
2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 a
nd 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know
ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.|||I am trying to create a user DSN and specify server name on the first screen
. On the security screen, it defaults to my AD login credentials, so I click
sql security, enter my NT4 domain credentials, then click Windows security.
The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated w
ith a trusted SQL Server connection"|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>I am trying to create a user DSN and specify server name on the first screen. On th
e security screen, it defaults to my AD login credentials, so I click sql security,
enter my NT4 domain credentials, then click Windows security. The error I get is " S
QLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted S
QL Server connection"
>
>

connect error with Windows Security

My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 and 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.
Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 and 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.
|||I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
>
>

Configure SQL server client

Hi,
I have installed MS SQL Server on a win XP and a MS SQL Server client on a win2000. I dont know how to configure this client to access the server remotely.
Any pointer?
Thanks.
I am very new to SQL Server.That's kind of a backward installation isn't it??

On the client, you need to go open Enterprise Manager.
Expand the Microsoft SQL Servers.
Right-click on SQL Server Group and click New SQL Server Registration.
When you get to the area that says "Available Servers", type in the name of the machine with the SQL Server.

You should then be able to access it.|||Thanks.

I tried and I always get:

Login failed for null. Reason: not associated with a trusted SQL server connection.

If I provide a user it would say: Login failed for xxx.|||Are you on a domain? If not, go to the sql server and set up a SQL Server username and password, giving it the access you want or grant MACHINENAME/username access to the SQL Server.

If I provide a user it would say: Login failed for xxx.

Was this a SQLServer username and password, or an NT username?|||Make sure you have the following Security Settings on your server.

Note: Here, the Windows User is the local user account that is used to connect to your instance of SQL Server.

1. Click "Start", point to "Settings",and then click "Control Panel".
2. In "Control Panel", double-click "Administrative Tools".
3. In "Administrative Tools", double-click "Local Security Policy".
4. In the "Local Security Settings" window, in the left pane, expand
"Local Policies", and then click "User Rights Assignments".

Also you can use sql standard user to connect to the database. In this case make sure that your sql server authentication is set to mixed.|||>> In this case make sure that your sql server authentication is set to mixed

How to do this?
I am using SQL Server 2000 developer edition.
Thanks.|||Its part of the set up procedure for SQL Server. You change in Enterprise Manager. Open EM on the box the server is on. It should already be configured/registered to access the server. Right click on server name and go to properties. Click on the Security tab. Under Authenication, select SQL Server and Windows. That's Mixed Mode, meaning it will allow Windows Authenication mode (obviously) as well as logins defined in the database.

To define your own login to the DB, go to security in the expanding tree. Then click on Logins. Right click on the blank space in the right pane and select new Login. Type a name, and select SQL Server Authenication, then type a password. On the next tab (Server Roles), check the System Administrators box. Now click OK.

Go back to your dev box. Open EM and do the registration process for the server using the username and password you just created.

Let me know if any of this isn't clear. Its late on a Thursday, so its about time that stuff makes sense in my head, but when it makes it out, I end up confusing others to no end.

Thanks,
Tim C|||Thank you all!
I got my client to talk to server following your instructions.
Thanks Tim!