1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Logon error...please help

Discussion in 'Legacy Windows' started by dragondreamer69, 2003/06/28.

Thread Status:
Not open for further replies.
  1. 2003/06/28
    dragondreamer69

    dragondreamer69 Inactive Thread Starter

    Joined:
    2003/06/28
    Messages:
    6
    Likes Received:
    0
    Not sure what happened, but I installed Windows update service pack 3 on Win2000 pro. I rebooted and got all sorts of stop errors, different dll's and such missing or corrupt. So I ran the repair process on the CD which repaired (or replaced) the damaged files. Now, when I reboot, I get the error "The system can not log you on now......Domain unavailable." Safe mode is the same way. I'm not exactly sure what to do here. I'm sure its because of system changes by the service pack and that I replaced the bad files with the ones originally on the disk. However, the fact remains that I can not logon to the system. Is there anyway around that? Possibly through the repair console? I really don't want to have to reinstall, but It's looking like I'm going to.:(
     
  2. 2003/06/28
    dragondreamer69

    dragondreamer69 Inactive Thread Starter

    Joined:
    2003/06/28
    Messages:
    6
    Likes Received:
    0
    I won't be online much longer...as this is giving me a headache trying to figure this out...lol. But I will be on later to read and respond to the replies, if any. As far as the repair console goes, I wasn't sure if there was a service I could disable or something like that, in order to be able to logon to my machine. Obviously, I don't have that problem with the machine I'm using now.
     

  3. to hide this advert.

  4. 2003/06/28
    dragondreamer69

    dragondreamer69 Inactive Thread Starter

    Joined:
    2003/06/28
    Messages:
    6
    Likes Received:
    0
    Hmmmm...maybe I have them stumped...no replies but my own. I guess I should mention that the machine in question is NOT on a network and is a workstation......Any ideas at all?
     
  5. 2003/06/29
    dragondreamer69

    dragondreamer69 Inactive Thread Starter

    Joined:
    2003/06/28
    Messages:
    6
    Likes Received:
    0
    Well. I had hoped to have a reply by now. But thanks for the views anyway, I guess. Well, I can't wait any longer to have that machine up and running so it's time to go wipe it clean and start all over again, that'll be the last time I download any service packs for awhile.
     
  6. 2003/06/30
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Sorry no one gave you any help on this. I was on vacation last week and only on occasionally.

    If you've already wiped it, too late for suggestions. If not, post back.

    Very possible that the logon line where you'd normally see the local machine name (for non-network logons) got messed up somehow and your system was looking for a location it couldn't find. I haven't used a stand-alone machine for a while but I think you have to show details or options or something to even see that line.

    For the future, weekends are sometimes strange on here. Lots of us look in regularly week days but not so regularly on weekends.
     
    Newt,
    #5
  7. 2003/07/07
    dragondreamer69

    dragondreamer69 Inactive Thread Starter

    Joined:
    2003/06/28
    Messages:
    6
    Likes Received:
    0
    Well, I did go ahead and wipe it clean and perform a fresh install. I tried to get it to show that information, but it would not allow me to edit it. It was grayed out. I guess that's because it is a stand alone machine and that information should not change. Thanks for the reply though. I'm not quite sure why it happened, but I'm guessing that when I downloaded the service pack, it must have had an interruption in the download which may have lost some information in the process. The pack was supposed to have contained some security issue patches, and those files or services affected by it may have been damaged and wouldn't allow me on the "domain ", or changed the "domain" name. Anyway, thanks again. I'm sure I will run into other problems in the future and will be back to post again.....that's the way it goes with microsoft...heh. :D
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.