Yes - the topic is "connecting WIN10 to SME9.2". I didn't set up a SME9.2 in a virtual Box but I believe, this guide could work also for the latest WIN10 build and for a SME9.2 server. Anyway, I could manage to add the WIN10-Workstation to an SME10 workgroup and I'm able to connect ibays to the workstation. Not working is the AD.
Here's what I followed/did:
1. Took the alpha3 SME10 iso
2. Grabbed the last i386 test-iso from M$ which is Build 17134.rs4_release.180410-1804
3. In virtualbox (host archlinux) I installed two guests. SME with two nics (one bridged, one intnet), the WIN10 with one nic and intnet. No promiscous mode anywhere.
4. In the SME-box I followed this:
https://wiki.contribs.org/Windows_10_Support#notes_about_Window_10_and_SME_Server_10:
config setprop smb ServerMaxProtocol NT1
expand-template /etc/smb.conf
service smb restart
The server is configured as Server and Gateway, Workgroup and Domain Controller is enabled, Roaming profiles are off. There's a test user, a group and an ibay.
5. I did not use any registry-patch from the SME side.
6. I installed WIN10 with a different user as the test user in the SME box. The user is per default a WIN10 admin. I disabled any firewall.
7. I followed this:
https://www.schkerke.com/wps/2015/06/windows-10-unable-to-connect-to-samba-shares/and:
8.
https://www.linuxliteos.com/forums/network/can%27t-access-samba-shares-from-windows-10-client/The latest build of WIN10 offers only two boxes to tick.
After re-booting the WIN10 workstation I was able to connect to the ibay as an SME user and also to add the WIN10 box to the workgroup of the SME10 server. The file-explorer of WIN10 shows correctly the SME server by the name of the server, the home of the user by the users name and the Primary ibay. Drive mapping of the ibay is working as expected.
Maybe it helps someone. Maybe all this is already known... I couldn't find information to this in one piece.
regards,
stefan
Edit: Sorry if the post is displaced, please move it to a better forum/sub-forum.