Re: SQL Server 2005 Login Problem

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: Connectivity to SQL Server from Existing COBOL Apps
    ... For access to MS SQL Server, have a look at sourceforge ODBTP. ... migration project, I'm just exploring options, one of which is database ... move a VMS application to Windows so just keep pushing it up that hill. ... equivalent SQL Server database running on Windows. ...
    (comp.os.vms)
  • Re: SQL Server 2005 Login Problem
    ... There are two authentication method in SQL Server. ... 1- Windows Authentication ... 2- Mixed Authentication (through SQL Server logins and Windows accounts) ...
    (microsoft.public.sqlserver.clients)
  • Re: Problem with SQL Server 2005 Express Edition
    ... Since you are specifying the user name and password in the connection string I assume you are using SQL Server authentication for your logins rather than Windows authentication. ... One cause for that error is trying to use a SQL Server login on a database server that is configured to only accept Windows logins. ...
    (microsoft.public.sqlserver.security)
  • Re: System Administrator Implied Permissions
    ... >> Hi Dan, ... >> Now, given this, why does SQL Server ... However, these logins were not ... Other sysadmin role members have the ...
    (microsoft.public.sqlserver.security)
  • Logins & Permissions
    ... I am using SQL Server 2005 on a Windows NT Network ... but I am trying to get some understanding of logins and permissions, ... white papers or web sites that explain the basics of SQL Logins and ...
    (microsoft.public.sqlserver.security)
Loading