Re: Can't logon to windows2000
From: Steven L Umbach (n9rou_at_nscomcast.net)
Date: 06/27/04
- Next message: JWC062604: "Re: Can't logon to windows2000"
- Previous message: Oli Restorick [MVP]: "Re: MS04-011 and NTOSKRNL.EXE version"
- In reply to: JWC062604: "Re: Can't logon to windows2000"
- Next in thread: JWC062604: "Re: Can't logon to windows2000"
- Reply: JWC062604: "Re: Can't logon to windows2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 26 Jun 2004 23:55:25 GMT
The link I showed shows exactly how to do that. Here are the basic steps.
Substitute your actual computer name for the locked out computer where I
show "computername". If you don't know the computers actual name, you should
see it in My Network Places on the good computer. Hopefully your working
computer is a Windows 2000 Pro computer or this will not work and stop after
verifiyng or not that you can access the C$ folder on the locked out
computer as described in the second sentence below. If you can at least
access the c$ folder there may be another option but I need to know the
operating system of your good computer. If you can not access the c$ drive
you will need to try to take it to someone who can slave the drive in
another computer running Windows 2000 or XP to try and repair it or
reinstall the operating system which can be done without destroying your
data but will require that you reinstall all of your applications, service
pack, and critical updates. Note that if you have any EFS encrypted files,
that a reinstall that is not an "upgrade" install will prevent you from ever
accessing them again unless you backed up your EFS privaye keys.
http://www.jsiinc.com/SUBG/TIP3300/rh3361.htm
First logon to your other computer with a logon name and password that
exists on the locked out computer that is an administrator on that computer.
Create the account on your "good" computer if need be.
In the run box type \\computername\c$ and then enter. If it brings up the
administrative share on the other computer which should show the whole drive
you are in. I am assumming c drive is where your operating system is at and
if it is not use the correct drive letter.
Go to the \winnt\security\database folder. First open the winnt folder and
then the others in the order shown. Folders are in alphabetical order within
a folder.This is called the "path". You should see a file called secedit.sdb
in the window to the right. Right click that file and select rename. Rename
it seceditold.sdm and hit enter.
Minimize the Explorer Window by selecting the minimize icon in the top right
hand corner. Now on your "good" computer go to the same folder path and find
the copy of secedit.sdb on it. Right click that file and select copy. Now
maximize the Explorer Window on your locked out computer and put your
pointer in the window to the right where you now have a file called
seceditold.sdb. Right click your mouse and select paste and you should now
see a copy of secedit.sdb from the other computer that you just copied.
Close your Explorer Windows and reboot the locked out computer to see if it
helps and let me know. --- Steve
"JWC062604" <anonymous@discussions.microsoft.com> wrote in message
news:2212e01c45bc1$8bc86b80$a001280a@phx.gbl...
> Steve:
>
> I actually do have another PC on my (2 PC) network. This
> is how I am communicating now. My purpose for the network
> was so both PC's could share the cable modem to the net.
> That's the only reason that I have the network.
>
> Are there other instructions possible with a PC on the
> network? Or how might a professional repair this problem?
> I would take the machine to a firm that only dealt with
> larger, corporate clients.
>
> Please respond.
> JWC062604
>
> >-----Original Message-----
> >See the tips in the link below. If you do not have a
> another computer on the network
> >you are going to need to try and replace the secedit.sdb
> file on your computer some
> >other way such as by putting your hard drive in another
> computer as a slave/secondary
> >drive or doing a parallel install of the operating system
> [best done into another
> >partition] in order to do the repair being very careful
> NOT to install over your
> >existing installation and do NOT format your drive, which
> you can delete when you are
> >done. Specifically what happened is either you removed
> groups from the logon
> >locally user right or added a group to the deny logon
> locally user right [more
> >likely]. --- Steve
> >
> >http://www.jsiinc.com/SUBG/TIP3300/rh3361.htm
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;266465
> >
> >"JWC062604" <anonymous@discussions.microsoft.com> wrote
> in message
> >news:21dd501c45ba2$07056480$a401280a@phx.gbl...
> >> I use my PC locally only so last night I was trying to
> >> bypass the Windows logon screen. I thought I had made
> the
> >> proper adjustments within "Local Security Policy"
> >> and "Users & Passwords" to allow for a straight boot up
> >> without the popup Windows logon box.
> >>
> >> This morning, when I booted up my PC, the Windows logon
> >> box still comes up so i went ahead and hit "OK" like i
> had
> >> always dine previously using Administrator as my ID.
> Then
> >> I got a popup message stating "The local policy of this
> >> system does not permit you to logon interactively."
> >>
> >> I hit OK and the above message keeps coming up. How can
> I
> >> go back and reset the logon settings the way they were?
> >>
> >> TY JWC062404
> >>
> >>
> >>
> >>
> >
> >
> >.
> >
- Next message: JWC062604: "Re: Can't logon to windows2000"
- Previous message: Oli Restorick [MVP]: "Re: MS04-011 and NTOSKRNL.EXE version"
- In reply to: JWC062604: "Re: Can't logon to windows2000"
- Next in thread: JWC062604: "Re: Can't logon to windows2000"
- Reply: JWC062604: "Re: Can't logon to windows2000"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
