Reload the Samba configuration: # smbcontrol all reload-config Setting Share Permissions and ACLs. It is recommended to grant the privilege to a group instead of individual accounts. Let me know if it works. There are five basic tasks that can be accomplished using Samba. Just check you have smb1.0/CIFS File sharing support enabled in Control Panel\All Control Panel Items\Programs and Features > Windows Features, should be ticked by default however worth checking. Network Nothing has been merged/rebased into master so far. I can Map a network drive to the share. The guide has now been updated to use a different branch (feat-discovery), which will resolve that reboot issue. Everything worked as advertised except the status numbers were different and I had an extra line of warnings. So my desktop is seeing the other Win10 laptops, but still not showing Samba. No special warning, looked like it’s working but it didn’t. Save and exit (press CTRL + X, press Y and then press ENTER). I also checked on my 2 Nvidia Shields and they are not seeing the shares/server under the SMB mounting section in Kodi. If the permissions are as above, you do not need to change anything, if not, change it to just allow, Modify, Read & execute, List folder contents, Read, Write, Active Directory (AD) domain controllers (DC), To enable accounts other than the domain user, Log on to a Windows host using an account that has the, Enter the name of the Samba host and click, A windows security box should open, asking if you want to continue, Click, Log on to a Windows host using an account that has. Can you check your Samba service status? Open wsdd.service in nano and comment out User=nobody and Group=nobody with a ; semicolon. I haven’t looked into the package, but I assume the user-contributed Ubuntu/Debian package does not include the development version but an officially released one from the master branch. You should also make sure Samba is already installed and running on Ubuntu. Hopefully the Samba gurus will get their socks on and implement this discovery process soon. Several guides and YouTube videos I’ve researched suggest manually enabling SMB 1.0 in Windows 10 in order to make other Ubuntu machines visible in Windows File Explorer. When trying to open a network Samba share, I kept getting this error: Network Error: Windows cannot access \\hostname. You will need sudo privileges on the Ubuntu machine to install the wsdd service. Samba kan også virke som en Windows domenekontrollør. If you had already installed the master branch, please follow section “How to Uninstall wsdd” and then reinstall by following section “Installing WDS on Ubuntu”. © DevAnswers Network Discovery is enabled on Private and so is “Turn on automatic setup of network connected devices”. Not sure if that would cause any problems with seeing the Samba share. I would not have even tried without your guide. I have to start it manually myself. Depending on what type of Samba server you require, see: The file system, the share will be created on, must support: For further details, see File system support. Only users and groups having the SeDiskOperatorPrivilege privilege granted can configure share permissions. I must have missed an ironically-described “intuitive step” along the way. All other Linux machines as well as macOS can discover this registration automatically. Ran it on ubuntu server 20.04 – nearly clean install. But I have to state that it’s the half of the path as the Linux device itself does not see any Windows device in its “Network”. So it may happen that this feature gets integrated into Samba at some time in the future. Works great. I wish I could’ve merely edited my original comments so these added ones are not separate, however, the “waiting for approval is the slowdown and I didn’t want to bother anyone with my mistakes, as one comment would’ve allowed. I have now updated the guide to use the master branch as these CPU and race issues seem to be resolved in 0.6. After a bit of “guesstroubleshooting” (I am not python fluent, by far!) KUDOS! I am seeing the Ubuntu 18.04 sambashare folder and its files (in both This PC and Network/ubuntu-ipAddress) however, when opening or editing the one-liner test files, they have no lines in them at all. ahh, what a pleasure to follow a perfectly created guide and see success right away. Stop using SMB1 . You can find out by checking the service with: Also make sure you have at least one folder shared in Ubuntu. Can you see other Win 10 shares for example? It would be great if you could update your post here, because your detailed step by step instructions are very helpful for people like me. But still no luck on it showing up under Explorer – > Network. If you want to completely uninstall wsdd, stop and disable the service. I then uninstalled and installed the feat-discovery branch and installed fine. You may need to restart the Windows 10 machines to force discovery. Except on my cellphone. Read my Ezoic review to find out how. This means that if you use the winbind 'ad' backend on Unix domain members, you must add a uidNumber attribute to users, or a gidNumber to groups in AD. I replaced the /usr/bin/wsdd file with the v0.6 wsdd.py and everything is OK now. Let me leave a small hint: please correct the swapped letters in headlines for wsd “WDS”. Still no luck with the Ubuntu Samba server or share showing up. "Windows 10" and related materials are trademarks of Microsoft Corp. My first files (in the old sambashare path) had the same names (as the ones in the new sambashare path) and were created with touch (so were empty). This enables Samba hosts to be found by Web Service Discovery Clients like Windows 10. after 3 days of following different guides for connection problems between ubuntu and win10 (without success except loosing my mind) i found this awesome explanation. What do I need to edit to remove or fix those errors? This enables you to add and revoke the privilege by updating the group membership. CGroup: /system.slice/wsdd.service That’s life. No discovery and the service puts a 100% load on one core permanently. Perfect guide – thanks and congratulation! Not sure what that could be. wsdd.service – Web Services Dynamic Discovery host daemon Many thanks for the update and kind comments. Follow me on Twitter, Facebook and YouTube, or buy me a smoothie. mkdir ~/share. the only thing missing is to restart the samba server for the changes to take effect. Main PID: 30179 (python3) Aug 15 16:15:41 devastator wsdd[30179]: logger.warn(‘ignoring address on {}’.format(interface.name)) While there is no connectivity problem and Samba will still run fine, users might want to have their Samba hosts to be listed by Windows automatically. Not concerned about the laptops not being able to see my desktop at this point. I increased my AdSense revenue by 68% using AI . While at it, I also replaced 6 occurences of logger.warn( by logger.warning(to get rid of related warning messages. | Most warnings have also vanished.