similar to: NT_STATUS_ACCESS_DENIED when issuing smbclient -k

Hi Rowland, Can we at least make it work in a new server, i need to virtualize this first before i moved to Samba AD domain, this conf came from the debian wheezy which has a samba 3.6.6 i'm trying to replicate the OLD server exactly as much as possible because i might break something. I tried to changed the security = ads and kerberos method = secrets and keytab but still could not work when

On 24/02/2020 14:56, Marlon Franco via samba wrote: > Hi, > > I migrated our OLD system to a NEW Debian 10 > I can verify that ldap and kerberos are working but i am having issue with samba which is also configured for kerberos > > NEW - Debian Buster with samba 4.9.5 > OLD - Debian Wheezy with Samba 3.6.6 > > root at sample:~# kinit abcd > Password for abcd at

Hi Rowland, I tried to set that option but still same result. I recreated the setup in old debian wheezy 7.11 and it's working. set the log level = 10 'abcd' is the user account then i noticed this in /var/log/samba/log.10.0.2.15 = the ip of the samba server, i am issuing the smbclient in the samba server itself. Unix User found. Rid marked as special and sid (S-1-22-1-12658) saved

Hello, I am trying to upgrade our domain controller to 4.2.0 from 4.1.16, however samba will not start after the upgrade. It appears to be related to the fact that this AD domain was created by running classicupgrade. My test environment, which was originally provisioned from 4.0 does not have this problem. This server was originally deployed back in 2004 using Samba3 and OpenLDAP. We upgraded

Hello, I apologize in advance for cross-posting (and posting for help) to samba-technical, but I've been seeking help on the samba list and bugzilla since last week and have had no replies. Using Google, I've found this issue referenced only once on the mailing list and once in a bugzilla bug (10991). Unfortunately, I've found no resolutions. The problem appears to be specific to

Hi 2 node drbd cluster with ocfs2. both nodes: openSUSE 4.1.9 with drbd 8.4 and ctdbd 2.3 All seems OK with ctdb: n1: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK (THIS NODE) pnn:1 192.168.0.11 OK Generation:1187222392 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:0 n2: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK pnn:1 192.168.0.11

Hi All, I'm struggling since weeks to get samba winbind and a kerberized nfs mount running. We have a Netapp SAN exporting the nfs share with sec=krb5 and a Linux Client Ubuntu 10.04 Server trying to access the exported share. Accessing the share without krb5 (sec=sys) works fine. The linux machine is joined to an Windows 2008R2 domain and user/group lookups login via ssh etc. work fine. I

Red Hat Enterprise Linux Server release 6.5 (Santiago) selinux is disabled. The following commands were all run on the RedHat Server on which I am running samba. *The following ports are open* 5 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:137 6 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:138 7 ACCEPT tcp --

2015-03-27 14:00 GMT-04:00 <samba-request at lists.samba.org>: > Send samba mailing list submissions to > samba at lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.samba.org/mailman/listinfo/samba > or, via email, send a message with subject or body 'help' to > samba-request at lists.samba.org

Hi All, I have machine M1 hosting Samba PDC. It stores only user information. I have machine M2 acting as KDC server. I have machine M3 hosting CIFS shares and it joins into the domain hosted by PDC M1. I have machine M4 used as CIFS client. On M2, I have added users and cifs/host service principals for M3. Also added service principal in keytab file. I have added all the user and service

Hi; ? I would like to use a samba configuration with : ? dedicated keytab file = /etc/krb5.keytab kerberos method = system keytab security = ADS ? But when I test the configuration (testparm) I have the following error msg : ? Load smb config files from /etc/samba/smb.conf Unknown parameter encountered: "dedicated keytab file" Ignoring unknown parameter "dedicated keytab file"

On Mon, 26 Feb 2018 12:27:56 +0200 Arcadie Cracan <arcadiec at gmail.com> wrote: > Dear Rowland, > > I have commented out the 'idmap config' options, nothing changed. > Here are my bind9 configs: > > /etc/bind/named.conf: Nothing wrong there > > /etc/bind/named.conf.options: > options { > directory "/var/cache/bind"; >

Hello, Can anyone offer assistance with this issue? Can someone help me understand what winbindd is looking for here? Thank you. /usr/local/samba/sbin/winbindd: winbindd version 4.2.0 started. /usr/local/samba/sbin/winbindd: Copyright Andrew Tridgell and the Samba Team 1992-2014 /usr/local/samba/sbin/winbindd: Maximum core file size limits now 16777216(soft) -1(hard)

Try verifying kvno from the client that gives the error message. That kvno = 2 for dc$ must've come from somewhere. You can also double check e.g. via ADUC ldap attributes of the dc$: lastpwdset and kvno. If  kvno is definately 1 that means that client connecting has some error, if it's 2, than it means that dc has outdated keytab. And if it's the former, than I really am not sure

Hi, We have a Samba AD domain with an Ubuntu 16 box as the AD DC . We then promoted a Windows 2008R2 box as a DC. The DNS zone/data in the Samba AD gets replicated to the Windows DC. However, when we try to add a host entry in Windows DNS, we get the message The host record abcd.LIN.GROUP cannot be created. Refused. When we try to create the same in the Samba AD box, it works. The DNS backend

what is the output of "kvno dc.domain.net.pl"? There seems to be mismatch kvno of the secrets keytab, and what is client expecting (kvno 2). Kvno increments by 1 for every password change. Was there by any chance password change for the dc$ account and keytab was not recreated? If You made some upgrades, maybe during process You for example rejoined the domain (that would set new

Hi! I have a samba4 domain with two r/w directory controllers. DNS is set up so that domain.com name adresses both servers for redundancy. But workstaions can't contact second server with address \\domain.com becuse the kvno is different that first servers kvno and when using \\domain.com address the kvno seems to be always first servers kvno. Can I somehow increase the second servers kvno

Hai Tom, Im not in 4.2 yet, but maybe i can help analize your problem. ( as long its possible, big power outage in the netherlands.. ) this : https://lists.samba.org/archive/samba/2014-September/185031.html is a good example how not to setup your samba server. so before we can think with, please post (and sorry if its again) some info. Your OS? Compiles samba or os provided samba, or

> -----Ursprüngliche Nachricht----- > Von: Rowland penny [mailto:rpenny at samba.org] > Gesendet: Sonntag, 5. Juni 2016 17:46 > An: Jo <j.o.l at live.com> > Cc: 'samba' <samba at lists.samba.org> > Betreff: Re: AW: [Samba] inconsistent DNS information, windows domain > member issues.. > > On 05/06/16 13:43, Jo wrote: > >> Your DCs really

I just installed samba on a new server, 3.4.5-42, 64 bit version from Sernet, over CentOS 5.4. When running testparm, I get the following warning: rlimit_max: rlimit_max (8192) below minimum Windows limit (16384) I searched Google for some answer but I couldn't find a satisfactory one. What should I do to solve this? Can someone from the Samba team enlighten me on this? Thank you!