How do I configure the new Samba 4.11.6

Howdy! Been working on this project off and on for over a year. Last time I tried to set up Samba it was at 3.6 and someone suggested I try Samba 4. Searching configuration guides for Samba 4 seem to not exist. I think I managed to get it installed but it won't share anything as I would suspect over Netbios. On my Windows laptop, I see the name of domain name that I have named my OpenWRT device (espressobin v5) when when I try to open up the share from Windows it tells me I am not authorized. I don't use WORKGROUP on my Windows 7 laptop. I haven't tried it yet on my Windows 10 machines.

The USB drive I can access via WinSCP and I see under /mnt/sda2 some directories I set up previously including /Music and /Movies.

I tried to add a share such as this:

Network Shares
Samba Version 4.11.6

    General Settings
    Edit Template

Interface
    lan: [Ethernet Adapter: "lan0"] [Ethernet Adapter: "lan1"] 

Workgroup			(sort of grayed-out)
Description			Samba on OpenWRT
Force synchronous I/O		blank
Enable macOS compatible shares	blank
Allow legacy (insecure) protocols/authentication.	blank
Allow legacy smb(v1)/Lanman connections, needed for older devices without smb(v2.1/3) support.  box-checked
Disable Netbios			blank




Added to SHARED DIRECTORIES:  (example test line)

Name		Movies
Path 		/mnt/sda2/Movies
Browse-able	checked
Read-only	blank
Force Root	blank	
Allowed users	blank
Allow guests	checked
Guests only	blank
Inherit owner	blank
Create mask	0666
Directory mask	0777
Vfs objects	blank
Apple Time-machine share	blank
Time-machine size in GB		blank

And I get the error message in windows when clicking on my server in the windows network access panel that I am not authorized. Thanks in advance.

Here is what the server log looks like:

Fri Apr  3 22:16:34 2020 user.info wsdd2[1878]: starting.
Fri Apr  3 22:16:35 2020 kern.info kernel: [   20.201031] mv88e6085 d0032004.mdio-mii:01 lan0: Link is Up - 100Mbps/Full - flow control rx/tx
Fri Apr  3 22:16:35 2020 kern.info kernel: [   20.210566] br-lan: port 1(lan0) entered blocking state
Fri Apr  3 22:16:35 2020 kern.info kernel: [   20.216075] br-lan: port 1(lan0) entered forwarding state
Fri Apr  3 22:16:35 2020 daemon.notice netifd: Network device 'lan0' link is up
Fri Apr  3 22:16:35 2020 daemon.notice netifd: bridge 'br-lan' link is up
Fri Apr  3 22:16:35 2020 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Apr  3 22:16:35 2020 kern.info kernel: [   20.226492] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Fri Apr  3 22:16:35 2020 authpriv.info dropbear[1885]: Child connection from 192.168.16.228:57962
Fri Apr  3 22:16:35 2020 authpriv.notice dropbear[1885]: Password auth succeeded for 'root' from 192.168.16.228:57962
Fri Apr  3 22:16:35 2020 daemon.err nmbd[1730]: [2020/04/03 22:16:35.657750,  0] ../../lib/util/become_daemon.c:136(daemon_ready)
Fri Apr  3 22:16:35 2020 daemon.err nmbd[1730]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]: [2020/04/03 22:16:35.951977,  0] ../../lib/util/become_daemon.c:136(daemon_ready)
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]: [2020/04/03 22:16:35.952845,  0] ../../source3/smbd/server.c:1073(smbd_open_one_socket)
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]:   smbd_open_one_socket: open_socket_in: Address not available
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]: [2020/04/03 22:16:35.953269,  0] ../../source3/smbd/server.c:1073(smbd_open_one_socket)
Fri Apr  3 22:16:35 2020 daemon.err smbd[1729]:   smbd_open_one_socket: open_socket_in: Address not available
Fri Apr  3 22:16:36 2020 daemon.err odhcpd[1335]: Failed to send to ff02::1%lan@br-lan (Address not available)
Fri Apr  3 22:16:36 2020 daemon.info samba4-server: Legacy Protocols allowed, don't use this option for secure environments!
Fri Apr  3 23:00:09 2020 authpriv.info dropbear[1979]: Child connection from 192.168.16.228:57965
Fri Apr  3 23:00:17 2020 authpriv.notice dropbear[1979]: Password auth succeeded for 'root' from 192.168.16.228:57965
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]: [2020/04/03 23:00:21.527660,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]:   *****
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]:
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]:   Samba name server SAMBASERVER is now a local master browser for workgroup WORKGROUP on subnet 192.168.16.252
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]:
Fri Apr  3 23:00:21 2020 daemon.err nmbd[1730]:   *****

Strange isn't it the lack of response and the lack of documentation on this. My problem was apparently that my Windows 7 system was hosed. I spent the last couple of days going through everything I could find on the web to resolve the issue I was seeing with the error:

\\NAME-PC is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The specified network provider name is invalid

It's all laid out here for what finally got me going. You may even have to do as I did and go further than all the steps this procedure lays out in order to resolve the issue with the network adapter where you can't access via Samba You may in fact have to do everything in this link AND go ahead and delete the option of "Client for Microsoft Networks", reboot your system and add "Client for Microsoft Networks" back. Additionally after going through all this, all that happened was that I got a completely different error message of which of course I didn't write down but basically I resolved that by disabling the old free AVG anti-virus on my Windows 7 system.

At last I can after tryng for over a year, access my Samba shared on OpenWRT. It is a shade disappointing that I can only obtain a speed of about 9M/sec uploading to the server but at least all my files are not disappearing off the ext4 partition I created using my Windows 7 machine and the best ext4 driver which is also flakey.

Everything is great now. I even added transmission and now the native SMB:xxxxxxx support of Kodi accesses this server and transmission can add new files as I desire. Great setup if you don't mind things a little slow. Kodi doesn't seem to have an issue with buffering or anything from using the SMB share, so I guess all is well that ends well and as far as a file server, this is going to be not anywhere near an acceptable file backup option but it will do in a pinch for an individual use media server.

Here's how to get started with any WIndows 7 access issues (and don't forget remove/re-add the Client for Microsoft and check disablign AVG):

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.