I have found that a number of problems with SMB resource publication can be solved by disabling the "HomeGroup Provider" service and setting "Function Discovery Resource Publication" to automatic. I don't know if it's germaine to your problem, as my problem was with discovery of other Windows 10 machines over SMB2/3 with SMB1 disabled, but all sorts of Windows machines started showing up properly when I disabled the HomeGroups service and made resource publication a default. HomeGroups seem to mess up regular LANManager (SMB) shares sometimes.
Let me know if this helps.
That worked. As you said, taking those actions on those two services caused my shared servers to show up immediately.
Hi folks
3 Get arounds to the Samba V4.11.x version(s) not showing (or serving) shares.
1) on "downgradeable" Linux / NAS systems downgrade 4 packages to samba 4.10.10-2, smbclient 4.10.10-2, libwbclient 4.10.10-2, ldb 1.5.6-2 (e.g...
Hi there
after trying all of the zillion suggestions on the Forum about getting an INBOUND connection from SAMBA (NAS Server) to access W10 shares (the OTHER way around from W10 TO the NAS wasn't a problem) it's finally working.
What I did was:...
Hi there.
After the latest set of Windows updates my SAMBA TO WINDOWS is working again -- note SAMBA TO WINDOWS --there never was any problem with WINDOWS TO SAMBA. I haven't changed / updated server for months now --stable and it doesn't change...
I have found with Windows 10 that if I make a drive or directory available for use over a lan, using standard windows shares, and then try to copy a file to or from an android device, it is very slow, and at best I get 4 Mbits/second.
However, if...