In my settings, CPU also throttles at ~100%, but with transfer speeds betwen 350 and 400 Mbps, I think thatâs expected The test was done by downloading from btrfs-formatted USB3 RAID drive connected to Omnia.
Does anybody have a tip for interesting non-default settings available with samba 4? I read about SMB direct, but havenât figured out how do I enable it (if itâs not by default). Offloading some CPU work would probably allow for even higher speeds.
It is not a crucial element, but the naming services does not work without it. I donât know the terminology, but you wonât see anything when you click on âNetworkâ in the Windows file explorer.
I have bad luck.
My Turris 1.0 + Samba4 + wdds2 does not work.
I have a PC with Win7 Enterprise and notebook with Win 10 Home, only works by IP address.
Restart the router and PC, did not help. Workgroup is DOMA.
net use r: \\turris\nas\tftp\images - error 53 net use r: \\10.0.0.1\nas\tftp\images - no problem, all fine, folder available
root@turris:~# ps | grep smbd
8661 root 31112 S /usr/sbin/smbd -F
8801 root 28608 S {smbd-notifyd} /usr/sbin/smbd -F
8802 root 28608 S {cleanupd} /usr/sbin/smbd -F
8823 root 31104 S {lpqd} /usr/sbin/smbd -F
19288 root 31228 S /usr/sbin/smbd -F
Hi, @commar, I just want to tell you that I had same problem adding samba3+ disk via ânet useâ while NetBIOS was enabled, Window7 is weird and buggy, but I was able to add it via DDNS name. Just mine observationâŠ
According to the description we it seems, that you have a poorly set up DNS. Launch a ping from the PC. Once with the IP address of the samba, and once with the DNS name. Ping should be working.
If does not work samba with DNS name, you need to set the DHCP.
(EDIT: no true! "and through foris/DNS/âRegister DHCP clients in DNSâ).