Share via

The remote procedure call failed and did not execute

Matt 101 Reputation points
2022-07-27T14:34:58.053+00:00

Hi all,

I tried to run psexec on a remote windows 10 enterprise machine 10.1.1.1

psexec \10.1.1.1 ipconfig /all

and got the following "could not start psexec service on 10.1.1.1:
The remote procedure call failed and did not execute."

Any idea or any other way to do it?

Thank you!

Windows for business Windows Server User experience PowerShell
Windows for business Windows Server User experience Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. MotoX80 36,291 Reputation points
    2022-07-27T20:40:43.52+00:00

    An authentication failure would be the most likely problem. Are you able to access the C drive? 

    dir \\10.1.1.1\admin$

    Try adding administrator credentials with the -u and -p switches.

    RDP to the machine and check the system event log for service start failures and the security event log for authentication failures.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.