My boss is concern that when using Windows authentication, a user can access any database that they have the rights too, using any SQL tool, and make unauthorised changes. He thinks that using SQL authentication is better because the username/password can be hidden from the user. (Access to the database is controlled by our applicatoin.)
Could someone knowledgeable in this are please comment.
hello ,I have a problem with connecting to SQL Server by Windows Authentication.It's the error:"Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. "and this is a source code :"SqlConnection cn = new SqlConnection ("Data Source=PLGRZFLS0001;Initial Catalog=Magazyn;Integrated Security=SSPI;Trusted_Connection=Yes");cn.Open();SqlCommand cmd = new SqlCommand("exec proc_permission",cn); SqlDataReader dr= cmd.ExecuteReader() ;dr.Read(); "in my web.config :<authentication mode="Windows" /> <identity impersonate="true"/>i have no idea what is wrong :(:( bye,sorry for my english
Brief Description: I would like to use C# to write a program to access a SQL Server instance which is at another PC and using Windows Authentication. (I know how to use SQL Server Authentication, but I need to use Windows Authentication only.)
Detailed Description: 1. I have two PCs, and I would like to write a C# program in PC1. to access SQL Server at PC2 with Windows Authentication only.
2. I installed Microsoft Dynamics POS system. I install the POS Database with Windows Authentication only at PC2, but then I can install POS at my PC1, and when I set up the connection to the SQL Server, POS will pop up a dialog to ask me the username and password. I can just use the PC2's windows user account to login. Then POS can work fine. I would like to do the same just like what they did.
3. I tried the following code at the PC2 (the same PC as the SQL Server running), and it is running fine. But if I copy the same program and run it at another PC, then it will pop up a "Logon failuer: unknown user name or bad password.".
After 2 days of reading everything on the net about setting up Remote Access of my SQL 2012 Express using Windows Authentication I'm still not able to connect from a remote client onto my SQL Server Database Engine. I can get connected if using SQL Server Authentication. I have set all the parameters to allow access (read and tried everything from this site: URL.... but when I try using SSMS from the remote client to login I get Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452).I've disable the firewall (Even though I have put in rules to allow port 1433 and UDP port 1434). Nothing is allowing me to connect. I've have tried every solution listed and got nowhere. My network is very simple with only three computers connected via a Linksys router (Two running Windows 7 the test client is running Windows 8.1). I can shared files and folders between all. Each computer only has one user defined (default admin user).
I need to make this work as I have to document it for other end users who will be using an application I created that requires an SQL Database and it needs to be accessible by other users on their network.
I have a linked server defined on a SQL Server 2005 SP2 standard edition server using the IBMDASQL OLEDB driver. The linked server has been defined and working for months when used from a SQL Server authenticated session. I started converting our developers to Windows Authentication and access to the linked server is denied when used from a Windows Authenticated session. Here are the error messages:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "IBMDASQL" for linked server "DB2ARUBA" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "IBMDASQL" for linked server "DB2ARUBA".
The linked server security is defined to login to the IBM iSeries using a fixed user and password regardless of the login using the linked server.
In order to analyze the problem, I created one sysadmin SQL Server authenticated login and one sysadmin Windows Authenticated login. The Windows Authenticated login refers to a domain login having administrator priviledges on the local SQL Server box.
So, when I connect to SQL Server using the SQL Authenticated login, a query against the linked server works. When I connect to SQL Server using the Windows Authenticated login, the exact same query against the linked server fails with the messages above.
SQL Database in my application with windows authentication rejects accessing after deploying and remote access 1- My web applications databese access is windows authentication 2- In developing area there is no problem for accessing database 3- After deploying to another server there is problem accessing database: Cannot open user default database. Login failed.Login failed for user 'BRCK231ASPNET'. How can I solve this problem? Thanks.
Hi there,I have installed MS SQL Server 2005 on my machine with windows authentication. But now I want to switch the authentication mode to SQL Authentication. I am unable to switch, I can’t find the proper way to do so here in 2005.Could any one help me in doing this?Thank you,-Ahsan
(Using win2k, sqlserver2k, framework 1.1) I have an fairly data-heavy application that uses Windows authentication (Trusted connection/aspnet account) to connect to Sql Server. The site uses IIS basic authentication.
On the dev server everything works fine but when I move to the live server things get strange and it starts to crawl along. (Pages load OK but then it just crawls as it loads the datagrids etc. Sometimes it brings back incomplete/incorrect data )
BUT When I use Sql Authentication to connect to Sql Server and there is no problem at all!
Ok, there is something obviously wrong with the live server (which is identical setup to dev)but I dont know where to start.
I've got two applications which both have a database on my MS SQL 2000 server. The problem is, one application must use Windows Integrated Authentication (which it is currently using and cannot be changed) whilst the other application which I'm trying to configure must use a SQL password.
Since the server has already been configured to use Windows Integrated Authentication for the existing database and application, how do I configure the other database to use the SQL password?
My work is using a shared application which accesses a MSSQL 2000 database. To access the application, the folder on the Windows 2003 Server is shared and users can access the folder through a shared drive.
For the application to access the database, it uses an ODBC connection to the MSSQL server which originally used the SA password.
We have recently switched to using Windows Integrated Authentication because we believe it offers a higher level of security. However the only way in which we have been able to enable this is to add the windows users to the SQL server.
The problem with this is that the application sets permissions for individual users on what records they can see within the database. We have found that by adding the windows users to the SQL Server, they can bypass the permissions the set by the application by simply using any application that can use an ODBC connection, such as Enterprise Manager, and see all the database.
One way around this would be to set up domains of users with access privileges to the tables which reflect the permissions set by the application, and configuring a view of the data so they may only see the records that they have permissions to. However to do this would require a high administrative cost to ensure that changes made in the application are reflected in the privileges of the SQL server.
Instead, is there a way the SQL server can authenticate that the ODBC connection is coming from the correct application using Windows Integrated Authentication?
This would allow the applcation to determine security, and stop users from connecting to the SQL server using other applications.
Alternatively, can the SQL server, using Windows Integrated Authentication, also ask the application to supply a username and password?
Any help with this matter would be greatly appreciated.
I just upgraded from Windows XP Pro to Windows Vista Bussiness and tried to reinstall SQL Server 2005 Developers Edition. After the installation i downloaded (using microsoft windows update) and installed all the service packs for sql and vista available.
My problem is when i open sql server management studio and try to connect to my default instance using windows authentication and database engine, an 18456 error occurs.
I enabled all the protocols and all the ports I disabled windows firewall and antivirus (eset nod32) I installed all service packs available I have also installed Visual Studio 2005 without installing sqlexpress
But nothing happens!
Please i am very desperate, any information will be gratefully accepted.
This is my installation Information
Code Snippet
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 6.0.6001.18000 (longhorn_rtm.080118-1840) Microsoft MSXML 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.6001.18000 Microsoft .NET Framework 2.0.50727.1434 Operating System 6.0.6001
Say, I have configured my SQL to use Mixed Authentication. Now, I have a applicaiton which uses my SQL Server. The application just creates a database in SQL Server and uses the database to store its information.
This application also has a SYSTEM DSN under ODBC through which it accesses the database. For the application to access this database, should I only use SA (as my SQL instance is configured to use Mixed Authentication) or can I use Windows Authentcation too...
If I should only use SA, do we have a documentation which talks about this.
For using different services of SQL SERVER 2005 which is better... Windows Authentication or SQL Server Authentication? what are the advantages and disadvantages of both?
I wonder if it is possible to set forms authentication for report manager but leave report server "as it is". I need to authenticate users from external LDAP and can't use windows authentication for report manager, but I would also like to leave report server open for anonymous users. In that way authenticated administrators could create reports which anonymous users could read.
I tested the Security Extension Sample and got it working when I rewrote the authentication part with my own LDAP authentication.
If I have understood correctly, the report manager is just application inside report server so is it possible to use forms authentication with one application but still leave the report server with Windows authentication?
I am in the process of rolling out a sql server 2005 enterprise install and had a question regarding authentication. We will be providing sql hosting for a number of groups on our campus, many who are not using our campus-wide active directory, though they all have an AD account.
Windows authentication via the management studio appears to use your AD authentication tokens and will not allow them to enter a username/password combo. Is there any way to configure this?
I would like to use our campus AD for obvious reasons but if there is a requirement for passing tokens this isn't going to work right? It's also going to make database mirroring more of a challenge.
My SQLExpress seems to be set for windows authentication and not sql server authentication ... I am not quite sure why it is set to windows authentication - I installed this with Visual Studio 2005 and it just seemed to be set that way.Am I able to change this - if I choose sql authentication when connecting I get an errorIf someone could answer this point I would be most grateful !!Patrick
In an effort to eliminate the need to code accounts and passwords into the VB Com calling stored procedures, I would like to use Windows Authentication. I have setup the account that the com is running under to have access to the database. How does this change my connection string. Do I just drop the account and password parameters or do I need to let it know somehow that I want to use Windows Authentication?
I'm having problems with windows authentication. I'm new to using using Microsoft SQL Server. I just migrated from powerbuilder 8 to powerbuilder 10. I'm using OLE DB and can't get the windows authentication to work within the application. Can anyone help....
Hi, I am wondering that do we need to create the separate login at SQL SERVER (server) for all the user using the application for the windows authentication?
How do the windows authentication works? I have a apllication and SQL SERVER (SERVER) running on the same machine. Any user from the same domain can access the application. Application is interacting with the DB through Windows Authentication. Now my question is whether do we need to authenticate each user from the domain at the DB level. That is to craete the login id for all the user for windows authentication.
I remove the windows authentication from enterprise manager. and Now i want to re-assign the the windows authentication . so can i do it from query analyzer.
Hi all,You're all stars, really helpful. Maybe one day i can be :)My question is regarding the authentication in Windows SQL Server 2005.We have setup a sa account. We purchase software from a third partythat runs on it. Before their software logs on the sql server as sa,and does its own access control, windows autentication takes over. Itslogs users on correctly i guess, using a more secure link via thedomain. However, I am probably blind, but where can we assign rights toeach domain user? I.e. stop XXY dropping tables, but allow ABC to droptables?I had a brief look through but could not find anything that stood out,in the SQL Manager.ThanksDavidP.S This is SQL Server 2005 Workgroup edition running on a 2003 windowsdomain server. Alongside a SQL 2000 server, which is running fine usingsa accounts.For those in the same timezones as me... have a good evening.
Hi! Happy New Year!I'm having windows authetication connection problem. Although I cansee all the servers by using SQL Server authentication conncection, Ican see only some of the SQL family servers by using windowsauthentication connection. I checked the servers' properties of that Ican and can't see, but couldn't find any difference. Can someone giveme a direction that will enable me to debugg?If the servers are not in the same domain, how can I see them (windowsauthentication) from the same PC (client)?For some SQL server I even can not login via windows authentication atterminal server. Is any specific setup I should do at server?Thanks!Saiyou
Hello,We have a SQL 2000 installation (running on NT4 SP6a) with a databaseaccessed by a client application. Currently the application logs into thedatabase using a the SA account. I'd like to move the client access over toWindow Authentication. Each user has their own NT account. What steps do Ineed to take to achieve this?Any help would be greatly appreciated.James G.
When using Windows Authentication and the Client (xp home edition) has NO PASSWORD and he accesses a server with sqlexpress...does that default him as 'guest'....
What is difference between State 8 Password Mismatch and 9 Invalad password
We have an application that uses SQL Server 2005 (Express) as its database server.
We have SQL server and the application database on our server.
To setup the application we need to point it to our database from the clients and specify authentication as either SQL server or Windows Integrated Authentication. We chose Windows Integrated Authentication. This works fine for an administrator user but for a standard user with non administrator privileges , authentication fails and we cant access the database. The client is running Visa Business with UAC on. If I run the application as adminisrator and enter the administartor username and password then I can connect otherwise it is rejected.
How can I can configure SQL server to allow non administrator users to access it using Windows Integarted Authentication.
I've got an application that's supposed to use a combination of Windows authentication and Custom authorization, here's how.
Only the administrator can add users, venues, and booking types. In addition, only the administrator can reset a booking password on the bookings table and/or form. I (as the current administrator) want to be able to add a user and grant him/her permissions (either as admin or just user).
Admin access: add new users, venues, booking types, and reset booking password which will be used to grant permission to change booking details such as time and date. When the administrator adds a new user, there's an option (a field called admin on the user table) on whether or not to give the user admin rights, if yes the user is added to both the admin role and the user table
'Normal' user access: add and/or change own booking and change other user's return time and date provided a password is correctly provided. Does not even have to know that there's a user, venue, and a booking type table.
I've read about Windows authentication on the MSDN library but I seem to be getting nowhere and just have no clue where to start.
My organization is in transition of converting from SQL Server 2000 to SQL Server 2005. Conversion from Visual C++ 6.0 to Visual C++ 2005 is done. The converted Visual C++ code has OLE DB and has only native code(== no managed code). The OLE DB uses user name and password information to log into SQL Server 2000. Microsoft recommand to use Windows Authentication for security reason. I was informed that Basic Authentication, SQL Server Authentication, or Mixed Authentication allows OLE DB connectivity with user id and password. However, I have tried but have not figured out how to use same OLE DB with user Id and password information to access SQL Server 2005 with Windows Authentication. Is it possible to use Windows Authentication with OLE DB connectivity with user id and password? If so, I would greatly appreciate sharing your findings.
I am new to the whole ASP .NET scene, so my knowledge is very limited, and if I’m not clear enough please let me know. I am reading a book published by APress about ASP .NET with C# and I am at the point where I get to begin working with data (fun!!). The problem is that I’m not able to connect to the SQL Server. I have Server 2003 and SQL Server 2005 running on a separate machine than the computer that I use for development – the server is named THESERVER, the SQL server is named THESQLSERVER, and the computer I use for development is my laptop named MYLAPTOP. So here’s my connection string (I put this in my web.config XML file):<add name="Pubs" connectionString="DataSource=THESERVERTHESQLSERVER; Initial Catalog=pubs;Integrated Securit=SSPI"/> Now here’s what my book reads: For Windows authentication to work, the currently logged-on Windows user must have the required authorization to access the SQL database. This is all it says about Windows authentication because the book assumes that I am running MS SQL Express off localhost. Questions: Does the book mean that I will have to add a user to my server for my laptop? If so, how do I log into this user using the connection string?What does it mean by “the current logged-on Windows user”? Is that referring to the user on my laptop, or a user on the server? I’ve been reading around trying to find more information on exactly how Windows authentication works, but I keep coming up dry. I know that much of this is probably trivial to a lot of you, which is why I am asking because it isn’t to me. Well, thanks in advance for any help that you can provide me.
