3

When I run SysInternals PSEXEC to launch a process on a remote machine, if I specify the password in the command line it fails with:

PsExec could not start cmd.exe on web1928:
Logon failure: unknown user name or bad password.

psexec \\web1928 -u remoteexec -p mypassword "cmd.exe"

or

psexec \\web1928 -u web1928\remoteexec -p mypassword "cmd.exe"

If I just specify:

psexec \\web1928 -u remoteexec "cmd.exe"

and type in the password it works just fine.

The originating server is Windows 2003 and the remote server is Windows 2008 SP2. The remoteexec account only exists on the remote server and is a member of the Administrators group.

Kev
  • 7,877
  • 18
  • 81
  • 108
  • 2
    Could it be that the password contains characters that need to the password to be in quotes? – John Gardeniers Apr 22 '10 at 21:42
  • @john - bingo mate! There's a dollar and a grave ($ and ^) in the password. Didn't think these would interfere. Make that an answer and I'll upvote and tick. – Kev Apr 22 '10 at 22:03

2 Answers2

4

Could it be that the password contains characters that need to the password to be in quotes?

John Gardeniers
  • 27,458
  • 12
  • 55
  • 109
2

If you don't provide a username your current authentication is passed through. When passing the -u paramater you may need to specify the username as DOMAIN\username. I am going to guess that psexec is trying to authenticate as the local account 'remoteexec' on the computer instead of a domain account like you expected.

Zoredache
  • 130,897
  • 41
  • 276
  • 420
  • Thanks for the reply. I did try specifying `WEB1928\remoteexec` as the user, but sadly no joy. – Kev Apr 22 '10 at 20:03
  • @zoredach - john's comment under the question nailed it. But thanks fort the suggestion. – Kev Apr 22 '10 at 22:04