Error establishing communication with PsExec service on LAPTOP-L9QUVJQ4: can not find network。

Question

My operating system is windows 10 enterprise edition when running commands

PsExec -s -i mmc /s taskshd.msc

An error will be reported and the network cannot be found

If anyone encounters the same problem, please tell us the solution in detail. Thank you very much

Answer 1

Hello @Young Sunny ,

Thank you for your question.

A known solution for this exact error is to kill any rogue psexecsvc.exe process on the target machine. While this works for remote callers, I suspect it can also solve local issues.

If psexecsvc.exe hangs after using psexec, something is probably wrong, such as an application crash or simultaneous remote executions with incompatible versions.

Some things to look at are;

1) Clean up older instances of psexecsvc.
2) Make sure you have the latest version of pstools.
3) Make sure you use the same versions of psexec on all your machines.
4) Use the scavenging process to find out what events are leaving the psexecsvc process running. psexecsvc.exe should automatically exit and remove itself from %windir%, where it is temporarily placed at runtime.

Cleaning up fake copies:

1) Check the %windir% directory and make sure there are no harmful files there.
2) In some reported cases, psexecsvc is being incorrectly copied to the %% windir% \ system32 directory. If that's the case and it continues to happen, look at your environment variables, user profiles, and credentials. The path is based on "Admin$" and should be %windir%.

Workarounds if all else fails:

1) Find a way to terminate the psexecsvc.exe process as part of the cleanup.

2) provide a top level username/password that is an administrator on the target machine and has domain level access to mapped network drives (where the .bat file was located).

If the answer was helpful, please don't forget to vote up or accept as an answer, thanks.

Yours sincerely,

Samuel

Answer 2

Hi,

Is the command exactly the following?

PsExec -s -i mmc /s taskschd.msc

What is our purpose to run the command? Regularly, we run a similar command like this:

PsExec \serverlab01 -s -i cmd /c mkdir c:\temp000

which will copy PSEXESVC.exe to \serverlab01\admin$, establish a pipe to get the return code of the executed application (0 stands for success)

If the error is The network path was not found, we can check if we can access \serverlab01\admin$

-i switch is to specify the session number, if omitted, the console session is used. Thus, here's some samples frequently used.

PsExec \serverlab01 -u <domain\username> -p <passwd> -i 2 notepad

PsExec \serverlab01 -s -i 2 mmc /s taskschd.msc

Alex
If the response is helpful, please click "Accept Answer" and upvote it.