I face the following isuse on a Microsoft SQL Server 2008 R2 (SP2):
Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only.
My SQL server has mixed mode enabled (i verified and switch it on and off several times)
I am able to loging from a peer server which is a replica with the same windows accounts
I am unable to loging from a Windows workstation
The DSN configuration in Windows is succesful though
If mixed mode is enabled why would the server tell me it is not?
What could cause the server to believe it is Win authentication only although the setup is mixed mode?
Wireshark did not help.
I traced back the changes on the server it appears that the main administrator user was renamed. A new sys admin user was created and I had to add this user in both Windows SQL Security groups.
Related
I've been using SQL Server Express with Windows authentication for many years with no problems. However, for a different application I need to use server authentication. I'm running SQL Server 2008 R2 Express.
Here is what I've done so far in SSMS:
Enabled "SQL Server and Windows authentication mode" in the "Security" section of Server Properties
Created a new server Login with 'public' and 'sysadmin' server roles
Created a new database user with the above login and assigned it db_accessadmin, db_datareader and db_datawriter.
When I try to connect to the server using SSMS and SQL Server authentication I get the "Login failed..." with 18456 error.
I'm definitely providing a correct password.
Is there anything else that needs to be done for the server authentication to work?
Thanks.
It is required to restart SQL Server after enabling the SQL Server authentication mode.
I have installed SQL Server 2012 Express edition on a pc which is on a workgroup running Windows 10. I have also created an user for access to the database through the VS2013 application.
When trying to connect to the server from the client machine, I am getting a message saying login failed and it is from an untrusted domain. The client is also on the same workgroup. However, after the SQL Express was installed on the "server" machine, the name of that pc was changed. I can connect to the database from the server using SSMS using the new computer name (in the instance). I have set remote connection parameters and also configured firewall rules. Yet I am unable to access the server from the client machine.
I also want to ensure that the database is totally secured against access or intrusion. Anyone having access to the server machine can view/edit the database using Windows Authentication. How best to safeguard against it?
Any tips would be appreciated.
CL
try to make a new user in server machin using SSMS and be sure that you are adding the new user to the Login Part of Security in SSMS . For this you need to Login to SSMS as administrator ...
I have installed SQL Server 2005, the SQL Server instance name is SOSO, the machine name is HERO, I tried to connect from another computer using SQL Server Management Studio:
Server name: HERO\SOSO
Authentication: Windows Authentication
But I didn't succeed.
SQL Server is enabled to be connected remotely.
So what is the problem?
Windows Authentication uses the Active directory user from the connecting machine to authenticate with the database. Does it have the right permissions to access the database? Maybe try authenticating with a SQL Server database user first. Maybe you've created a SA user on installation, try connecting with that.
But as the other replies also tell, first check network / firewall connection and please provide us with the error message.
I have some database problems.
I have SQL Server Developer installed on my local machine. When I open SQL Server Management Studio and log in with windows authentication there is no problem. I have created a new database there and added a new user. The new user is owner of the database.
When I disconnect from my windows session and try to log in with the newly created user in SQL Server authentication mode I get the 'cannot connect to (local)'
Please help!
Have you enabled SQL Server authentication? (During installation and/or afterwards)
If not, connect using windows authentication, right-click on the server instance, go to properties and change auth mode...
I'm trying to connect to a remote SQL Server Express machine using Windows authentication.
I´m logged on with a user with username Administrator, but when logging in, I get the error message:
Login failed for user guest ...
Why is not using the Administrator account?
Thanks in advance.
For Windows Authentication to work, the target machine has to be on a domain where your Windows credentials will be recognized. If the server is outside of your organization's control, it will not recognize your credentials and you will have to use a Sql Server user ID and password to log in.
SQL Server Express by default only allows local connections - you can enable it, but you have to explicitly do so.
See these:
SQL Server Express team blog: how to enable Express to accept remote connections.
How to enable Remote Connection on SQL Server 2008 Express