I have figured out how to use MS SQL Server Management Studio for SQL
Server 2005, including how to create users.
At my client's offices, on my own LAN (a one man office with two
computers in a peer to peer LAN - machines running the professional
edition of WXP), and on my colleagues computers (stand alone
notebooks), SQL Server was installed allowing both local and remote
connections, and support for both Windows and SQL Server
authentication.
At my client's offices, both local and remote connections work. On our
respective notebook computer/workstations only local connections work,
unless we're connecting to our client's network, in which case remote
connections work.
So far, it would seem all is well. However, there are two issues.
1) With regard to local connections on our notebooks, I can connect to
the default server using SQLCMD without specifying any command line
arguments, while my colleages have to specify at least the machine and
server name. I don't understand why.
2) On my peer to peer LAN, MS SQL Server Management Studio can not find
the other machine that is running SQL Server, and using SQLCMD, I can't
connect to the other server when I provide the proper credentials for a
user I set up on it to use SQL Server authentication. What should I
look at in order to find out why this is and how to fix it?
We are looking at developing an SQL Server 2005 Database and I would like to use Windows Authentication rather than SQL Server Authentication to connect our client app.
In our development environment, we have two Servers, one being used as a file server and the other as an SQL Server. We have now set up a domain using the file server as the domain controller. (We had previously been set up to use a workgroup).
I have set up an active directory group called SqlDevelopers and added an active directory user called Jonathan to it.
On the SQL Sever, in management studio, I have set up a new server login which uses windows authentication called DomainSqlDevelopers. I used the GUI to verify I could see the domain and the group.
The default database is set to a test database on the server. A user in the test database is mapped to the DomainSqlDevelopers and given the Roles dbo, db_datareader, db_datawriter.
To test the log in, on the server, I logged out as administrator and in as Jonathan. I could successfully access the server through management studio using windows authentication.
However, if I log in as Jonathan on my client PC and try to access the SQL Server using management studio and windows authentication, I have problems.
The first time I try I will get a timeout error. If I try again will get either:
Login failed for user ''. The user is not associated with a trusted SQL Server connection
Or
Cannot generate SSPI context
I can€™t determine any pattern to which of the above errors I get.
However, if I log in as administrator on my client PC, I can connect to the server using management studio and windows authentication.
Sounds like Active Directory/Domain or other Network issue (Not really my area). I would be grateful for any help.
Hi, hope someone can help I've been setting up reportig services and now i want to set permissions on the /reports site so i created a domain group called reporting added my users and then added this group to site wide security as user, but it doesnt appear to work, the only way i can get logged on is if i user a local user for my server that is added to Builtinadministrators, what am i doing wrong? why cant my domain users access the site?
I have created a website using Visual Studio 2005 that runs in ASP.NET v2.0. In the debugging mode of VS2005 the site works just great and I use the ASPNETDB.MDF database to hold all of my user authentication data. Since I have deployed the website over to a remote server the authentication no longer works. I can access the first page of my website that is a login page but as soon as I attempt to log in with a valid user I receive an error message as below:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I copied all of my files in the website folder over to the corresponding folder on the remote server. I then installed MS SQLServer Express on the remote server. I'm suspect the problem is something to do with that ASPNETDB.MDF file. Please can somebody help? Is there anything else I need to do for the website to work as it did on my local machine? I have given the NETWORK SERVICES user full access on the website folder.
I'm almost sure that it's not possible, but I wanted to ask in case that I'm missing something.Is it possible to get the Windows user when someone logins using SQL Server Authentication? I know how to get the hostname, but I can't find how to make the next step.By the way, do sleeping connections affect performance? Would they consume resources such as RAM or network?
Hey Gang, I get a error message "Authentication Failed for SQL Serverinstance: local with friendly name local SQL Server does not exist oraccess denied". I have a Just loaded SQL Server on my virtual box and loadedMicrosofts bpa and microsoft security anlyzer. The security scan work but thebpa scan doesnot. I also look at the database,I can get access to and notice a newdatabase schema(sqlbpa). Any help would be appreciated.ThanksGarry D
User1 : have sql rights on database but dont have rights to login into windows User2 ; have rights to login into system but dont have access rights to database
Now I have windows application and i have logged into system with User2 and want to run windows application with the rights of User1. How can i achieve this.
I have built a site that uses form-based authentication. Am I correct in assuming that the users and passwords will be stored in the SQLServer database in the aspnetdb.mdf file? The website works great and the authentication works how I want it to. However, I've tried to copy over the file onto a remote machine. The first page is a login screen and this is displayed without any problems but as soon as I attempt to log in I get an error message of:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)I'm wondering if this is something to do with the fact I installed SQLServer Express edition on the remote machine. The website works no problem on the local machine in debug mode of Visual Studio 2005 (Professional Edition). I followed instructions to enable remote connections on SQLServer Express from a Microsoft support doc. If anybody can point me in the right direction I'll be very grateful as I've hit a wall here.
I have a website written in asp.net and the current DATABASE logins do not use windows authenticaton. They are for online use only with a username and password. I'm trying to run my program locally on my machine and access the database locally. This is very frustrating. I'm able to connect to my database, but I can't login to it. Here's my connection string from ym webconfig file: <add name="sqlConnectionString" providerName="System.Data.SqlClient" connectionString="Connect Timeout=8; Initial Catalog=linkexchanger; Data Source=SCOTSQLEXPRESS; "/> I have the MSSQL engine running and I have connected with the SERVER. My database is in my directory tree of Microsoft SQL Management Studio Express. The server is SCOTSQLEXPRESSI have attempted to add a login to my sql database by right clicking on the security folder to create a new login. My understanding is that under windows, I don't need a uid and pwd in my connection string . Thus I tried removing all of this just as you see above, and I get an error message every single time I try to create a login with windows authentication. Can someone please explain how I make this work? Thank you. Scot
Can someone please help me with troubleshooting my SQL Server authenticated user. One of the users that I created has a login name of <None>. I am unable to delete this user and recreate his login nor plug in a login name. I believe that there is a script to correct this problem but I am having trouble researching it. I am working under the gun to resolve this issue so anyones help with the issue is much appreciated.
Is there a way to connect to database using Windows authentication as a different user than what you've logged in with to your desktop?
For example:
I log on to my desktop as mydomainme. I'm developing queries using Management Studio against a database (on another server) where mydomainme doesn't have access, but the admins have granted access to mydomainJobs1. I have the password for mydomainJobs1, and I'm hoping I can connect to the database using that account without having to log-off my local desktop as mydomainme and then re-login using mydomainJobs1.
The analogy in the file/share-permissions world would be using "net use" from a command prompt:
net use \SomeServer /User:mydomainJobs1 jobs1password
I have created a database now I am setting login details for that user. I am using slq server authentication and entering a password of recommended length.
I enter my details in my webconfig file and I get -couldnot connect to database specified in connection string for sql data provider.
when I check the login properties the password has changed it appears to be the password for NT Authoritysystem, ie same length, what it is Idont know.
I'm working on an ASP.NET project, and we're attempting to switch from SQL Server authentication to Windows authentication to connect to the database. It works fine locally when I debug in Visual Studio, but when it hits the web server, I get the error: "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." IIS has anonymous access disabled, and Integrated Windows Authentication is checked. The web.config file has: <authentication mode="Windows"/><identity impersonate="true"/> The database I'm attempting to access is on a different machine than IIS, and the connection string doesn't contain a username or password, and has "Trusted_Connection=Yes", and "Integrated Security=SSPI". From what I've been able to find online, I'm guessing the problem is due to IIS and SQL Server residing on different machines, but I'm not sure how to fix it. Any ideas?
I'm trying to connect to a SQL Server 2005 database engine on a local network server. When I am presented with the Connect to Server dialog box, if I select Windows Authentication from the Authentication drop-down, the User name & Password area is grayed out and unusable. The domain user account I'm authenticated with is visible, but grayed out, and the password field is blank and unusable. I'd like to be able to connect as described in help:
User name
Enter the user name to connect with. This option is only available if you have selected to connect using Windows Authentication.
I can connect with either SQL Server or Windows authentication... but with Windows Authentication I'd love to be able to type a specific user name to select with :-)
Hi-- I am building an intRAnet website using windows authentication for website access and SQL Server access ( Trusted_Connection = true ). In IIS I have these settings:
Allow Anonymous = unchecked (false) Windows Authentication = Checked (true) Digest windows = checked (true) In my Web.Config file:
authentication="windows" impersonate="true" allowusers="*" When I pull up the page these are my credentials: Security.Principal.Windows: mydomainmyuserid (this is correct what it shows on my page) Me.User.Identity: mydomainmyuserid (this is correct what it shows on my page) Threading.currentThread.currentUser mydomainmyuserid (this is correct what it shows on my page)
So the ASP.NET page recognizes it is me and my domain. However, when i click a button to pull some data from a database I get the error message: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. My data access on SQL Server works fine. The weird thing is when I debug on my machine it pulls data fine. but when I copy the files to the windows 2003 server it doesn't work. Do i have to do something with delegation?
Would be interested in any advice or comment on the issue we are experiencing with SQL 2005.
In order to test some DTS package migrations, we simply created a DTS package on SQL 2000 (using Export) to copy all database objects from one database to another.
Then we restored the source database on SQL 2005 server, migrated the DTS package, and tried to execute it.
The package migrated 'fine', ran part way, and then failed. Since then we have been unable to connect to the server (Database Engine, or Integration Services) using Windows Authentication. (Error 18456, Sev 16, State 11).
We can connect to the Database Engine using SQL Authentication (but not to Integration Services which only allows Windows Authentication).
We have been able to replicate this consistently - every annoying time we've tried it!
(Reinstalling SQL Server does 'fix' the issue ... until you try a similar package again).
We need to use SQL Server Authentication for some reason and would like to enforce Password Policy with 90-day expiration period. I found "Change password" dialogue appears when I first logged in with the new user, but don't know
(1)what happens when the user failed to change the password before it's expired or (2)how a user can change his password in advance of the expiration date with no particular server-level permission.
I folks.I Have installed sql server 2005 express and choosed windowsauthentication on instalation, but i make a mistake and now i needmixed authentication, how can i modify this whithout uninstall andinstall again the application?thanks for the help.
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.
Hi,I'm using SQL Server 2005. My Connection String looks like that at the moment: <add name="LocalSqlServer" connectionString="Data Source=xx;Initial Catalog=xx;Persist Security Info=True;User ID=xx;Password=xx" providerName="System.Data.SqlClient"/> Now I'd like to change this kind of authentication to Integrated Windows AuthenticationI added the WorkerProcess IIS_WPG to the permitted Users but it didn't help.Changed the Connection String to this:connectionString="Server=xx;Database=xx;Trusted_Connection=True;"All I'm getting is that my NetworkService is not permitted to access DB when I try to connect to the DB in ASP.NET.How can I properly configure that? Thanks!
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?
Oracle and Teradata are able to capture the windows/client login that connects to their database with a functionnal ID.I've searched around and I don't think MS SQL can do this...I administer SQL 2014 server and also SAS Enterprise guide product. I've created sql server logins for several teams so everyone shares the same sql server login which is used to bind the SAS library to my SQL server database.
However, when looking at activity monitor, I can't drill down to which user is executing a particular query. I only see the SQL login which is share amongs 200 other folks.On the other hand, when they connect from SAS to Oracle or Teradata, I can see the shared login + additionally their windows NT login used to connect to SAS which is awesome....they can't fool me by using a shared/funcionnal ID....i still see who's using that ID...
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?
This is my first time to deploy an asp.net2 web site. Everything is working fine on my local computer but when i published the web site on a remote computer i get the error "Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed" (only in pages that try to access the database) Help pleaseee
