Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > PsTools
  New Posts New Posts RSS Feed: PsExec could not start
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Topic ClosedPsExec could not start
 Post Reply Post Reply
Author
Message Reverse Sort Order
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121 		Direct Link To This Post Topic: PsExec could not start
    Posted: 04 July 2008 at 1:19am
<Mod>
elpasha's post has been moved into a separate thread, because
+ this thread is about psexec v1.70, the current version is v1.94
+ reviving a thread which has been dead for 2 years does not make sense
+ in particular as it is pretty unclear which problem elpasha really faces.
</Mod>

Edited by Karlchen - 04 July 2008 at 1:19am
Back to Top
Radsam View Drop Down
Newbie
Newbie
Avatar

Joined: 29 June 2006
Online Status: Offline
Posts: 2 		Direct Link To This Post Posted: 30 June 2006 at 3:56am

Thanks, but yes I am aware they are placeholders.

I got it figured out now. Many thanks!

Radsam



Edited by Radsam - 30 June 2006 at 6:21am
Back to Top
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121 		Direct Link To This Post Posted: 29 June 2006 at 4:48pm
If you get an "Access denied" error message by the command "dir \\target\Admin$", then I bet the previous command, "net use \\target\Admin$ /user:administrator" did not return successfully, either. Correct?

(Hope it is not too trivial, but you are aware that the terms "target" is a placeholder for the real name of your target machine (or its IP address)?
Similarly, "administrator" is a placeholder for any user having admin privileges.)

My network at home is a Workgroup and not a domain, if that matters.

Yes, it matters, but no, not in the sense that it prevents you from using psexec.
My home computers are not members of any domain, yet it is perfectly possible to launch psexec commands towards my company's domain based server machines, provided my logon credentials are OK.

Karl
Back to Top
Radsam View Drop Down
Newbie
Newbie
Avatar

Joined: 29 June 2006
Online Status: Offline
Posts: 2 		Direct Link To This Post Posted: 29 June 2006 at 6:23am

I have followed your directions and I get still get access denied when attempting to use: dir \\target\Admin$

My network at home is a Workgroup and not a domain, if that matters.

any ideas?



Edited by Radsam - 29 June 2006 at 6:33am
Back to Top
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121 		Direct Link To This Post Posted: 22 January 2006 at 7:58am
Hello, Jerome.

On your target machine check if
  • it is not running Windows XP Home. Windows XP Home is lacking some of the network functionality required by (most) PSTools commands
    (Jerome, I read that you are using WinXP Pro Sp2, so this is not for you, but others reading this.)

  • the Workstation service is running (check using services.msc)

  • the Server service is running (check using services.msc)

  • the Admin$ share is available (check using computer management)

  • the Windows Network is running and Printer and File Sharing are activated (no need to actually share anything)

  • Incomming network users authenticate as themselves
    To achieve this:
    (1) Turn off simple file sharing and thus turn on classical file sharing like on Win2K.
    (2) Turn of network users identify as guests and thus turn on network users identify as themselves like on Win2K.
    (Please, read how to configure authentication here.)

  • Note:
    Classical Network Authentication requires a non-empty password.
    If you have not already done so, assign the user who will logon to \\target a strong password.
    (This is recommended for security reasons anyway.)
    (Again, Jerome, this is not for you, read your statement about the complex password.)

  • Check your WinXP firewall settings. By default on WinXP Sp2 the firewall will block any incoming traffice. So it may be necessary to open ports 135 and 445 on your target machine for incoming traffic from your local machine.


As soon as your target machine meets all of the above listed requirements, from your local machine try to execute these commands to your target machine:

net use \\target\Admin$ /user:Administrator
dir \\target\Admin$
net use \\target\Admin$ /delete (only disconnects, does not delete anything.)

If these 3 commands work, then it should be possible to run psexec to \\target as well.

Let us know how it worked (or did not).

Regards,
Karl



Edited by Karlchen - 07 September 2007 at 3:21pm
Back to Top
furax View Drop Down
Newbie
Newbie


Joined: 21 January 2006
Online Status: Offline
Posts: 1 		Direct Link To This Post Posted: 21 January 2006 at 6:29pm

Hi there,

I've been successfully using psexec on several machines at work without any problem for years. I'm now trying to use it on a computer at home, when using psexec to run a command on the very same machine using 'psexec ipconfig' I got the following error:


PsExec v1.70 - Execute processes remotely
Copyright (C) 2001-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

PsExec could not start ipconfig:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

This is on a WinXP Pro w/ SP2, all security fixes. I'm *not* using simple file sharing, the account used is a member of the local admin group, the local admin account has a normal (i.e. excessively complex!) password. This issue seems similar to the one described on www.sysinternals.com/Forum/forum_posts.asp?TID=1904

I couldn't find anything obvious using filemon or regmon to trace down any issue, nothing is logged in event logs.

Thanks in advance for your help.

Cheers  /jerome

 
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down