search

MicrosoftDocs / sysinternals

Content for sysinternals.com
http://sysinternals.com
Creative Commons Attribution 4.0 International
469 stars 259 forks source link

Error creating key file...: The network name cannot be found. #442

Open gewarren opened 3 years ago

gewarren commented 3 years ago

Issue moved from MicrosoftDocs/feedback#3683

From @enzedonline on Monday, September 6, 2021 1:21:20 PM

Describe the bug Running psexec (or psexec64) on local machine with -i and -s switch. Process fails with the error:

To Reproduce Steps to reproduce the behavior: eg psexec64.exe -i -s %windir%\system32\mmc.exe /s taskschd.msc

Output:

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

Error creating key file on [[local machine name]]:
The network name cannot be found.

Expected behavior Pre 2.3, this would run normally.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

gewarren commented 3 years ago

Issue moved from MicrosoftDocs/feedback#3683

From @welcome[bot] on Monday, September 6, 2021 1:21:21 PM

Thank you for creating the issue! One of our team members will get back to you shortly with additional information. If this is a product issue, please close this and contact the particular product's support instead (see https://support.microsoft.com/allproducts for the list of support websites).

gewarren commented 3 years ago

Issue moved from MicrosoftDocs/feedback#3683

From @claudiamendez on Tuesday, September 7, 2021 7:31:58 AM

.

foxmsft commented 3 years ago

Thanks for the report. Investigating and looking to produce a fix!

CosmicHazel commented 3 years ago

I have the same issue

psexec64 -i -s cmd.exe

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

Error creating key file on *******:
The network path was not found.

OS Name Microsoft Windows 10 Pro Version 10.0.19042 Build 19042

sevmonster commented 2 years ago

I also ran into this issue. Originally I was using PsExec 2.2 before upgrading to 2.34 to see if that fixed the issue.

Z:\bin\PSTools>.\psexec -i -s cmd.exe

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

Error establishing communication with PsExec service on SERVER:
The specified network name is no longer available.

Z:\bin\PSTools>sc stop psexesvc

SERVICE_NAME: psexesvc
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 3  STOP_PENDING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

Z:\bin\PSTools>sc delete psexesvc
[SC] DeleteService SUCCESS

Z:\bin\PSTools>.\psexec -s -i cmd.exe

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

Error creating key file on SERVER:
The specified network name is no longer available.

Z:\bin\PSTools>systeminfo
...
OS Name:                   Microsoft Windows Server 2016 Datacenter
OS Version:                10.0.14393 N/A Build 14393
...
Hotfix(s):                 12 Hotfix(s) Installed.
                           [01]: KB4601051
                           [02]: KB3199986
                           [03]: KB4054590
                           [04]: KB4486129
                           [05]: KB4535680
                           [06]: KB4540723
                           [07]: KB4550994
                           [08]: KB4562561
                           [09]: KB4576750
                           [10]: KB5001402
                           [11]: KB5005698
                           [12]: KB5004238
huytmb commented 2 years ago

I have same issue... Maybe, this issue is relative to the issue: https://twitter.com/michridn/status/1349023386161307652

"Theres a new issue when running 32 bit psexec on 64 bit is now. "

realprocrastinator commented 4 months ago

Hi, is there any update on this issue? :)

foxmsft commented 4 months ago

By the way, when this happens, is the Server service (check in services.msc) running?

realprocrastinator commented 4 months ago

By the way, when this happens, is the Server service (check in services.msc) running?

Yes, it is running in my case

image

KDAM71 commented 3 months ago

Thanks to the comment of realprocrastinator I was able to fix it for myself (windows home 11 23h2) by turning on "File and Printer Sharing for Microsoft Networks" in my network adapter properties (control panel>Network and Internet>Connections)

daemonjax commented 2 months ago

I can confirm that enabling "file and print sharing for microsoft networks" allowed the command to run.