stephdl
(Stéphane de Labrusse)
November 16, 2016, 6:40am
1
Hi
I cannot connect to a shared folder in NS7.2 with Nethserver-dc installed…A new VM without tricks
used client Fedora23 with gnome and nautilus
I create a user, I set a password
I create a group
I create a shared folder, I set the group, I allow the read and write permissions
I browse the network in nautilus, I found the domain
I connect to the shared folder, I set the login/password/domain
and it is endless, the password popup comes.
What I did wrong ?
Moreover I don’t have logs, all interesting things are empty
[ root@NS7DEV ~]# ll /var/log/samba/
total 80
drwx------ 4 root root 28 Nov 14 23:11 cores
-rw-r–r-- 1 root root 0 Nov 14 23:11 log.
-rw-r–r-- 1 root root 0 Nov 14 23:12 log.192.168.12.25
-rw-r–r-- 1 root root 0 Nov 15 20:18 log.192.168.12.40
-rw-r–r-- 1 root root 0 Nov 15 20:18 log.helene-pc
-rw-r–r-- 1 root root 0 Nov 14 23:12 log.leo
-rw-r–r-- 1 root root 8952 Nov 16 07:21 log.nmbd
-rw-r–r-- 1 root root 1566 Nov 16 07:34 log.smbd
-rw-r–r-- 1 root root 60983 Nov 16 07:19 log.smbd.old
drwx------. 2 root root 6 Jul 26 12:37 old
davidep
(Davide Principi)
November 16, 2016, 8:45am
2
A similar issue has been already reported here and a workaround is available, please check if it applies to your setup!
NethServer Version: NS7rc1
Module: fileserver
Hi all,
me and samba/shared folders, we can’t get along very well…
I had stuff working:
NS7rc1, Samba AD, fileserver.
I manually added NFS, partially serving the same folders as samba.
Then I changed some stuff on my webserver:
Let’s encrypt certificate, for which I added some info in “organization contacts”,
blocked SSLv3 on the main apache-server, changed some cipher-stuff (wrote in this topic).
Rebooted.
And then, samba stopped accepti…
stephdl
(Stéphane de Labrusse)
November 18, 2016, 6:42am
3
confirmed @davidep after this tricks
alternatives --set libwbclient.so.0.12-64 /usr/lib64/samba/wbclient/libwbclient.so.0.12
systemctl restart smb
I can reach the ibay (and write inside) and see the home share of the domain user.
Sure that you are not responsible of bugs and incompatibilities that window can create on its own, but it must work simply
Even a button radio must be really really really clear. A new user tests a product on a short period and the installer and his first tests can decide if he will adopt the new toy. I’m sure that the test to share some contents on the network is the first stuff he will do…with some difficulties it seems :’(
2 Likes
davidep
(Davide Principi)
November 18, 2016, 8:11am
4
I agree and we are going towards that direction! Let’s continue our discussion here:
There are a few feature requests that could lead us to resume the “Windows network” page in server manager
The new page (I’d like “Windows file server” as title) should contain:
“Workgroup name” field, modifiable only with LDAP providers, read-only if joined to AD.
A radio button to switch between legacy NTLM-auth access and domain Kerberos-auth. See this bug .
A checkbox to enable the home$ share , that enables the domain administrator to access users’ home directories.
As requ…