similar to: Failed to find [principal](kvno 4) in keytab MEMORY:cifs_srv_keytab (arcfour-hmac-md5)]

Yes, I am planning on upgrading the FreeNAS which will include a newer version of samba. However, I'm quite confident that this is not a duplicate of #12262. To be clear: I'm offering to leave my production system in a degraded state to help myself and the Samba developers understand exactly what's going on here, to determine if this is a new bug, or an existing one. I'm worried

On 27/12/2019 17:06, Jonathon Reinhart wrote: > On Wed, Dec 18, 2019 at 9:52 AM Rowland penny via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > On 18/12/2019 14:34, Jonathon Reinhart wrote: > > On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba > > <samba at lists.samba.org <mailto:samba at

On Wed, Dec 18, 2019 at 9:52 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 18/12/2019 14:34, Jonathon Reinhart wrote: > > On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba > > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > > > Problem is, and as I said, Samba 4.3.x is EOL as far as Samba is >

On 16/12/2019 20:22, Jonathon Reinhart via samba wrote: > Hello everyone, > > I have a FreeNAS server (9.10 running samba 4.3.11-GIT-UNKNOWN) that's recently > started emitting this error: > If you are running Samba 4.3.11 then you should be aware that it is EOL and bug 12262 was fixed in 4.4, so I would suggest you upgrade to a supported Samba version. You will probably find

On 18/12/2019 14:34, Jonathon Reinhart wrote: > On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > Problem is, and as I said, Samba? 4.3.x is EOL as far as Samba is > concerned and if you have found a bug in it, it is very, very > unlikely > to get fixed, unless it is

On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba < samba at lists.samba.org> wrote: > Problem is, and as I said, Samba 4.3.x is EOL as far as Samba is > concerned and if you have found a bug in it, it is very, very unlikely > to get fixed, unless it is still in a later, supported, Samba version. > Of course; I wouldn't expect any more patches for 4.3.x. I've dug

Hi. I'm using Samba 4.3.11 as a domain member on FreeBSD 10.x. Some of my users (around 1%) are experiencing problems from time to time, browsing this server's shares in Windows Explorer - it starts to ask for the password. It doesn't ask the password while accesssing it via it's IP address, and I see in its logs the following (when accessing it via its name): [2016/09/20

After reviewing logs I found that my previous assumption was wrong. Situation: - i'm trying to start live migration from hyper-v host A (BMSRV4-HYPERV) to hyper-v host B (BM-SRV-5) from host B (logged in as user from DOMAIN ADMINS group). Kerberos constrained delegation is set in accordnance to microsoft instructions with proper SPN's set (well, proper as in with the workaround I

Hi, I hit the issue described in this thread https://groups.google.com/forum/#!topic/linux.samba/VfjW9Af92Wg while testing out s4u2self and s4u2proxy in a windows service, so I wanted to share my setup. So I wrote a small windows service that's running as a local system account to impersonate an user via s4u2self (using LsaLogonUser in win32 api than calling ImpersonateLoggedOnUser) and then

Ubuntu 16.04.1 LTS Samba Version 4.3.11-Ubuntu Hi I'm still testing and trying to migrate from a NT4 domain to samba4 AD With the test configuration: AD-DC + domain_member_file_server + Windows_8.1_client all is working well, inclusive server profiles But I have to migrate also some old WindowsXP_SP2 and Windows7 I could join the domain with the WindowsXP. I see it's record with

Hello, This won't be a very helpful reply, but I can confirm I've had the exact same issue. I ran into this a few years ago and could not get HyperV migrations to work with a Samba DC. I even went so far as to install a Windows DC just to prove to myself that it is supposed to work, and it does, perfectly (with ADDC it even creates all the SPNs for you auto-magically). Unfortunately at

Samba - General mailing list wrote >> [2017/01/11 16:42:34.522067, 1] >> ../source3/librpc/crypto/gse.c:496(gse_get_server_auth_token) >> gss_accept_sec_context failed with [ Miscellaneous failure (see text): >> Failed to find cifs/hg004.humgen.0zone at HUMGEN.0ZONE(kvno 1) in keytab >> MEMORY:cifs_srv_keytab (arcfour-hmac-md5)] >> [2017/01/11

On Mon, 16 Jan 2017 09:07:35 -0800 (PST) rawi via samba <samba at lists.samba.org> wrote: > Samba - General mailing list wrote > >> [2017/01/11 16:42:34.522067, 1] > >> ../source3/librpc/crypto/gse.c:496(gse_get_server_auth_token) > >> gss_accept_sec_context failed with [ Miscellaneous failure (see > >> text): Failed to find cifs/hg004.humgen.0zone

hello, today the following problem occurred: [2019/10/08 09: 57: 23.568282, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token) gss_accept_sec_context failed with [Miscellaneous failure (see text): Failed to find cifs/fs-share at dom.corp (kvno 109) in keytab MEMORY: cifs_srv_keytab (arcfour-hmac-md5)] in my smb.conf I have the lines: kerberos method = dedicated keytab

Samba - General mailing list wrote > On Mon, 16 Jan 2017 09:07:35 -0800 (PST) > rawi via samba &lt; > samba at .samba > &gt; wrote: > >> Samba - General mailing list wrote >> >> [2017/01/11 16:42:34.522067, 1] >> >> ../source3/librpc/crypto/gse.c:496(gse_get_server_auth_token) >> >> gss_accept_sec_context failed with [

Rowland, it is not a problem of mount but of kerberso ticket: [2019/10/08 10:58:09.626059, 1] ../../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step) gensec_spnego_server_negTokenInit_step: gse_krb5: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_LOGON_FAILURE [2019/10/08 10:58:09.634532, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token)

Hi Rowland, I refer again after a week, perhaps missing an important piece to the big picture: the error message appears ONLY when you access the share using the netbios alias: [Global] workgroup = WG1 realm = DOM.CORP netbios name = fs-a netbios aliases = oldsamba security = ADS if you access the \\fs-a\sharename is ok if you access \\oldsamba\sharename the logs report the

On 05/11/2019 12:17, banda bassotti via samba wrote: > Luis, ok I'v removed everything, step 1: > > KRB5_KTNAME=FILE:/etc/krb5.keytab2 net ads keytab CREATE -P I have said this once already, but, I will try again ;-) You are creating a keytab, which may or may not be called /etc/krb5.keytab2 > step2: > # KRB5_KTNAME=FILE:/etc/krb5.keytab2 net ads keytab ADD >

Luis, my typos, I'v to mask the output sorry (compliance) # su - testuser $ smbclient --option='client min protocol=NT1' -U testuser //oldsamba/testuser -c 'ls' Unable to initialize messaging context Enter DOM\testuser's password: session setup failed: NT_STATUS_LOGON_FAILURE [2019/11/05 15:50:50.009481, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token)

I made some progress with the issue, but didn't solve it completely It's basically a kind of bug (i'm not sure if it's on kerberos side or samba, I think samba is the culprit here (?). Microsoft uses kind of weird SPN for Hyper-V. Weird as there are "spaces" in the string - which is kind of unique as far as SPN's go, usually SPN form a complete string. So I kind