1

I amn trying to test out how PsExec work. However, even when I'm trying to simply send a 'echo Hello', with the correct password and everything, it says that couldn't access the other computer.

Here's what my command looks like:

C:\PSTools>psexec \\COMPANY-PCNN -u "COM Pany - PCNN" -p PCNN echo Hello

PsExec v2.2 - Execute processes remotely
Copyright (C) 2001-2016 Mark Russinovich
Sysinternals - www.sysinternals.com

Couldn't access COMPANY-PCNN:
Access is denied.
Saaru Lindestøkke
  • 5,515
  • 8
  • 30
  • 48
MarcolinoIM
  • 11
  • 1
  • Not an expert, but could it be that the user should perhaps be specified with a domain (e.g. `"domain\COM Pany - PCNN"`) – Saaru Lindestøkke Jan 08 '19 at 15:11
  • That (include the domain) seems correct because a local user account on the target system will be the default. In addition, I suggest getting out of the habit of including the password in the plain-text command, and instead get prompted for it instead (and this would also verify if it is trying to use a local account on the target system or the domain account.) – Debra Jan 08 '19 at 20:33
  • For the time being I have put on hold researching PsExec. I will try it again later. Thanks anyway – MarcolinoIM Jan 09 '19 at 13:28
  • 1
    Gotta ask: Why do your usernames have spaces? Passwords can have spaces because... because. But to to spaces in a username just seems to me to be asking for problems. Yes, they are officially supported in an AD environment, but EVERY best practice source out there will strongly recommend against them for, among other reasons, precisely what you're experiencing here. – music2myear Jan 10 '19 at 16:30

0 Answers0