PSEXEC remote to Win 10 - No process is on the other end of the pipe
up vote
2
down vote
favorite
I tried to use PSEXEC from a Windows 7 to Windows 10 PRO (not the preview).
PsExec.exe -i 1 -u myuser -p mypass \xxx.xxx.xxx.xxx cmd
Output
Error communicating with PsExec service on xxx.xxx.xxx.xxx
No process is on the other end of the pipe.
I have only one admin user (myuser) on the remote machine.
I can see the service PSEXESVC.exe being created and running. I stopped it, tried again, same result.
*I am using same command and same config (firewall disabled, LocalAccountTokenFilterPolicy to 1) on Xp,Win7,Win8,Win10Preview without issue.
windows-10 psexec
asked Jul 30 '15 at 11:22
user11099
11112
add a comment |
up vote
2
down vote
favorite
I tried to use PSEXEC from a Windows 7 to Windows 10 PRO (not the preview).
PsExec.exe -i 1 -u myuser -p mypass \xxx.xxx.xxx.xxx cmd
Output
Error communicating with PsExec service on xxx.xxx.xxx.xxx
No process is on the other end of the pipe.
I have only one admin user (myuser) on the remote machine.
I can see the service PSEXESVC.exe being created and running. I stopped it, tried again, same result.
*I am using same command and same config (firewall disabled, LocalAccountTokenFilterPolicy to 1) on Xp,Win7,Win8,Win10Preview without issue.
windows-10 psexec
asked Jul 30 '15 at 11:22
user11099
11112
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I tried to use PSEXEC from a Windows 7 to Windows 10 PRO (not the preview).
PsExec.exe -i 1 -u myuser -p mypass \xxx.xxx.xxx.xxx cmd
Output
Error communicating with PsExec service on xxx.xxx.xxx.xxx
No process is on the other end of the pipe.
I have only one admin user (myuser) on the remote machine.
I can see the service PSEXESVC.exe being created and running. I stopped it, tried again, same result.
*I am using same command and same config (firewall disabled, LocalAccountTokenFilterPolicy to 1) on Xp,Win7,Win8,Win10Preview without issue.
windows-10 psexec
asked Jul 30 '15 at 11:22
user11099
11112
I tried to use PSEXEC from a Windows 7 to Windows 10 PRO (not the preview).
PsExec.exe -i 1 -u myuser -p mypass \xxx.xxx.xxx.xxx cmd
Output
Error communicating with PsExec service on xxx.xxx.xxx.xxx
No process is on the other end of the pipe.
I have only one admin user (myuser) on the remote machine.
I can see the service PSEXESVC.exe being created and running. I stopped it, tried again, same result.
*I am using same command and same config (firewall disabled, LocalAccountTokenFilterPolicy to 1) on Xp,Win7,Win8,Win10Preview without issue.
windows-10 psexec
windows-10 psexec
asked Jul 30 '15 at 11:22
user11099
11112
asked Jul 30 '15 at 11:22
user11099
11112
asked Jul 30 '15 at 11:22
user11099
11112
asked Jul 30 '15 at 11:22
user11099
11112
asked Jul 30 '15 at 11:22
user11099
11112
11112
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57
add a comment |
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I almost gave up on Psexec because of this... but you might want to try connecting to Session ID 0 instead of 1. I've noticed some anomalies if (when...) Psexec ever gets hung up and decides to not delete itself (probably version related...) It gets 'locked' to SessionID 0 on the remote pc, and in my version 1.97, I am forced to specify SessionID 0 to interact with it again (or else reboot the remote pc). If running Psexec from script, you likely should specify SessionID 0 to avoid the situation.
Good luck!
answered Apr 19 '17 at 7:12
speroster
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I almost gave up on Psexec because of this... but you might want to try connecting to Session ID 0 instead of 1. I've noticed some anomalies if (when...) Psexec ever gets hung up and decides to not delete itself (probably version related...) It gets 'locked' to SessionID 0 on the remote pc, and in my version 1.97, I am forced to specify SessionID 0 to interact with it again (or else reboot the remote pc). If running Psexec from script, you likely should specify SessionID 0 to avoid the situation.
Good luck!
answered Apr 19 '17 at 7:12
speroster
1
add a comment |
up vote
0
down vote
I almost gave up on Psexec because of this... but you might want to try connecting to Session ID 0 instead of 1. I've noticed some anomalies if (when...) Psexec ever gets hung up and decides to not delete itself (probably version related...) It gets 'locked' to SessionID 0 on the remote pc, and in my version 1.97, I am forced to specify SessionID 0 to interact with it again (or else reboot the remote pc). If running Psexec from script, you likely should specify SessionID 0 to avoid the situation.
Good luck!
answered Apr 19 '17 at 7:12
speroster
1
add a comment |
up vote
0
down vote
up vote
0
down vote
I almost gave up on Psexec because of this... but you might want to try connecting to Session ID 0 instead of 1. I've noticed some anomalies if (when...) Psexec ever gets hung up and decides to not delete itself (probably version related...) It gets 'locked' to SessionID 0 on the remote pc, and in my version 1.97, I am forced to specify SessionID 0 to interact with it again (or else reboot the remote pc). If running Psexec from script, you likely should specify SessionID 0 to avoid the situation.
Good luck!
answered Apr 19 '17 at 7:12
speroster
1
I almost gave up on Psexec because of this... but you might want to try connecting to Session ID 0 instead of 1. I've noticed some anomalies if (when...) Psexec ever gets hung up and decides to not delete itself (probably version related...) It gets 'locked' to SessionID 0 on the remote pc, and in my version 1.97, I am forced to specify SessionID 0 to interact with it again (or else reboot the remote pc). If running Psexec from script, you likely should specify SessionID 0 to avoid the situation.
Good luck!
answered Apr 19 '17 at 7:12
speroster
1
answered Apr 19 '17 at 7:12
speroster
1
answered Apr 19 '17 at 7:12
speroster
1
answered Apr 19 '17 at 7:12
speroster
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f947481%2fpsexec-remote-to-win-10-no-process-is-on-the-other-end-of-the-pipe%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Well I started a brand new version of Windows 10, disabled firewall and set LocalAccountTokenFilterPolicy key. It works. :| I'll leave the question open if anyone has any clue.
– user11099
Jul 30 '15 at 11:57