similar to: samba, sssd, Active Directory, NT_STATUS_NO_LOGON_SERVERS, NT_STATUS_ACCESS_DENIED

> Now go and ask your question on the sssd-users mailing list, this > has nothing to do with Samba. Thank you for the response. Why do you say this has nothing to do with samba? The samba logs indicate the problem is with samba. The sssd logs show everything working except for samba. I changed my smb.conf to default setting and setting that should not be there (as explained in your

> On Apr 23, 2017, at 10:15 PM, Data Control Systems - Mike Elkevizth <mike at datacontrolsystems.com> wrote: > > What exactly are you trying to accomplish? Based on the smb.conf that you posted, it looks like you only want to be able to authenticate using the active directory server (i.e. I don't see any shares). I did not include the share as I didn’t think it was

What exactly are you trying to accomplish? Based on the smb.conf that you posted, it looks like you only want to be able to authenticate using the active directory server (i.e. I don't see any shares). If you are only authenticating to an M$ AD server, sssd is all that you need. Samba doesn't even need to be installed on your machine. I think Rowland's recommendation of asking on

Upgraded from samba 3.6.20 on gentoo to samba 4.1.6 on Ubuntu Trusty. Since the upgrade all attempts to open Microsoft Office files results in the file being opened Read-Only. Found multiple posts from multiple sites dealing with similar problems.

On Fri, 21 Apr 2017 23:44:26 +0000 Bob Tanner via samba <samba at lists.samba.org> wrote: > Environment > ========================================================================== > ubuntu 16.04 > samba 4.3.11+dfsg-0ubuntu0.16.04.6 > sssd 1.13.4-1ubuntu1.2 > Windows Server 2008 R2 > > At site1 the above works. My ubuntu server running samba+sssd can >

Hi, I am trying to implement the *password must change at next logon* in CentOS 6.5 client using sssd 1.11.6 where Samba 4.1.10 is my backend server. Here are the list of things which I have done, 1. I have setup the CentOS to do the Domain login using sssd service. I can able to login into the CentOS client using Domain user's credentials from display and from SSH also, no problem at all.

I am currently looking at migrating my existing CentOS6 servers over to CentOS7 and am currently testing out my sssd configuration on the new build with some issues. For some reason I am unable to see any secondary groups for my user like I would expect, and the /etc/sssd.conf, /etc/nsswitch and related /etc/pam.d configurations should be the same for both my CentOS6 and 7 servers (Configuration

Hi, I am trying to implement the *password must change at next logon* in CentOS 6.5 client using sssd 1.11.6 where Samba 4.1.10 is my backend server. Here are the list of things which I have done, 1. I have setup the CentOS to do the Domain login using sssd service. I can able to login into the CentOS client using Domain user's credentials from display and from SSH also, no problem at all.

Hello, I'm trying to use the cifs proxy vfs module in Samba4. I can join the domain seemingly without problem. When trying to access the proxy server (and hence its share) I get NT_STATUS_NO_LOGON_SERVERS. My setup is as follows: root@proxy# ./setup/provision --realm=<realm> --domain=<domain> --adminpass=<adminpass> \ --server-role='member server'

I have my Samba 3.0.21c Linux Server as Domain member (security=ADS) so that domain users can use the Samba Server as shared file server. Everything works nice if the domain controller is present, e.g. wbinfo -a DOMAIN\\donald%donald plaintext password authentication succeeded challenge/response password authentication succeeded (this just simulates a Windows 2000 Client using the share which

Hi, I've been following the troubleshooting guide, but our situation is a little different, so hopefully someone will be able to help out. :) We've got three machines, a domain controller running samba 3.0.10 (OSX 10.3), a server running Win 2k3 server, and a client running samba 3.0.24 (Ubuntu). The problem we're having is trying to connect to the Win 2k3 server from the samba

I've configured a domain trust between Samba 3.5.6 and Windows 2003 Server Enterprise Edition SP2. It's a one way trust, Windows is the trusted and Samba the trusting. I want to give access to my resources in the Samba domain to the users in the Windows domain. The configuration of the trust was fine (I think). The validation on the window server says that it' s ok and the Windows

In the end I just upgraded all DCs to 4.5 and remote-deleted the broken ones. Seemed to work without a hitch, manual removal was only necessary to remove the IPs from DNS\_msdcs.ourdomain\gc\. I'll try adding new DCs on a date that's not "Friday two hours before I disappear for vacation". On 2017-03-29 16:51, Sven Schwedas via samba wrote: > Situation: Trying to upgrade

Hi, I have a samba4 AD setup with 2 DCs and one samba4 server with fileshares. If both my DCs are offline i can't login to any of the shares on the samba4 fileshare server with smbclient, but wbinfo -K works fine and ntlm_auth also works fine with offline cached credentials. ??san???root???~???smbcontrol winbind offline ???san???root???~???smbcontrol winbind onlinestatus PID 292952:

Hi there I have samba-3.0.27a rolled out over a large number of servers, and every once in a while one of them will start failing to allow people to connect, with winbind reporting NT_STATUS_NO_LOGON_SERVERS, and ntlm_auth failing with "NT_STATUS_NO_LOGON_SERVERS: No logon servers". The same problem occurred with earlier versions too. I think I've tracked down the cause of the

Hi list, Thanks in advanced. I have written a winbindd client software to do NTLM authentication by using WINBINDD_PAM_AUTH_CRAP message. that is to say, my winbindd client is similar to ntlm_auth, but with high performance. when I test it under large traffic, most of the time they all work well. and the transaction per second can reach more than 900. but sometimes, winbindd will return

Every few weeks users are not able to logon anymore until i restart the winbind daemon. The message in winbind.log is NT_STATUS_NO_LOGON_SERVERS. after that PAM (system-auth --> pam_succeed_if.so) is not able to resolve the active directory groups anymore. The quick fix is to create a new situation in our monitoring tool to restart the daemon if this message appears in the log. Is this a known

Hello, We had a strange thing happen today - we shut down our system (virtual machines) so that some work could be done in the server closet and everything was shut down gracefully but when everything was started back up I can no longer access my file server from windows. I get the following message in windows: \\fs1 is not accessible. You might not have permission to use this network

Hello Sven, Am 29.03.2017 um 16:51 schrieb Sven Schwedas via samba: > Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption > too much by adding new DCs and demoting old ones. > > After bringing online the first 4.5 DC, I ran `demote > --remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs > (held no FSMO roles). That seemed to run fine (the DC

> > – I noticed a typo in the server's `netbios name` setting, corrected > it, and restarted the DC Where did you change this, in smb.conf or /etc/hosts ?? By default netbios name is adapted from the hostname. If you changed the hostname you might have found the source of your problem. > > – Noticed I had problems with the LDAP SSL certificates for this node > and