Re: Help: Login failed for User ???

Hi Jim,
Thanks again for the reply.

"Jim Hughes" wrote:

The users desktop permssions are not relevant to their ability to access the
SQL Server. They will not need to be admins on their desktop or the server.

I was sure that the case, but wanted to make sure there was not some wierd
setting that would make a difference.

UserID and Passwd are not used in the connection string when
trusted/integrated security is used and should not be present.

Understood. Have removed all that.

You can test database access by creating an empty file with as UDL extension
and then opening it and setting the parameters and using the Test Connection
button.

The SQL Server will need to be a member server of the domain as will the
users workstations.

Internal DNS will need to be properly configured with appropriate records to
access the domain controllers.

Firewall settings on the SQL Server will need to be set to allow access for
Named Pipes.

The SQL Server Network Configuration network utility will need to be set to
allow Network connections via Named Pipes and perhaps TCP/IP.

On my development machine (logged in as myself) I can use the application
without any login errors, but as soon as I Login into windows(again on my dev
machine) using the clients(employees here) userid and password, my app will
not work and gives the lonin error as noted before.

I have a question about something I read in the online help.
<Quote
When a network user tries to connect, SQL Server uses Windows-based
facilities to determine the validated network user name. SQL Server then
verifies that the person is who they say they are, and then permits or denies
login access based on that network user name alone, without requiring a
separate login name and password.
/>
Does this mean that the password needs to be set in SQL Server. I ask,
because, since I have Windows Auth set for the database, I can't change any
of the users passwords. If I have to include the passwords for the users,
how do I do this in Windows Auth mode?
I was trying to do a test and just setup the db so that it uses only SQL
Auth, but when I try to change it to SQL Auth in the Edit database
registration, I get an error:
SQL Server registration failed because of the connection failure.
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.

I was thinking of changing over to SQL Auth to make it easier (If I've got
to go through this each time I add a new user). What do you all think? I've
heard that Windows Auth is better than plain SQL Auth. Why? How about
creating a single userid and password on the server and user that combo in
the connect string to connect to the db. I hope I can get Windows Auth to
work, so I won't have to go in this direction.
Thanks for hanging in there.
Michael

.