hi,
The password hashes generated by pwdencrypt() for SQL7.0 & SQL2000 are
different. The password hash generated for SQL 2000 stores both the actual
passsword & it's upper case version (David Litchfield's article on cracking
SQL passwords). But the passwor hash for SQL 7.0 is of 16 bytes only. I
wanted to use the pwdencrypt() to generate the password hashes but want to
verify the values without sending the 'pwdcompare()' query to server. I
could do it for SQL 2000 but the SQL 7.0 hashes seems to be different.
Thanks.
Ajey.Those undocumented xp shouldn't be used in production. They're not supported
and subject to change by MS without notice (which has been changed in the
past). If you're looking a way to hash your password, take a look at this
udf (courtesy of Steve Kass).
http://groups.google.co.uk/groups?q...58-E7ADEA79360F
-oj
"Ajey" <ajey5@.hotmail.com> wrote in message
news:OuaWKJ2BFHA.2568@.TK2MSFTNGP10.phx.gbl...
> hi,
> The password hashes generated by pwdencrypt() for SQL7.0 & SQL2000 are
> different. The password hash generated for SQL 2000 stores both the actual
> passsword & it's upper case version (David Litchfield's article on
> cracking
> SQL passwords). But the passwor hash for SQL 7.0 is of 16 bytes only. I
> wanted to use the pwdencrypt() to generate the password hashes but want to
> verify the values without sending the 'pwdcompare()' query to server. I
> could do it for SQL 2000 but the SQL 7.0 hashes seems to be different.
> Thanks.
> Ajey.
>
Showing posts with label sql2000. Show all posts
Showing posts with label sql2000. Show all posts
Wednesday, March 7, 2012
Saturday, February 25, 2012
PASSWORD
I forgot my "sa" password for SQL2000. Is there some place to look to get
it back? (Enterprise Manager or Query Analizer) please help?This is a multi-part message in MIME format.
--=_NextPart_000_0167_01C3A9CF.CEBC57C0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Unless you removed the BUILTIN\Administrators group from the sysadmin role,
you can connect as a local Windows administrator on the server and use
Windows authentication to log into SQL Server. At that time, you can reset
the sa password.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"matta25" <matta125work@.hotmail.com> wrote in message
news:#1wbjkfqDHA.2820@.TK2MSFTNGP10.phx.gbl...
I forgot my "sa" password for SQL2000. Is there some place to look to get
it back? (Enterprise Manager or Query Analizer) please help?
--=_NextPart_000_0167_01C3A9CF.CEBC57C0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Unless you removed the =BUILTIN\Administrators group from the sysadmin role, you can connect as a local Windows =administrator on the server and use Windows authentication to log into SQL =Server. At that time, you can reset the sa password.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"matta25"= wrote in message news:#1wbjkfqDHA.2820=@.TK2MSFTNGP10.phx.gbl...I forgot my "sa" password for SQL2000. Is there some place to look =to getit back? (Enterprise Manager or Query Analizer) please help?
--=_NextPart_000_0167_01C3A9CF.CEBC57C0--
it back? (Enterprise Manager or Query Analizer) please help?This is a multi-part message in MIME format.
--=_NextPart_000_0167_01C3A9CF.CEBC57C0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Unless you removed the BUILTIN\Administrators group from the sysadmin role,
you can connect as a local Windows administrator on the server and use
Windows authentication to log into SQL Server. At that time, you can reset
the sa password.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"matta25" <matta125work@.hotmail.com> wrote in message
news:#1wbjkfqDHA.2820@.TK2MSFTNGP10.phx.gbl...
I forgot my "sa" password for SQL2000. Is there some place to look to get
it back? (Enterprise Manager or Query Analizer) please help?
--=_NextPart_000_0167_01C3A9CF.CEBC57C0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Unless you removed the =BUILTIN\Administrators group from the sysadmin role, you can connect as a local Windows =administrator on the server and use Windows authentication to log into SQL =Server. At that time, you can reset the sa password.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"matta25"
--=_NextPart_000_0167_01C3A9CF.CEBC57C0--
Pass-Through Authentication won't work when replicating via the ActiveX Library?
Hi all,
My sql2000 to sql2000 merge replication via internet is run via an
application on the subscriber using activex library.
I read about setting up pass-through authentication so that the user
accounts don't need to be on the same domain. So, I set up Sql Server
and Sql Agent to run on a user account set up identically on each
machine. But, it doesn't seem like the Sql Agent is even involved in
the communication on the subscriber.
Authentication at the publisher fails because it is trying to
authenticate - not the account that sql server and sql agent services
are running under - but the current windows account running on the
subscriber.
ie:
- sql server and sql agent running under "serviceAccount"
- windows user on subscriber machine logged in as "Joe"
- error at publisher = cannot authenticate Joe.
Now, if I create a Joe user on the publisher, with the same password as
on the subscriber, everything works. But this is an impossible setup to
work with because of course there will be many different unknown users.
Please, can anyone help with this? I can't find this problem
anywhere...
JJ
Its probably using the security context of the account you are logged in
under. If you were to run this program/script as a job spawned by SQL Server
agent it would work. Another option would be to use the run as command (have
a look at runas from the command prompt).
I think your best bet would be to use sql authentication though.
This could also be an rights issue when you connect to the snapshot share -
exactly what error message are you getting?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJ" <joe.jabour@.gmail.com> wrote in message
news:1121742075.969113.19600@.z14g2000cwz.googlegro ups.com...
> Hi all,
> My sql2000 to sql2000 merge replication via internet is run via an
> application on the subscriber using activex library.
> I read about setting up pass-through authentication so that the user
> accounts don't need to be on the same domain. So, I set up Sql Server
> and Sql Agent to run on a user account set up identically on each
> machine. But, it doesn't seem like the Sql Agent is even involved in
> the communication on the subscriber.
> Authentication at the publisher fails because it is trying to
> authenticate - not the account that sql server and sql agent services
> are running under - but the current windows account running on the
> subscriber.
> ie:
> - sql server and sql agent running under "serviceAccount"
> - windows user on subscriber machine logged in as "Joe"
> - error at publisher = cannot authenticate Joe.
> Now, if I create a Joe user on the publisher, with the same password as
> on the subscriber, everything works. But this is an impossible setup to
> work with because of course there will be many different unknown users.
>
> Please, can anyone help with this? I can't find this problem
> anywhere...
> JJ
>
|||Yes I'm pretty sure that it's a rights issue - i was seeing error 1326
(unknown user or bad password). Like you said, it's likely because it's
using the security context of the account that I am logged in under on
the subscriber. In fact, I know that's the issue, b/c if I change the
username and password of my windows account that i am logged in under
on the subscriber to match the publisher, everything works like a
charm. But this is an impossible setup for me.
The issue here is that this is supposed to be an installable
application (unknown users)using MSDE on the subscriber, and the
application is using the ActiveX library - so anything outside of the
control of what can be set up by an installation app won't be feasible.
Re SQL authentication, are you saying that if I change the SQL Server
setup on the subscriber to use SQL authentication instead of windows
authentication, that it might work?
JJ
|||Yes, I am suggesting you do both (SQL authentication on the publisher and
subscriber). You can also use a com component and have this component run
under different security credentials than the account the user is logged on
under.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJ" <joe.jabour@.gmail.com> wrote in message
news:1121776681.002861.67670@.o13g2000cwo.googlegro ups.com...
> Yes I'm pretty sure that it's a rights issue - i was seeing error 1326
> (unknown user or bad password). Like you said, it's likely because it's
> using the security context of the account that I am logged in under on
> the subscriber. In fact, I know that's the issue, b/c if I change the
> username and password of my windows account that i am logged in under
> on the subscriber to match the publisher, everything works like a
> charm. But this is an impossible setup for me.
> The issue here is that this is supposed to be an installable
> application (unknown users)using MSDE on the subscriber, and the
> application is using the ActiveX library - so anything outside of the
> control of what can be set up by an installation app won't be feasible.
>
> Re SQL authentication, are you saying that if I change the SQL Server
> setup on the subscriber to use SQL authentication instead of windows
> authentication, that it might work?
> JJ
>
|||SQL auth on both didn't work - It was still using the credentials of
the windows login on the subscriber.
Solution - I created a "launcher" application that starts the
application under credentials that match the publisher.
Thanks for the help.
|||Well, it worked on my LAN, but not when i tested it from outside the
LAN. Again, permission problems. Do I need to upgrade the server to a
domain controller?
JJ
My sql2000 to sql2000 merge replication via internet is run via an
application on the subscriber using activex library.
I read about setting up pass-through authentication so that the user
accounts don't need to be on the same domain. So, I set up Sql Server
and Sql Agent to run on a user account set up identically on each
machine. But, it doesn't seem like the Sql Agent is even involved in
the communication on the subscriber.
Authentication at the publisher fails because it is trying to
authenticate - not the account that sql server and sql agent services
are running under - but the current windows account running on the
subscriber.
ie:
- sql server and sql agent running under "serviceAccount"
- windows user on subscriber machine logged in as "Joe"
- error at publisher = cannot authenticate Joe.
Now, if I create a Joe user on the publisher, with the same password as
on the subscriber, everything works. But this is an impossible setup to
work with because of course there will be many different unknown users.
Please, can anyone help with this? I can't find this problem
anywhere...
JJ
Its probably using the security context of the account you are logged in
under. If you were to run this program/script as a job spawned by SQL Server
agent it would work. Another option would be to use the run as command (have
a look at runas from the command prompt).
I think your best bet would be to use sql authentication though.
This could also be an rights issue when you connect to the snapshot share -
exactly what error message are you getting?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJ" <joe.jabour@.gmail.com> wrote in message
news:1121742075.969113.19600@.z14g2000cwz.googlegro ups.com...
> Hi all,
> My sql2000 to sql2000 merge replication via internet is run via an
> application on the subscriber using activex library.
> I read about setting up pass-through authentication so that the user
> accounts don't need to be on the same domain. So, I set up Sql Server
> and Sql Agent to run on a user account set up identically on each
> machine. But, it doesn't seem like the Sql Agent is even involved in
> the communication on the subscriber.
> Authentication at the publisher fails because it is trying to
> authenticate - not the account that sql server and sql agent services
> are running under - but the current windows account running on the
> subscriber.
> ie:
> - sql server and sql agent running under "serviceAccount"
> - windows user on subscriber machine logged in as "Joe"
> - error at publisher = cannot authenticate Joe.
> Now, if I create a Joe user on the publisher, with the same password as
> on the subscriber, everything works. But this is an impossible setup to
> work with because of course there will be many different unknown users.
>
> Please, can anyone help with this? I can't find this problem
> anywhere...
> JJ
>
|||Yes I'm pretty sure that it's a rights issue - i was seeing error 1326
(unknown user or bad password). Like you said, it's likely because it's
using the security context of the account that I am logged in under on
the subscriber. In fact, I know that's the issue, b/c if I change the
username and password of my windows account that i am logged in under
on the subscriber to match the publisher, everything works like a
charm. But this is an impossible setup for me.
The issue here is that this is supposed to be an installable
application (unknown users)using MSDE on the subscriber, and the
application is using the ActiveX library - so anything outside of the
control of what can be set up by an installation app won't be feasible.
Re SQL authentication, are you saying that if I change the SQL Server
setup on the subscriber to use SQL authentication instead of windows
authentication, that it might work?
JJ
|||Yes, I am suggesting you do both (SQL authentication on the publisher and
subscriber). You can also use a com component and have this component run
under different security credentials than the account the user is logged on
under.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJ" <joe.jabour@.gmail.com> wrote in message
news:1121776681.002861.67670@.o13g2000cwo.googlegro ups.com...
> Yes I'm pretty sure that it's a rights issue - i was seeing error 1326
> (unknown user or bad password). Like you said, it's likely because it's
> using the security context of the account that I am logged in under on
> the subscriber. In fact, I know that's the issue, b/c if I change the
> username and password of my windows account that i am logged in under
> on the subscriber to match the publisher, everything works like a
> charm. But this is an impossible setup for me.
> The issue here is that this is supposed to be an installable
> application (unknown users)using MSDE on the subscriber, and the
> application is using the ActiveX library - so anything outside of the
> control of what can be set up by an installation app won't be feasible.
>
> Re SQL authentication, are you saying that if I change the SQL Server
> setup on the subscriber to use SQL authentication instead of windows
> authentication, that it might work?
> JJ
>
|||SQL auth on both didn't work - It was still using the credentials of
the windows login on the subscriber.
Solution - I created a "launcher" application that starts the
application under credentials that match the publisher.
Thanks for the help.
|||Well, it worked on my LAN, but not when i tested it from outside the
LAN. Again, permission problems. Do I need to upgrade the server to a
domain controller?
JJ
Subscribe to:
Posts (Atom)