Re: SQL Server registration failed because of the connection failure displayed below

From: Peter Afonin (pafo@specialtypulltabs.com)
Date: 07/25/02 

From: "Peter Afonin" <pafo@specialtypulltabs.com>
Date: Thu, 25 Jul 2002 08:30:16 -0700

Thank you, Linda.

Let me explain in details what I'm doing now.

With the current settings everything works great. These settings are:

1. Under Properties - Security tab:

Authentication: SQL Server and Windows

Start and run SQL Server in the following account: System Account

(before it was set to SPECIALTY\pafo, and it also worked fine)

2. Under "Edit Server Registration properties":

Connection: Use Windows authentication

The error occurs when I change it to "Use SQL Server authentication" and put
"sa" or any other account. When I click "OK", I get this:

"SQL Server registration failed because of the connection failure displayed
below. Do you wish to Modify anyway?
Login failed for user 'sa'"

In my home computer that is not a member of a domain I didn't have any
problems changing authentication. I don't know though whether this has
anything to do with the domain.

Thank you,

Peter Afonin

"linda deng[MS]" <lideng@online.microsoft.com> wrote in message
news:3l7MDZ5MCHA.1380@cpmsftngxa07...
> Hi Peter,
>
> Since you have configured the authentication mode as 'SQL Server and
> Windows' authentication in the security tab, you should also set it in the
> 'Edit SQL Server registration Properties' window. Once you have chosen the
> 'Use SQL Server authentication' option, the 'Login Name' and 'password'
> will be enabled. You should specify the account and password there, which
> is the standard account of the SQL Server like 'sa' and others created as
> 'SQL Server Authentication' in the Enterprise Manager (EM). They are
> different from the Windows account, for example, 'SPECIALTY\pafo' and
> 'Administrator'. You can try to add a new login by expanding
> security\logins in EM.
>
> The authentication mode 'SQL Server and Windows' support two
authentication
> methods. You can specify the standard account after selecting 'SQL Server
> authentication'. Or, you can select 'Windows authentication' which doesn't
> require you to specify the account, because it authenticates with the
> account which you login on the operating system.
>
> If you have any further questions, please don't hesitate to contact me.
>
> Sincerely,
>
> Linda Deng
> Microsoft Support Engineer
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

Relevant Pages

  • Re: Login failed for ServerGuest
    ... | guest and the use of the same account/password does not ... |>I think it is not a limitation in Windows 2000. ... |>use same password for Administrator account on both Win2000 and WinXP ... although Windows Authentication is more secure than ...
    (microsoft.public.sqlserver.connect)
  • 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: User authentication
    ... With Windows authentication, ... an account is a member of Domain Admins. ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: Remote connection failed
    ... If you are going over a remote connection or are not logging ... into the domain where SQL Server is then no, Windows ... authentication won't work. ...
    (microsoft.public.sqlserver.connect)
  • Re: User authentication
    ... Server Agent service account. ... What I want to do is configure scheduled backup. ... However, if possible, I would like to use Windows authentication as opposed ...
    (microsoft.public.sqlserver.clients)