Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Win 2000 issue

  1. #1
    PHP/PostgreSQL guy
    Join Date
    Dec 2001
    Posts
    1,164

    Win 2000 issue

    Right on, now's the time to laugh at Vorlin, hehe. I helped a friend install windows 2000 and all related patches about two months ago. All was fine. Several small patches during the interim and nothing's gone wrong. She went on vacation over the past week and her son (a good friend of mine) was surfing on her machine Friday and Saturday. He swears up and down that he didn't do anything except go to several computer parts sites (he's in the case-looking mode) and conversion charts (mm to inches). On Opera, so it wasn't anything through IE downloading, etc.

    On Friday, all was fine. On Saturday, he said he couldn't get to any website (that doesn't necessarily mean anything in this problem, but it could be related). He got a rundll.exe fault which popped up the "Send error report?" message, but he didn't think to read it all at the time. The box is then shut down.

    Fast forward to today. He tries to start her machine up and at the login prompt, after logging himself in, he gets this message:

    "The local security policy on this machine does not permit you to log in interactively."


    I've done all the looking up I can do and every answer requires either an rconsole or domain admin account to fix. I'm not familiar with rconsole in windows environments nor is this machine on a domain (small network, IP based, nothing extravagant).

    What am I looking at doing to fix this? Will a reinstall over the top fix it? Will the repair console do anything? I've found several sites that show fixes, but they're all domain-related from what I've seen.

    Thanks in advance!
    We the willing, led by the unknowing, have been doing the impossible for the ungrateful. We have done so much with so little for so long that we are now qualified to do just about anything with almost nothing.

  2. #2
    Gray Haired Old Fart aeallison's Avatar
    Join Date
    Jul 2002
    Location
    Buffalo, Missouri USA
    Posts
    888
    Use the "Administrator" login and pass, does that work. I assume you do have at least one "admin" account on that box... don't you?
    I have a question; are you the bug, or the windshield?

  3. #3
    As aeallison mentioned, try using the Administrator account for the box itself if you haven't already. Hopefully, that wasn't the account that was being used full-time. I'm thinking that W2K will see the comp. name as the 'domain' and you should be able to fix the issue once in with the admin account for the box.

    Also, the W2K install disc should have a Repair option once you boot from the CD. You may end up having to give that a try.
    - Maverick

  4. #4
    AO French Antique News Whore
    Join Date
    Aug 2001
    Posts
    2,126
    I never try booting with the Recovery Console but I know it might be password protect. (Probably not by default on 2K) What you might try is to have another W2K or XP computer join the same workgroup that the BAD W2K and try to access it remotly. It'll ask you the login/password from the bad W2K computer and you might be able to access the computer Computer Management Console.. Never try that... Might work? Might not?

    Thinking about it, it's probably faster with a recovery console or re-installing
    -Simon \"SDK\"

  5. #5
    Senior Member
    Join Date
    Oct 2002
    Posts
    4,055
    First off, I'ma do what no one did and do what Vorlin said we would do:

    Right on, now's the time to laugh at Vorlin, hehe.
    HAHAHAHAAHHAHAHA! k, I'm done now. Anyways, it's apparent that a trojan (according to my estimation) was installed somehow or he went to a site that had a script-bug. In either chance, you could re-install or boot in safe mode and scan for viruses/trojan's. That would be my first guess. Also:

    Also, the W2K install disc should have a Repair option once you boot from the CD. You may end up having to give that a try.
    Try that, I never used the W2k install disk after installation on my friends laptop, but that could help fix the problem.
    Space For Rent.. =]

  6. #6
    Senior Member
    Join Date
    Mar 2004
    Posts
    113
    Hi,

    first try everything that has been already told by others, then if u have not tried group policy/local policy u might want to try that.

    Local policy is located in administrative tools

    and for group policy type mmc in start>run
    then in console click add snap in then choose group policy and then check in the user configuration or in the local policy in computer configuration windows settings. Note this option might not be available since u are not on Domain.

    Also U might want to add that particular user to the power users group and try.

    MRG.

  7. #7
    Senior Member
    Join Date
    Apr 2004
    Posts
    1,130
    If you have lost the win2k admin password, you will need to use a crack tool to get it.
    For a w2k DC, if you dont have DC admin password:
    http://www.jms1.net/nt-unlock.html
    Please be aware that you will reset local admin password on W2K server and AFTER boot on DC recover mode
    However, if you have more than one DC on that network:
    - shutdown all DC server except one
    - run crack tools and follow that guide (it works!) on the remain server
    - recover DC Admin password
    - bring all DC servers back

    Congratulations! you have hacked your own servers!
    Meu sítio

    FORMAT C: Yes ...Yes??? ...Nooooo!!! ^C ^C ^C ^C ^C
    If I die before I sleep, I pray the Lord my soul to encrypt.
    If I die before I wake, I pray the Lord my soul to brake.

  8. #8
    Senior Member
    Join Date
    Oct 2002
    Posts
    4,055
    Err.. that's one way to go about it however the issue isn't about his admin account's password being lost or stolen. And btw:

    Angelic is Senior member and Im still a little worm
    Do you two know each other or something? Just asking..
    Space For Rent.. =]

  9. #9
    PHP/PostgreSQL guy
    Join Date
    Dec 2001
    Posts
    1,164
    Well, as messed up as this is going to be, here's what happened after I posted. I received an email from her stating the same thing as you've all already read. I went over there before work, sat down, popped the Win2K CD in and was going to boot into the recovery console. I forgot to hit any key to boot and it went to the regular login, I hit enter just for S&G's and ...

    SHIGGITY BLAKOW BOOYAKAS!!!!!!

    ...it logged in without any problems. I did see the window saying "Applying security policy", then the desktop popped up. We had done absolutely NOTHING. I couldn't log in prior with the administrator account (does this occur when more than one account is considered administrator besides the administrator account?) hence why I brought the win2k cd over.

    Weirdest thing I've ever seen. Nothing was done, nothing got changed, nothing was found on virus or spyware scans, nothing...no idea what happened, why it broke, or how it got fixed.

    Thanks all for your help though, I've documented most of this to make sure I have notes for later use.
    We the willing, led by the unknowing, have been doing the impossible for the ungrateful. We have done so much with so little for so long that we are now qualified to do just about anything with almost nothing.

  10. #10
    Senior Member
    Join Date
    Feb 2002
    Posts
    130
    There is a tool called NTrights.exe that allows you to edit user rights from the command prompt, if you can get into the recovery console you can try that

    http://support.microsoft.com/default...b;EN-US;279664

    couldn't find a download link to it for 2k but this is the 2k3 one, chances are it will still work, as far as I know the a lot of the polcicies are configured in the same way, 2k3 just has extras.

    http://www.microsoft.com/downloads/d...displaylang=en

    [edit]
    Just seen it has already been fixed, I am too slow, must be getting old
    [/edit]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •