Re: Problems changing the password for the service account in SQL
- From: Jill <Jill@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 21:43:02 -0700
Uri,
Adding the domain account which runs SQL Server into SQL Server doesn't
make any difference. Note the account I use to logon to the server is a
local admin on the server and even this account cannot connect to the SQL
Server if it is running under the domain account. The domain account
domain\blah has the following group access Domain Users, Local
Admin-SQL(grants local admin to all SQL Servers), Logon Exec - exception from
account ager lock-out. On the server the account is assigned to the
following local admin rights: ACT Part of OS, Logon Batch, LOgon Service and
Replace Process Token.
--
Jill
"Uri Dimant" wrote:
Jill.
If I change the account running SQL to Local system everyone
can logon. Any idea what is going on?
It is because there is BULTIN\Administrstors Login that alllow access to
everyone who is a memeber of LOCAL Administrators Group
> connect to SQL Server are the domain account running SQL Server and SQL
Server accounts. No other domain accounts can access SQL. The
following
is
the error which we get " A connection couldn't be established. Reason:
login
failed for user (NULL) Reason: not associated with a trusted SQL Server
connection".
Let me understand you. You have a domaim account group that SQL Server
Services run under (you have a login in SQL Server DOMAIN/blblbla) , so now
you are saying that "no other domain accounts can access SQL" , so I think
you need to add this account to DOMAIN/blblbla group OR create a login for
this domain account in SQL Server
"Jill" <Jill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A0B3814-AB1A-4836-BC79-FB10B0944D86@xxxxxxxxxxxxxxxx
The account which SQL Server is running under is a Domain account and it
doesn't matter whether MSSQL Server is running Windows Authentication or
mixed security no one using a domain account can logon
--
Jill
"Uri Dimant" wrote:
Jill
What is an acoount MSSQL Server running under?
Is that Windows Auithentication or Mixed?
"Jill" <Jill@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C2E38E25-6D9F-4B25-A330-CAD4FF6C6AFE@xxxxxxxxxxxxxxxx
We are currently in the process of Moving all our SQL Server 2000
servers
from Windows 2000 using NT security over to Window2003 using Activity
Directory. We have migrated the Service account and password over to
the
new
domain and have installed SQL Server successfully using this account.
We
have now testing changing the password. We changed the password on the
domain controller and then in SQL Server and now the only accounts
which
can
connect to SQL Server are the domain account running SQL Server and SQL
Server accounts. No other domain accounts can access SQL. The
following
is
the error which we get " A connection couldn't be established. Reason:
login
failed for user (NULL) Reason: not associated with a trusted SQL Server
connection". If I change the account running SQL to Local system
everyone
can logon. Any idea what is going on?
--
Jill
- References:
- Re: Problems changing the password for the service account in SQL 2000
- From: Uri Dimant
- Re: Problems changing the password for the service account in SQL
- From: Uri Dimant
- Re: Problems changing the password for the service account in SQL 2000
- Prev by Date: Re: DTS Package - Destination server is now off domain.
- Next by Date: Re: sql2k5 security
- Previous by thread: Re: Problems changing the password for the service account in SQL
- Next by thread: Re: Problems changing the password for the service account in SQL 2000
- Index(es):
Relevant Pages
|
