Mark Ridley

This is fixed now. I have made a fork that works with SMB2

Hi Colvin, I think you were getiing the NT_STATUS_OBJECT_NAME_NOT_FOUND message because SMB2 does not like the \ in the share names. SMB1 didnt seem to care. I have posted a full fix. Cheers, Mark

Finally got it all working. This is a SMB2 version only of winexe. It does not work with SMB1. The SMB3 code in samba is also a bit suspect as it works only about 10% of the time, but I am not fixing that yet. Let me know how you get on. It is based on Michael's Samba 4.4.5 fork. just type ./waf configure and ./waf build git source

Dentar / Colvin - Apologies for not checking forum for 3 days and seeing your messages. I'e had my head buried in winexe and samba source code. Drop me an email at mark_ridley@hotmail.com

Dentar / Colin - Apologies for not checking forum for 3 days and seeing your messages. I'e had my head buried in winexe and samba source code. Drop me an email at mark_ridley@hotmail.com

Hi Dentar, Thanks for sending that over. As mentioned above, I have got a new version of winexe working on SMB2, but having problems with the last little bit. It fails 9 out of 10 times. There is a timing issue somewhere and after 2 weeks, day and night I need some coding help. If I put -d99 in the winexe line to slightly slow it down, it works 50% of the time. it is reading from the named pipes from windows that is cauing the issue. Colvin - Another I had to change in the main winexe code was to...

Hi Colvin, Great to hear someone is also looking at this. I've got it to work...just. but there seems to be an issue in the async_read_recv code, but it may be down to the smb2_create. Most times I am getting an NT_STATUS_INVALID_PARAMETER returned in te read code. It works 1 in 10 times and all works great, but it is just not reliable enough, After spending weeks on this, I have just about given up, re-written the winexesvc_loop code to use temp files instead of pipes and getting winexe.c to open...