Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > PsTools
  New Posts New Posts RSS Feed - Please READ Before POSTING
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic ClosedPlease READ Before POSTING

 Post Reply Post Reply
Author
Message
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Status: Offline
Points: 17516
Direct Link To This Post Topic: Please READ Before POSTING
    Posted: 22 August 2008 at 7:07pm
(Props to Karlchen for collecting this info)
 
Use of PSTools and This Forum
  1. Please study the PStools web page carefully.

    It contains essential information about PSTools in general and a link to each of the PSTools commands:

    • PsExec - execute processes remotely
    • PsFile - shows files opened remotely
    • PsGetSid - display the SID of a computer or a user
    • PsKill - kill processes by name or process ID
    • PsInfo - list information about a system
    • PsList - list detailed information about processes
    • PsLoggedOn - see who's logged on locally and via resource sharing
    • PsLogList - dump event log records
    • PsPasswd - changes account passwords
    • PsService - view and control services
    • PsShutdown - shut down or reboot a computer
    • PsSuspend - suspend processes

    For those interested in a concise overview on the usage of all the PsTools utilities in one single article: please, have a look at Wes Miller's PsTools Primer.


  2. Check that your target machine meets the minimum requirements.

    Definitions:
    Local machine: the machine where you logged in and where you type in your PSTools command.
    Target machine: the machine where you want the PSTools command to execute something remotely.
    \\target: same as above, substitute "target" by the real machine name or by the appropriate IP address.

    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
    • 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.
    • 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.)
    • Make sure that the user who will execute the command on the target machine has got admin privileges.
    • Check your WinXP firewall settings. By default on WinXP Sp2 the firewall will block any incoming traffic. So it may be necessary to open port 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 a PSTools command to \\target as well.



  3. Check out the PSTools FAQs.

    Kindly take the time to check out if your issue is covered by the FAQs:
    *** FAQ: Common PSTools Issues ***



  4. Use the search feature in the PSTools forum.

    If you run one of the PSTools commands and receive an error message,
    paste this error message to the Search for field and
    set the Search Forum to "PSTools".
    Chances are not bad that other users reported the same issue before and that you will find a solution.



  5. If these options did not help, please post on the PSTools forum.

    Make sure your problem description is as precise as possible:

    Choose a descriptive title, e.g. "PsExec gives Network Path Not Found" instead of just "Psexec won't work".

    Make sure you include all relevant information, i.e.:

    • Exact windows version of the local machine,
      i.e. the machine where you typed the PSTools command.
    • Exact Windows version of the target machine,
      i.e. the machine where the PStools command is supposed to do something.
    • The exact version of the PSTools command you use.
    • The exact command line as you typed it.
      (You may of course disguise real names and passwords. No need to reveal confidential information.)
    • The exact error message which you received on the local machine.


Thanks a lot.

Edited by molotov - 11 November 2008 at 1:22pm
Daily affirmation:
net helpmsg 4006
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down