Re: SQL Server 2005 Login Problem

What's the error message do you get exactly? Do you see any tracks in Event Logs or better SQL Error Log regarding this issue? SQL Error Log will give you an inside track.

Tell me if your SQL Server is a Named Instance or Default Instance? Show me your Connection String that you use to connect to your SQL Server instance.

--
Ekrem Önsoy



"Absolutely" <abs@xxxxxxxxxx> wrote in message news:O28NkQPTIHA.3516@xxxxxxxxxxxxxxxxxxxxxxx
Not a firewall issue. Windows firewall is not active on the SQL server.


"Absolutely" <nospam@xxxxxxxxxxx> wrote in message news:ukPtcS8RIHA.5264@xxxxxxxxxxxxxxxxxxxxxxx
Sorry for the random thoughts... the SQL 2005 is a default instance.


"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:%23ukEHkLRIHA.4152@xxxxxxxxxxxxxxxxxxxxxxx
Then a possible firewall could be blocking your connection.

If your SQL Server is a default instance then it must be using port 1433.

If it's not a default instance, then it's going to be using dynamic ports (unless you specify a static port for it). And clients learn about this dynamic port using 1434. So ensure that your 1433 and 1434 ports are not being blocked by a firewall (probably Windows Firewall).

--
Ekrem Önsoy


"Absolutely" <abs@xxxxxxxxxx> wrote in message news:u01114JRIHA.3388@xxxxxxxxxxxxxxxxxxxxxxx
The clients can ping the SQL server. To take DNS out of the picture I tried to connect using the IP of the SQL server. No go.



"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:A7C29321-42E3-4B88-91F8-3373DED350EE@xxxxxxxxxxxxxxxx
You said you are using "sa" Login to login to your SQL Server. So, a non-domain member client may connect to your SQL Server using the "sa" Login (of course if the network settings let them communicate).

It seems that your clients may not even communicated with your SQL Server server? Are you sure your clients can ping your SQL Server server? Or did you try to reach to your SQL Server server from a client of yours? First, ensure your clients can communicate with your SQL Server server itself and then we will be narrowed the scope of the connection problem.

--
Ekrem Önsoy



"Absolutely" <nospam@xxxxxxxxxxx> wrote in message news:uhOcvP$QIHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
This is workgroup SQL 2005. Here's the odd part of this... a machine that IS NOT a domain member can connect without issue. Domain machines cannot. I've defined the users that cannot connect in SQL and given them rights to the database, but no go. Can't connect using sa account either. Also cannot setup an ODBC connection.

A little background on this...

Customer had an existing 2000 domain. SQL 2005 was setup on a new server that they installed 2003 SBS on. Obviously this is a different domain and a trust cannot be established with the old domain. We joined one of the problem machines to the new domain to alleviate any issue with the trust aspect, but this didn't help.



"Ekrem Önsoy" <ekrem@xxxxxxxxxxxx> wrote in message news:2762B0B7-21E0-425C-ADEC-2BEA0D4A2707@xxxxxxxxxxxxxxxx
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: 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: login 101..
    ... On Windows 2003, SQL Server 2005 can enforce the Windows password complexity ... Windows authentication - SQL Server uses a special protocol to ask ... user is in the list of allowed logins, ...
    (microsoft.public.sqlserver.security)
  • RE: How to create a trusted connection
    ... You need to grant access for the Windows login by referring to the books ... is set to use Windows authentication to be able to do trusted connection. ... There are two modes of authentication in SQL Server: ...
    (microsoft.public.sqlserver.security)
  • Re: Windows NT user or group not found.
    ... out what SQL Server thinks the login name is vs. what Windows thinks the ... When the SQL Server collation and the Windows collation are different, ... The following example uses the Param2 parameter to get the SID from Windows ...
    (microsoft.public.sqlserver.connect)
  • RE: How to create a trusted connection
    ... What do you mean by "creating a Windows login"? ... To login SQL Server 2000 using trusted connection, grant the Windows ... Group" in SQL Server Books Online to get the concept, ...
    (microsoft.public.sqlserver.security)
Loading