question

pepak-5340 avatar image
0 Votes"
pepak-5340 asked pepak-5340 commented

PsExec after 2.20: "The network name cannot be found"

I am using PsExec to start an application under the system account:

 psexec -i -s -d cmd.exe /c c:\far\far.exe

This form works fine with PsExec 2.20 but fails with "Error creating key file on <COMPUTERNAME>. The network name cannot be found" error on all newer versions that I could find, including 2.34. Now I am not too surprised that I get a network-related error because my firewall is set up to prevent most network access and since I removed the administrative shares, but I don't see a reason why running a process under the system account should require a network access - and apparently it doesn't since PsExec version 2.20 can run the command just fine. I can only assume that the change was done to facilitate some network-related stuff, which is just fine if someone needs it, but is there a way to make PsExec work in the local-only fashion as it used to?

windows-sysinternals-pstools
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Apparently there have been multiple changes in the execution - if I try to run the 2.34 version of PsExec, it installs a service which subsequently blocks the proper execution of 2.20 PsExec. Once I stopped and deleted the service, I could run 2.20 correctly once again.

1 Vote 1 ·

0 Answers