Archived from groups: microsoft.public.windowsxp.security_admin (
More info?)
You're welcome, Tim. Somehow I suspect we should have all thought of System Restore a bit earlier :-(
--
Doug Knox, MS-MVP Windows Media Center\Windows Powered Smart Display\Security
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
"Tim Z" <magna03@swbell_REMOVETOREPLY_.net> wrote in message news:5cv681tgblbkaeg0k9gu1r8utfnv10m1vo@4ax.com...
> On Wed, 11 May 2005 23:34:31 -0700, "Kerry Brown"
> <kerry@kdbNOSPAMsys-tems.c*a*m> wrote:
>
>>"Tim Z" <magna03@swbell_REMOVETOREPLY_.net> wrote in message
>>news:kvk581dv4bamok2g5ffncg4rlrq9lh5rd7@4ax.com...
>>> On Wed, 11 May 2005 20:59:37 -0400, "Doug Knox MS-MVP"
>>> <dknox@mvps.org> wrote:
>>>
>>>>Tim,
>>>>
>>>>The situation you're describing is typical if a computer is joined to a
>>>>domain, and then removed, without creating a Local user account that can
>>>>access the computer without validating against the domain. This can also
>>>>apply if your IT department did not allow caching of logon credentials.
>>>>
>>>>Changing the machine name of the computer, or the workgroup name will not
>>>>cause any password changes.
>>>>
>>>>Alternatively, you may not have been in a domain and inadvertently told it
>>>>to join a domain. The same thing would apply. There is no domain to
>>>>validate your logon, so you can't log in.
>>>
>>> Ok, now that I understand. Thanks for the explanation sir.
>>>
>>> Now, wouldn't that also hamper the administrator logon? What I mean
>>> is, is the fix as simple as logging on as administrator and resetting
>>> the computer name or is the process more involved than that?
>>>
>>> Thank you.
>>>
>>> Tim
>>> Tim
>>> magna03@swbell_REMOVETOREPLY_.net
>>> (remove "_REMOVETOREPLY_" to reply)
>>>
>>> The United States Constitution © 1791. All Rights Reserved.
>>
>>You have to logon to the local machine instead of the domain. It sounds like
>>you were previously logging on to a domain. At the logon screen is there an
>>options button? If so click on it. You should now have a third text entry
>>field with a drop down list. Use Administrator as the user name. Try leaving
>>password blank or if you know the administrator account password type it in.
>>In the drop down list pick the name of your computer. If the administrator
>>password is not blank and you don't know it then you are out of luck until
>>you are connected to the domain again. You'll have to get your IT department
>>to do it. If you are using the Welcome Screen to log on then you weren't
>>connected to a domain and something else is happening. You can to the
>>administrator account by booting into safe mode and see what has happened.
>>If you can log on in safe mode try to change things back to what they were
>>before.
>>
>>Kerry
>>
>
> Yes I was (and now am again) in a domain. I want to thank all who
> tried to enlighten me.
>
> From a link I found, I made a boot cd and changed the admin's
> password and then logged on under admin. then I fooled around with it
> trying to get the workgroup name changed to workgroup (which I wasn't
> even supposed to do). After all was said and done at 300am this
> morning I got the bright idea to go to system restore and restore to a
> previous time. Now I can logon like I used to and all is well in my
> world at the moment.
>
> I really didn't want to tell my IT people (who are in another state)
> that I am an idiot. I'll just let them think I am competent and only
> myself and you folks will know the truth.
>
> Well, again, thanks all.
>
> Tim
>
> Tim
> magna03@swbell_REMOVETOREPLY_.net
> (remove "_REMOVETOREPLY_" to reply)
>
> The United States Constitution © 1791. All Rights Reserved.