Re: Connections errors

From: joseph (anonymous_at_discussions.microsoft.com)
Date: 11/21/03 

Date: Fri, 21 Nov 2003 11:35:01 -0800

" Reason: Unknown user name or bad password"
" User Name: aa225502"
" Domain: CONS"
" Logon Type: 3"
" Logon Process: NtLmSsp "
" Authentication Package: NTLM"
" Workstation Name: W1012108A "

>-----Original Message-----
>What's the exact error message from the NT security event
log ? Do you know
>if the clients generating the errors are using Named
Pipes or TCP/IP ?
>
>--
>HTH
>
>Jasper Smith (SQL Server MVP)
>
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"joseph" <anonymous@discussions.microsoft.com> wrote in
message
>news:018501c3b049$d4d6e460$a101280a@phx.gbl...
>Thanks for you post, however you are missing what the
>problem is. The users connect using their SQL Server
>accounts and not the NT domain account. They have been
>doing that fine for a long time and I am not about to
>change that. The problem is that somehow somewhere an
>attempt to establish connection using the NT domain
>account is occurring and we need to find how that is
>happening and stop it. The attempt to connect with the NT
>account is not a voluntary attemp. It is happening just
>because the user has Enterprise Manager open. That is
>only explanation I can find.
>>-----Original Message-----
>>"joseph" <anonymous@discussions.microsoft.com> wrote in
>message
>>news:0bfb01c3b045$d3c79410$a401280a@phx.gbl...
>>> We've recently migrated to SQL 2000 and ever since
we've
>>> been observing connection errors that we can trace back
>to
>>> the user's NT domain account. The security event log
on
>>> the server is filling up with connection errors for
>these
>>> NT Domain ID's which are associate with the users that
>>> have Enterprise Manager open. Somehow, enterprise
>manager
>>> is initiating a connection using the usrer's NT Domain
>>> account which was not set up in the SQL Server. The
>users
>>> are assigned a SQL login name which they use without
any
>>> problems. The problem is with these shadow connection
>>> attempts using the NT user's domain account which fail
>and
>>> generate an entry in the event log.
>>
>>It's likely that you need to grant the NT User accounts
>proper sql server
>>login access and database permissions.
>>
>>You may be seeing attempts for the NT account to connect
>to the server
>>itself through Windows Authentication.
>>
>>Steve
>>
>>
>>.
>>
>
>
>.
>

Relevant Pages

  • Re: Problems changing the password for the service account in SQL
    ... Adding the domain account which runs SQL Server into SQL Server doesn't ... Server if it is running under the domain account. ... Admin-SQL, Logon Exec - exception from ...
    (microsoft.public.sqlserver.security)
  • Re: Problems changing the password for the service account in SQL
    ... It is because there is BULTIN\Administrstors Login that alllow access to ... You have a domaim account group that SQL Server ... this domain account in SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Get "credentials not valid" message installing SQL2008 Failver
    ... The user account (domain account) has to be pre-created. ... The network name gets created during the install process. ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.setup)
  • SQL services failing on startup
    ... The services are set to autostart using a windows account. ... The account is restricted to logon only to computers ... for several months, the last two weekends, SQL Server has failed to startup ... The domain account was a member of the local admin group. ...
    (microsoft.public.sqlserver.server)
  • Re: Connections errors
    ... Jasper Smith (SQL Server MVP) ... accounts and not the NT domain account. ... >> been observing connection errors that we can trace back ...
    (microsoft.public.sqlserver.security)