Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not log onto a machine with any

Status
Not open for further replies.

RadioX

IS-IT--Management
Joined
May 15, 2001
Messages
145
Location
US
Can not log onto a machine with any known username. Looks as is someone has changed the information. Is there any way to get around this so I can restore access to the machine without redoing the OS. I do not have any emergency disk or anything like that.

Thanks
Ron
 
No, I don't think so.. You must not lose the administrators account logon information. If you do, you will be in trouble. There is much security built into the operating system to prevent unwanted logons...If you can not log onto the machine locally, your better off reloading the OS.

Is this computer connected to a domain? You may want to try to use the domain administrators account on this machine. I would try to logon to the domain from this machine as domain administrator. If that doesn't work, try to log on to this machines locally as domain administrator.

Hope this helps... Joseph L. Poandl
MCSE 2000


 
1. Assuming that you can logon with the administrator account, remove/re-add the computer to the domain. Otherwise, proceed to step 2.

2. If you can't even log on to the administrator account and are getting a message along the lines of &quot;<computername> domain could not be found&quot;, then it sounds like your High Encryption is corrupted - probably as a result of software that was installed just prior the start of your problem. If that's the case, you need to reboot to your recovery console (or if not a startup option, boot up to the W2K CD and choose the repair option. Once the command prompt appears, you want to have a good copy of the file 'Rsaenhs.dll' on a diskette and overwrite the bad copy located at C:\WINNT\system32 and you're done. Reboot and log on as usuall. Once in, you will probably have to address the problem with the software installed that caused the problem in the first place.

Hope this helps! ________
S. Joseph Vergara
SVergara@Texas.net
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top