similar to: Ubuntu 18.04, bound to Windows AD, sssd auth, Samba 4.7.6: Can't get no share satisfaction

Keep you naming conventions as they should. wrong netbios name = cns-bio-krak1 right netbios name = CNS-BIO-KRAK1 If you resolving setup is correct. Then you can use : disable netbios = yes and dns proxy = yes Then your netbios name should be resolved over dns. But you still need to set it as shown above. > Still need to find out if there is a > way to allow a few non-domain

So, we have Samba file sharing working on CentOS 7.6 with sssd: [root at cns-srv-lnode2 samba]# cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [root at cns-srv-lnode2 samba]# smbd --version Version 4.8.3 Some smb.conf configuration details: - security = user - an idmap entry is unnecessary - disable netbios = yes works fine - pretty sure nmbd is unnecessary

I thought I sent this, but didn't see it hit the list. Since this presented a considerable amount of frustration (requiring a netbios name seems illogical in an AD-only world), I'm sending it again. Apologies if this is a repost. -------- Forwarded Message -------- Subject: Samba + SSSD: confirmed working for Samba versions 4.7.6 and 4,8.3 Date: Tue, 18 Jun 2019 17:15:47 -0500 From:

On 6/13/19 10:48 AM, Alexey A Nikitin via samba wrote: > According to the MS docs SID=('S-'+version+identifier authority value+domain or computer identifier+RID). The SIDs that don't contain RID are the special cases of Machine SID, Domain SID, Service SID, and some predefined universal well-known SIDs [1]. According to the common use in MS tools SID encompasses RID. And even in

I have a new CentOS 7 installation which I joined to my domain using 'realm join mydomain.com'. That worked great. I can get a ticket with 'kinit administrator at mydomain.com'. But my samba shares don't work. In fact, when I browse (from windows 7 domain member) to the host (lserver), it just times out. Similarly, when I try from another Linux server: smbclient

No takers thus far. These are the Samba 4.2 changes to which I previously referred (https://www.samba.org/samba/history/samba-4.2.0.html) : For the client side we have the following new options: "require strong key" (yes by default), "reject md5 servers" (no by default). E.g. for Samba 3.0.37 you need "require strong key = no" and for NT4 DCs

On 13/06/2019 17:17, Goetz, Patrick G via samba wrote: > On 6/13/19 10:48 AM, Alexey A Nikitin via samba wrote: >> According to the MS docs SID=('S-'+version+identifier authority value+domain or computer identifier+RID). The SIDs that don't contain RID are the special cases of Machine SID, Domain SID, Service SID, and some predefined universal well-known SIDs [1]. According to

You may have included this in another email however I will ask anyway, did you set DNS to your server in the Linux and Windows clients? Can you check if a Windows Server can join? Can you use DNS management to check the DNS on you samba server? On Mar 28, 2016 2:15 PM, "Dale Schroeder" <dale at briannassaladdressing.com> wrote: > No takers thus far. These are the Samba 4.2

On Thursday, 13 June 2019 09:18:25 PDT Goetz, Patrick G via samba wrote: > On 6/13/19 10:48 AM, Alexey A Nikitin via samba wrote: > > According to the MS docs SID=('S-'+version+identifier authority value+domain or computer identifier+RID). The SIDs that don't contain RID are the special cases of Machine SID, Domain SID, Service SID, and some predefined universal well-known

I have an NT domain on Debian Stretch. It's been upgraded numerous times, but has been running for almost a decade. Since upgrading from 4.1.17 to 4.3.3 (huge Debian jump), then to 4.3.6, clients cannot connect to shares. Prior to upgrading, I found the changes mentioned for 4.2 regarding NT domains and applied them. Even so, I still cannot connect to network shares nor print to

Hi all! I've bumped into an issue which Dovecot which has me a bit stumped; All of a sudden (ie. no obvious changes made to the config as far as I know) Dovecot seems to never stop 'imap-login' processes. This continues to the point where it will hit the 'process_limit'. For a 50-ish user install the limit was set to 100 but I increased it to 512. The only thing this changes

Hi all, I was trying to plot a graph using the following data: method percent accuracy group A1 4 0.8529 cns A1 10 0.8412 cns A1 15 0.8235 cns A2 4 0.9353 cns A2 10 0.9412 cns A2 15 0.9471 cns A1 4 0.8323 col A1 10 0.8452 col A1 15 0.8484 col A2 4 0.8839 col A2 10 0.8677 col A2 15 0.8678 col ################# The code I'm using to generate the graphs is: ### code :

Hi everybody, this is a real dummy thing. I sorted a matrix based on a given column, and what I get is right, until it comes to columns of negative and positive values; than, "order" orders everything from max to min in the negative values, and then AGAIN from max to min in the positive values!!! Why isn't everything order from max to min, and that's it? Thank you!!! Attached

Hi, I've lost my mind on it... I have to scatterplot two vectors, grouped by a third variable, with two different dimensions according to whether each cell line in the plot is sensitive or resistant to a given drug, and with a different color for each of 9 tissues of origin. Here's what I've done:

I've just installed a new DEC Unix 4.0d machine and downloaded the binary version of samba 1.9.18p8 for DEC Unix. I am able to get it up and running, but I am having problems with passwords. I am being prompted for a password when I try to connect to a non-public share, and when I type in my password it is being rejected. I did set security=share in my smb.conf file. I also tried the

I must be missing something- Are these Windows clients?  Or are these Linux clients authenticating against Samba ? if they were linux clients then yes I could see sssd or other authentication components besides winbind coming into play. And in that case yes you would have sssd work with winbind to enable caching of credentials. Is the event log entry below from the server ?   Is it from

Hi All, Yesterday I began experimenting with using LDA to do delivery. To begin with I'm using a .forward file entry for myself so as to avoid affecting other users. When "deliver" is passed an item to deliver, the following is logged: > deliver(allen): Sep 18 19:28:52 Info: Namespace: type=private, > prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes

Hello All, Please consider the following: TotEmp<-c(19,6,1,1,8,44,2,33,48,1) ClusterType<-c("AGF","CNS","OSV","RTL","RTL","TRN","REL","ACC_CLUST","RTL","WHL") Taz<-c(0,0,0,100,100,100,101,101,102,103)

Hi All, I'm attempting to set up print-sharing on a Samba 2.2.7 running on Redhat 7.3. Both 98 and 2000 clients can print fine and dandy if I install the drivers I downloaded from HP (I'm using a LaserJet 5MP for reference). What I want to do is install the drivers to the Linux box so future clients can download the drivers painlessly. I believe I've followed the instructions in

Hi Again, I figured out what my problem was with the encrypted passwords - it's sufficient to say that it was an error on my part, not the software. Oops. However, now I'm completely baffled. I can login to the domain perfectly (encryption is on, by the way), my home drive maps correctly, the login script runs as it is supposed to, but I'm getting an error about my remote