After doing a lot of research on code, hacker attacks and reading a lot of websites and even discussing topics with MS, the root cause of the problem is that Microsoft has deleted SMB1.0 from Windows 8.1 and Windows Server 2012 R2. See: http//technet.microsoft.com/en-us/library/dn303411.aspx To get the deleted complete list. After spending as much time as possible (to make sure it lasts no less than a few days) studying winexe code, it seems that winexe uses smbclient's SMB 1.0 library.

    I'm sure I have the same problem with Windows 8.1 and Windows Server 2012 R2

    It looks like a problem between winexe and Windows 8.1. winexesvc seems to work normally. Can you check that smbclient works normally? Run it with the same credentials and try to connect to share// host / admin $, and use the - d 99 option to post the run log.

    I ran some custom commands to read and write remote named pipes, and to write and read ahexec pipes. PSExec also applies to 8.1.

    After doing a lot of research on code, hacker attacks, reading a lot of websites and even discussing topics with MS, the root cause of the problem is that Microsoft has deleted SMB1.0 from Windows 8.1 and Windows Server 2012 R2. See http//technet.microsoft.com/en-us/library/dn303411.aspx for a complete list of deleted items. After spending as much time as possible (to make sure it lasts no less than a few days) studying winexe code, it seems that winexe uses smbclient's SMB 1.0 library. For intentional backward compatibility, we use the lowest common Demoninator ourselves to ensure that as many people as possible can use my code.
    If, as I said, if SMB1 is not available, if it does not use SMB2 at least, then winexe or winexe-waf (built yesterday) will hit the wall. On this point, I hope you can refute me and put forward other opinions. smbclient has no problem communicating with sockets. I assume that the executable automatically tries to use the newer version of SMB...

    Execute in the shell:

    cat </dev/null|winexe

    It works, but why... I don't know either

    I tried your method and made the same mistake:

    ERROR: smb_raw_open_recv - NT_STATUS_INVALID_PARAMETER
    ERROR: on_ctrl_pipe_error - NT_STATUS_INVALID_PARAMETER
    ERROR: Cannot open control pipe - NT_STATUS_INVALID_PARAMETER

    I can tell you about the error that occurred when calling smbcli_request_is_error (req) in smb_raw_open_recv. Obviously req - > state is smbcli_request_receive (req) operation is no problem.

    I use it in shell scripts (cat </ dev / null | winexe)
    preusercmd.sh

    cat </ dev / null | $ WINEXE --uninstall --interactive = 0 -U $ UNAME -W $ WRKGRP 
    --password = $ PWD // $ BOX'cmd.exe /cc:backuppcpre-exec.cmd ' 

    It's useful for me.

    I tried this approach as you suggested, but with the same error message, do you run these commands with Windows 8.1 preview and/or Windows Server 2012 R2 preview (I use the latest version).

    I think Marks's suggestion is to address the problem that winexe does not use file redirection. As for your discovery of smb/smb2, I doubt it is the main reason, but I think I will not be able to finish this work in late August. Anyway, thank you for your research, it should be helpful for my patch development.

    I can wait a month or more. If I can find some excellent documents about samba (and possibly it), I can solve this problem by myself. Unfortunately, this is the first time I have been exposed to the internal operation of smba. There seems to be a lack of information about its developers. I'm sure I just missed something obvious.

    Bless you
    William M. Rawls 
    http://my.william-rawls.info

    Hey, hello, my boss asked me to ask you if winexe's support for Win8.1 could be achieved in August.

    Bless you
    William M. Rawls 
    http://my.william-rawls.info

    Yes, I hope it can be settled this week.

    Regards
    Andrzej

    I just uploaded a patch to solve this problem, at least on my machine. Please test it on as many machines as possible.

    Is the patch still useful?

    Patches have been applied to the current code. You can get the latest code:

    git clone git://git.code.sf.net/p/winexe/winexe-waf winexe-winexe-waf

    After compiling the source code, you can get winexe 1.1

    Follow your next steps, you must allow Netlogon to change firewall rules through the firewall to make it work, and then preview everything in Windows XP 32, 732, 764, 832, 864, Windows Blue preview, Server 2008 R2, Server 2012 and Server 2012 R2.

    VM XP cannot open the connection (psexec works)
    Change Firewall File Sharing Range Re-test Successful!

    VM 7 32 could not open the connection (psexec works)
    Failure to prevent NetLogon from retesting successfully

    VM 7 64 could not open the connection (psexec works)
    Failure to prevent NetLogon from retesting successfully

    VM 8 32 could not open the connection (psexec works)
    Failure to prevent NetLogon from retesting successfully
    VM 8 64 Lucky Firewall crashed, so it didn't encounter the same problem.
    VM Blue cannot open the connection (psexec works)
    Unblocked NetLogon Retest Successful

    VM 2008 passed 
    HV 2008 passed
    HV 2012 passed
    HV 12R2 passes

    Although cross-operating system testing is not very extensive, it still shows that the basics are applicable to all versions.

     1. We should always test winexe like this. What do you do?
     2. Why does psexec not work and there is no winexe (no firewall changes)?

    Thank you very much for your work in this area.

    1. I have a Hyper-V hypervisor (in my case Hyper-V) that has set up a virtual machine, and each operating system is used to test the code I wrote for our product. Therefore, it's easy to start ubuntu and other VM s and run the same winexe command on them.

    2. I would say that psexec does not send authentication like winexe 1.1. I have to check this out carefully, but winexe 1.0 is also applicable to all operating systems, except for the new operating system, which convinces me that winexe 1.1 requires netlogon services in the way that winexe 1.1 does not, but that's just a guess.

    How to work on Linux... I got msg NT_STATUS_INVALID_PARAMETER when I connected on Windows 8.1. I tried to compile the complete source but could not work on ubuntu. When will any patches or new winexe-1.1 for winexe-1.0.0 be released?

    Any patches for 1.winexe-1.0.0
            Sorry, No.

    2. When is the new winexe-1.1 being released?
            Build winexe 1.1-prerelease from source code (that is, from the "current" or "winexe-waf" git repository) and use it until winexe is officially released.