runas - access denied

[Martin Miethe]

Hello Newsgroup!

I also have lots of problems getting RUNAS to work on a WindowsXP
Pro/SP2 machine.

runas /user:Administrator cmd.exe

does not work on a restricted user account (Access denied).

But when I switch to Administrator, the same command just works fine.

Now, can anyone please explain me this behaviour?



Thanks a lot and have a nice day

 

[Jon Phipps]

it could be the folder/file permissions. Check that the user/group
inquestion has access(read/execute) to both the file and folder(s) in
question. The windows tree is usually locked so that only members of the
administrators group and the system can make changes to it. I am not sure,
not ever having tried to run cmd.exe, from other than a power user or
administrator level account or from safe mode (command prompt or other
wise). Also check in LSP make sure that there are no software or security
rules preventing access to that file.

 

[ChRyman]

try: runas /userOMAIN\administrator cmd.exe - otherwise the runas
command might want the local admin password, rather than domain
password...


just a thought

 

[Martin Miethe]

it could be the folder/file permissions. Check that the user/group
inquestion has access(read/execute) to both the file and folder(s) in
question. The windows tree is usually locked so that only members of the
administrators group and the system can make changes to it. I am not sure,
not ever having tried to run cmd.exe, from other than a power user or
administrator level account or from safe mode (command prompt or other
wise). Also check in LSP make sure that there are no software or security
rules preventing access to that file.

hi,

it´s not just the cmd.exe, it happens with any file I want to "runas".
I also tried with several other tools - same result.

Except one:
I found a tool "SUperiorUser" which works for me. Once I run a program
in a different account using this "SUperiorUser" tool, the original
RUNAS works as well! But when I reboot the machine and try again with
RUNAS I get the old "Acess denied" with excactly the same command ....
I am really stuck here ...

 

[Martin Miethe]

okay, I found the solution:
the secondary logon service needs to be started!