Re: SQL Server 2005 Login Problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Is that SQL Server 2005' s Workgroup Edition? As I don't have Workgroup Edition on my test environment I don't know its default values.

However there are something must be turned on before a remote connection to SQL Server. For example in Express and Developer Editions of SQL Server, Remote Connections are disabled by default. You can enable this option using SQL Server Surface Area Configuration tool.

And then configure your TCP protocol from the SQL Server Configuration Manager.

--
Ekrem Önsoy



"Absolutely" <nospam@xxxxxxxxxxx> wrote in message news:uPQO4oyQIHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
I'm getting a similar issue. SBS with SQL 2005. XP Pro SP2 machines just won't connect to it. SQL server is in mixed mode. We're using the sa login at the workstations and it still won't connect.





"Andy Baker" <abaker@xxxxxxxxxxxxxxxxxx> wrote in message news:13j8hg7l3m460d5@xxxxxxxxxxxxxxxxxxxxx
Hello Ekrem

Thanks very much for the advice, I have got it working now. It is only a simple 3 station network and all users only require access to a single SQL server database, so I created a login for the users group and only allowed access to the one database. I think it is OK - I can get a connection now! Thanks again.

Andy Baker

"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:93A243FE-4994-4224-9A7F-210D2C1616DA@xxxxxxxxxxxxxxxx
Hello Andy,

There are two authentication method in SQL Server.
1- Windows Authentication
2- Mixed Authentication (through SQL Server logins and Windows accounts)

When you use Windows Authentication, yes, as you mentioned you do not need usernames and passwords. Instead, you need an authenticated Windows account. However, you have to create Login objects for those Windows accounts. Otherwise, all Windows users would be able to reach any content in databases right? Only creating Logins is not the complete solution of course, then you'll need to map those users to the appropriate databases and assign them roles and grant them permissons. So, you'll ensure that every user has access to databases that you want them to have.

In terms of managebility, it's better to create Windows Security Groups and create logins for these groups when you use Windows authentication. For example, you'd create a Windows group in your domain called Accountants and add all users of accountance department to this group and create a login in SQL Server for this group and grant to this group the appropriate permissions. So, you'll accomplish your task in shorter time. When you'd need to modify accounants' permissions, you'd perform this only for Accountants Login (which is a Windows Security Group, remember?) One stone, two birds, maybe more =)

When you use Mixed Authentication, you can use Windows accounts and SQL Server logins both. However, this is not a recommended method for SQL Server Authentication when possible.

--
Ekrem Önsoy



"Andy Baker" <abaker@xxxxxxxxxxxxxxxxxx> wrote in message news:13j88fgquc8d8b4@xxxxxxxxxxxxxxxxxxxxx
Thanks for getting back to me. I don't really know much about how SQL Server works, so please correct me if I have misunderstood you, but I thought that the idea of Windows Authentication was that you didn't need to use separate usernames / passwords, it worked when you were logged into windows because it was a trusted connection (integrated security =SSPI. My SQL Server 2000 installation doesn't have a separate logon for each user - is 2005 different?. Do I have to set up each user as a SQL Server user as well, and do I have to include Userid and Password in the connection string? It is a default installation.

Andy Baker

"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:D97FC7FA-9CD8-4C93-829F-29F35B3B9D5F@xxxxxxxxxxxxxxxx
Ensure you have approprate logins for those users who can't connect in your SQL Server Logins, if not, create logins for those users.

Also, it's a default instance I believe, because you use only server name in Data Source?

--
Ekrem Önsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCDBA, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT



"Andy Baker" <abaker@xxxxxxxxxxxxxxxxxx> wrote in message news:13j6eo61mk6he1e@xxxxxxxxxxxxxxxxxxxxx
We have recently purchased Small Business Server Premium, with SQL Server 2005 workgroup edition included. I has 3 XP PCs that I want to access the SQL Server database, and have set it up with windows integrated security. When I try to connect (from a VB.NET application) I am getting an error 'Login failed for User' followed by the domain name and user name. The connection string that I am using is 'Data Source=MAIN; Database=Vanputer; integrated security=SSPI; persist security info=False;" (where MAIN is the server name and Vanputer is the database name) The application connects fine to a server running SBS 2000 and SQL Server 2000, but 2005 is rejecting the login. What am I doing wrong. Thanks in advance for any suggestions.

Andy Baker











.

Relevant Pages

  • Re: SQL Server Authentication, NOT Windows NT
    ... Windows wizard for creating ODBC link on user pc. ... The problem is that even though I set up the ODBC links to use SQL Server ... Authentication because SQL Server won't accept our Windows logins (reads them ... SQL Server Login window opens, unclick Trusted Connection, input SQL ...
    (microsoft.public.sqlserver.security)
  • Re: Windows Authentication in asp.net 2005 to SQL Server?
    ... If the domains do not trust each other, Windows authentication is not going ... Basic authentication sometimes makes the need for Kerberos delegation go ... generic account to do the backend data stuff on our SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Kerberos / Authentication to SQL2K
    ... use Windows integrated security for database access. ... That SQL Server be running on the same computer as IIS. ... > authentication until I switched on impersonation either. ... > When set up on my web server however, I get the "Login failed for user ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Slow booting xp home.
    ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Changing passwords / Blocking SA login attempts
    ... I went into the Server Config properties and changed to Windows ... My login for Start and Run SQL server was in this format. ... I am supposing this was an SQL authentication, ...
    (microsoft.public.sqlserver.security)