Re: Changing passwords / Blocking SA login attempts
From: Fox (fox@connexions.net)
Date: 02/13/03
- Next message: Fox: "When comparing a field name with a column name of more than one word"
- Previous message: Denny: "Re: Database Access from Active Directory to NT 4.0"
- In reply to: Fox: "Re: Changing passwords / Blocking SA login attempts"
- Next in thread: BP Margolin: "Re: Changing passwords / Blocking SA login attempts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Fox" <fox@connexions.net> Date: Thu, 13 Feb 2003 15:12:38 -0500
Hi,
This is a follow up which is more clearly explained (I Hope).
With the urgency I also posted it as a new thread.
I know this was my fault, not using common sense.
And I thank you for getting me started. With the next
answers I am sure I will be settled. So here is a copy
of the new post.
I went and did it. I followed some good advice, but did not understand it
entirely. Now I have issues ;)
This takes place locally in Enterprise Manager.
I went into the Server Config properties and changed to Windows
Authentication.
My login for Start and Run SQL server was in this format. [ .\myname ]
I am supposing this was an SQL authentication, but do not remember. I am a
newbie.
Does the format tell me that this was an SQL login since there is no domain
or machine name present ?
I ok' this as it was.
NEXT:
It appears that since my login and Password were probably not based on a
Windows 2000
account, Enterprise Manager lost connection and would no longer connect.. I
then
went in to the Edit Server registration properties and changed that to
Windows
Authetication. Now I rebooted Enterprise Manager and I am again connected.
The
Server Config properties still says Windows Authentication and my old login
is still
there. I am now afraid to close this since I have no idea what I have
actually done and
where I no stand. Can anyone straighten me out ?
Questions include whether to change the Config back to SQL authentication or
to
change the log in to a trusted windows login. What would the exact format be
if I change it to (I do not use a domain) machinename myname ?
If it matters to tell me, why was I able to get back in when I went into the
Edit Registration properties and changed to a Windows Authentication ?
I do not understand the difference or relationship between the Registration
(and its
properties) and the Server Config and its properties.
Thanks,
Fox
"Fox" <fox@connexions.net> wrote in message
news:OpT4AW50CHA.2488@TK2MSFTNGP12...
> OK, now I understand all the ramifications. I guess I can look into the
> templates
> and figure out how to change them. But I now have a more urgent issue.
>
> I did as you suggested, but now have a serious problem. Since I changed to
> Windows Authentication, I can no longer access Enterprise Manager.
>
> I am guessing that the Start SQL server account I had in there was not
> a Trusted Account. I had my name in there probably as an SQL
> authentication. Now that I screwed myself, what must I do to get
> back into Enterprise Manager ;)
>
> Regards,
> Fox
>
>
>
> "BP Margolin" <bpmargo@attglobal.net> wrote in message
> news:eiLlz1w0CHA.2296@TK2MSFTNGP10...
> > Fox,
> >
> > The authentication mode covers **all** connections to SQL Server. The
> > purpose of Windows Authentication is not just to "thwart" the sa account
> ...
> > that is simply a "side-effect" of changing to Windows Authentication.
> >
> > Windows Authentication is more secure because, for example, SQL Server
has
> > no mechanism to require that users periodically change passwords, or to
> > enforce password standards. Windows does have those abilities.
> >
> > Basically the idea behind Windows Authentication is that SQL Server
relies
> > upon the Windows operating system to authenticate that a user is who he
> says
> > he is. After that, the SQL Server administrator can choose which Windows
> > users or Windows groups to access the SQL Server databases. But the
basic
> > authentication process is left to Windows rather than to SQL Server.
> >
> > -------------------------------------------
> > BP Margolin
> > Please reply only to the newsgroups.
> > When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.)
which
> > can be cut and pasted into Query Analyzer is appreciated.
> >
> > "Fox Bortniker" <fox@connexions.net> wrote in message
> > news:OmCMaEw0CHA.2076@TK2MSFTNGP10...
> > >
> > >
> > > Great, that brought me to it. Just one question. I have a pre-existing
> > > set of templates running in a database that are in PHP. They are
> > > numerous and complex. They use my name for login via SQL. If I change
> > > the authentication to Windows where you said to do so, is that for all
> > > authentication or is that just for the SA account ? I am afraid that
if
> > > I change that, the other template will not allow me to log in as the
> > > admin for the application. Is this going to happen ? Will I need to
find
> > > out how to change the log in that is built into that set of templates
so
> > > I can change it as well ?
> > >
> > > Thanks,
> > > Fox
> > >
> > > *** Sent via Developersdex http://www.developersdex.com ***
> > > Don't just participate in USENET...get rewarded for it!
> >
> >
>
>
- Next message: Fox: "When comparing a field name with a column name of more than one word"
- Previous message: Denny: "Re: Database Access from Active Directory to NT 4.0"
- In reply to: Fox: "Re: Changing passwords / Blocking SA login attempts"
- Next in thread: BP Margolin: "Re: Changing passwords / Blocking SA login attempts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
