Hi there We're starting to play around with Win10 and I've noticed winexe doesn't seems to work against it - generates a NT_STATUS_BAD_INITIAL_PC error when connecting Looking around it seems like winexe really isn't maintained anymore? - which may be the reason it doesn't support Win10 as currently you can't even compile it against a current version of Samba4 (which presumably contains whatever changes are needed to solve this problem). The idea is great - I have tonnes of reasons to want to trigger Windows calls from Unix systems - so is there an alternative that people have moved to? Thanks -- Cheers Jason Haar Corporate Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
On 07/07/15 05:38, Jason Haar wrote:> The idea is great - I have tonnes of reasons to want to trigger Windows > calls from Unix systems - so is there an alternative that people have > moved to?Hello. I think I'm doing something similar with cygwin's sshd and a key pair. Probably the details can make the difference, but I had never heard of winexe before, so I cannot tell. bye av.
Possibly Parallel Threads
- samba-3.5.14 (and less) corrupting AD->UID mappings
- ongoing problems with winbind since we rolled out RODCs
- Failed to set servicePrincipalNames error
- Vista SP1-rc1 appears to break against Samba-3.0.27a
- NT_STATUS_INSUFFICIENT_RESOURCES - but only from Samba - works for Windows?