On February 12, 2017 11:07:33 PM PST, Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
I do use cifs when I mount shares.
In my use case, I am making shares on the openSUSE host available to Windows users. They authenticate with their Windows credentials. Both the Windows and the local smbclient fail authentication on the newer Samba host. Which is why I feel the issue is on the Samba host. I choose to show smbclient with the error so we could eliminate the Windows clients. Samba all by itself cannot authenticate.
I suspected that there could be some difference in the newer samba. The joining of the Windows domain and all else was set up by Yast on the new server with the new Samba. When it failed I looked around at the parts I knew about and saw that it had set things up exactly as an older Yast did on the functioning server running an older Samba.
So, is it that Yast has missed something in the new Samba server?
On Fri, Feb 10, 2017 at 6:37 PM, John Andersen <jsamyth@gmail.com> wrote:
Mind the samba versions Roger. Somethings have changed in version 4.
By the way, you don't actually need smbclient to act as a client. Cifs is sufficient. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
What about smbpasswd ? Are these users all in there? Ports all open ? -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org