Error when using 'winexe' tool. Trying to invoke Windows commands via Linux server
Successfully installed winexe tool(link) but when executing the tool, the following command appears
#./winexe -U 'domainuser%pass' //ip "tasklist /V"
ERROR: Failed to open connection - NT_STATUS_CONNECTION_RESET
Any help? Found similar question in stack, but no answer.
Open for any other easy suggestions on how to invoke Windows commands via Linux server, preference from PowerShell.
linux windows powershell samba
asked Nov 5 '18 at 14:20
igorigor
1161117
add a comment |
Successfully installed winexe tool(link) but when executing the tool, the following command appears
#./winexe -U 'domainuser%pass' //ip "tasklist /V"
ERROR: Failed to open connection - NT_STATUS_CONNECTION_RESET
Any help? Found similar question in stack, but no answer.
Open for any other easy suggestions on how to invoke Windows commands via Linux server, preference from PowerShell.
linux windows powershell samba
asked Nov 5 '18 at 14:20
igorigor
1161117
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11
add a comment |
Successfully installed winexe tool(link) but when executing the tool, the following command appears
#./winexe -U 'domainuser%pass' //ip "tasklist /V"
ERROR: Failed to open connection - NT_STATUS_CONNECTION_RESET
Any help? Found similar question in stack, but no answer.
Open for any other easy suggestions on how to invoke Windows commands via Linux server, preference from PowerShell.
linux windows powershell samba
asked Nov 5 '18 at 14:20
igorigor
1161117
Successfully installed winexe tool(link) but when executing the tool, the following command appears
#./winexe -U 'domainuser%pass' //ip "tasklist /V"
ERROR: Failed to open connection - NT_STATUS_CONNECTION_RESET
Any help? Found similar question in stack, but no answer.
Open for any other easy suggestions on how to invoke Windows commands via Linux server, preference from PowerShell.
linux windows powershell samba
linux windows powershell samba
asked Nov 5 '18 at 14:20
igorigor
1161117
asked Nov 5 '18 at 14:20
igorigor
1161117
asked Nov 5 '18 at 14:20
igorigor
1161117
asked Nov 5 '18 at 14:20
igorigor
1161117
asked Nov 5 '18 at 14:20
igorigor
1161117
1161117
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11
add a comment |
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11
add a comment |
1 Answer
1
active
oldest
votes
Your winexe is probably using SMB1 dialect to connect, which is deprecated in modern windows versions.
Just for debugging purposes, temporarily enable SMB1 in Windows (hint:OptionalFeatures.exe) and try again. It should work, unless you also need to add "LocalAccountTokenFilterPolicy" to the registry.
Don't forget to disable SMB1 again.
There is a winexec binary with SMB2 support that works in Centos 7 against Windows 10:
http://dl-openaudit.opmantek.com/winexe-static
The source code that worked for me:
https://bitbucket.org/reevertcode/reevert-winexe-waf
Besides the README file, you should also read the 'BUILD' file, it contains additional information (patches to apply).
Good luck!
answered Jan 20 at 5:19
masimitomasimito
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f1372880%2ferror-when-using-winexe-tool-trying-to-invoke-windows-commands-via-linux-serv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your winexe is probably using SMB1 dialect to connect, which is deprecated in modern windows versions.
Just for debugging purposes, temporarily enable SMB1 in Windows (hint:OptionalFeatures.exe) and try again. It should work, unless you also need to add "LocalAccountTokenFilterPolicy" to the registry.
Don't forget to disable SMB1 again.
There is a winexec binary with SMB2 support that works in Centos 7 against Windows 10:
http://dl-openaudit.opmantek.com/winexe-static
The source code that worked for me:
https://bitbucket.org/reevertcode/reevert-winexe-waf
Besides the README file, you should also read the 'BUILD' file, it contains additional information (patches to apply).
Good luck!
answered Jan 20 at 5:19
masimitomasimito
1
add a comment |
Your winexe is probably using SMB1 dialect to connect, which is deprecated in modern windows versions.
Just for debugging purposes, temporarily enable SMB1 in Windows (hint:OptionalFeatures.exe) and try again. It should work, unless you also need to add "LocalAccountTokenFilterPolicy" to the registry.
Don't forget to disable SMB1 again.
There is a winexec binary with SMB2 support that works in Centos 7 against Windows 10:
http://dl-openaudit.opmantek.com/winexe-static
The source code that worked for me:
https://bitbucket.org/reevertcode/reevert-winexe-waf
Besides the README file, you should also read the 'BUILD' file, it contains additional information (patches to apply).
Good luck!
answered Jan 20 at 5:19
masimitomasimito
1
add a comment |
Your winexe is probably using SMB1 dialect to connect, which is deprecated in modern windows versions.
Just for debugging purposes, temporarily enable SMB1 in Windows (hint:OptionalFeatures.exe) and try again. It should work, unless you also need to add "LocalAccountTokenFilterPolicy" to the registry.
Don't forget to disable SMB1 again.
There is a winexec binary with SMB2 support that works in Centos 7 against Windows 10:
http://dl-openaudit.opmantek.com/winexe-static
The source code that worked for me:
https://bitbucket.org/reevertcode/reevert-winexe-waf
Besides the README file, you should also read the 'BUILD' file, it contains additional information (patches to apply).
Good luck!
answered Jan 20 at 5:19
masimitomasimito
1
Your winexe is probably using SMB1 dialect to connect, which is deprecated in modern windows versions.
Just for debugging purposes, temporarily enable SMB1 in Windows (hint:OptionalFeatures.exe) and try again. It should work, unless you also need to add "LocalAccountTokenFilterPolicy" to the registry.
Don't forget to disable SMB1 again.
There is a winexec binary with SMB2 support that works in Centos 7 against Windows 10:
http://dl-openaudit.opmantek.com/winexe-static
The source code that worked for me:
https://bitbucket.org/reevertcode/reevert-winexe-waf
Besides the README file, you should also read the 'BUILD' file, it contains additional information (patches to apply).
Good luck!
answered Jan 20 at 5:19
masimitomasimito
1
answered Jan 20 at 5:19
masimitomasimito
1
answered Jan 20 at 5:19
masimitomasimito
1
answered Jan 20 at 5:19
masimitomasimito
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.
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%2f1372880%2ferror-when-using-winexe-tool-trying-to-invoke-windows-commands-via-linux-serv%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
Have you checked all the prerequisites as described in your link1 and link2?
– harrymc
Nov 5 '18 at 15:11