How to work around misplaced Administrator password 1

[Actsh]

Folks,

Recently had to ship a server to another company. This server would have been originally a member server in Domain A. The recipient Company took delivery of the server with the intention of migrating it to Domain B but cannot log on as it seems that the local administrator password had been chnaged recently and not documented - cardinal error but it's happened.
Is there any way of resetting the local Admin password?
Any help would be appreciated.

BR, Actsh

 

[SilviaS]

http://home.eunet.no/~pnordahl/ntpasswd/

This util will allow you to change the password

 

[lawndart]

You can use the NTDSUTIL or setpwd.exe to reset the password.

See:

http://support.microsoft.com/default.aspx?scid=kb;en-us;223301

-

 

[SilviaS]

We are talking about logging on using the local Admin password!

 

[Bungle76]

2 ways I can think of that work with workstations and I don't see why they shouldn't wouldn't work with a server, as long as you have full admin rights on the machine you are doing this from.

1) Either use the cusrmgr.exe utility provided with the Windows 2000 server resource kit

2) Use a remote instance of the "at" command:

- On any machine (with admin rights)

- Schedule an at scheduler command pointing to the machine you want to change

Syntax (without quotes) “at \\machine time net user administrator password”

Replace \\machine with machine name time with the time to run and password with the password you want to set to

For instance – "at \\server01 15:15 net user administrator laptop" executed from your machine will reset server01's local admin password to “laptop” at 15:15hrs.

Hope this helps.
Regards,
Colin Anderson

 

[nils1]

Hi,

I can't manage to get the "pass-through authentication" feature of IIS 6 working. This is the simple configuration:

step 1)

I create a folder on server "server_a" (win 2003 standard), NTFS security settings: only user "user_x" has full access, this folder is shared as "\\server_a\remote"

step 2)

On server "server_b" (win 2003 standard with IIS 6) I start the IIS manager, at the level "server_b/web sites/default web sites" I create a new "virtual directory" named "remote". The "web site content directory" is the UNC of the shared directory from step 1: "\\server_a\remote", in the windows "security credentials" I omit the username and password - instead I select the option "always use the authenticated user's credentials when validating the access to the network directory", in the window "virtual directory access permissions" I select "read" and "run scripts (as ASP)"

step 3)

then I configure the tab "directory security" of the new virtual directory: under "authentication and access control" I press the "edit" button and select only the option "integrated windows authentication" (no "anonymous access" and no "basic authentication")

Now logged in as "user_x" I try to access the shared folder on "server_a" via the IIS6 on "server_b" :

http://server_b/remote

(using IE6, WinXP SP2) ... unfortunately without success: first of all I get a window asking me for username and password (why ? I checked the option "integrated windows authentication" - so the system should know my credentials ?!?) but even if I enter my credentials I can't get access to that share: "HTTP Error 401.3 - You are not authorized to view this page".

As long as the resource is located locally on the webserver, the "pass-through authentication" feature works for me and entering a specific account as security credentials for the remote web resource (in step 2) is also working. BUT the "always use the authenticated user's credentials when validating the access to the network directory" thing does not ...

Maybe I missed something important in the configuration ?

regards
Nils

 

[martyh]

If its a DC (or was) and you ever need to get into DS restore mode you are screwed. And of course you can't log on locally anyway. I would rebuild.

Marty
Network Admin
Hilliard Schools

 

[NickFerrar]

Silvia's solution should work fine, there's a lot of Linux-based boot floppy programs available out there to do this. I used one a few months ago (and it worked great) but can't remember the exact one...