similar to: migrated from gentoo to debian, DM throws errors ...

Am 05.09.19 um 17:37 schrieb Stefan G. Weichinger via samba: > Am 05.09.19 um 17:19 schrieb Stefan G. Weichinger via samba: >> >> what do I miss here: > > update: maybe the reboot of the clients helped ... looks better now > > > Access works, but I still get [2019/09/05 17:49:41.888422, 1] ../source3/librpc/crypto/gse.c:658(gse_get_server_auth_token)

On 05/09/2019 16:50, Stefan G. Weichinger via samba wrote: > Am 05.09.19 um 17:37 schrieb Stefan G. Weichinger via samba: >> Am 05.09.19 um 17:19 schrieb Stefan G. Weichinger via samba: >>> what do I miss here: >> update: maybe the reboot of the clients helped ... looks better now >> >> >> > Access works, but I still get > > [2019/09/05

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

Overall domain architecture hasn't changed since my spring cleanup post earlier (I did sort out the krb5 packages and logging settings, though). To start the migration, I figured I'd first update the file servers, since they're the least critical component. Upgrade 4.5 ? 4.8, 4.8 ? 4.9, 4.9 ? 4.10 seemed to work fine each step. However, SMB logins either with smbclient or with

Hello, I am using Samba as file server as member of a windows domain. Kerberos is configured with kerberos method = secrets and keytab Currently some (not all) users get issues when connecting to samba shares from windows. In the corresponding samba logs I found entries: .... [2020/07/23 12:08:06.697678, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token)

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

Ok, Your keytab looks ok now. oldsamba.dom.corp is an alias for fs-a.oldsamba.dom.corp. fs-a.dom.corp has address 10.0.0.2 i would have expected here. oldsamba.dom.corp is an alias for fs-a.dom.corp. fs-a.dom.corp has address 10.0.0.2 Or was that a typo? I assuming a typo.. About your setup from the script outpout. Change this one. /etc/hosts 10.0.0.2 fs-a.dom.corp fs-a oldsamba #

On 23/07/2020 11:28, Georg.Biberger--- via samba wrote: > Hello, > > I am using Samba as file server as member of a windows domain. > Kerberos is configured with kerberos method = secrets and keytab > > Currently some (not all) users get issues when connecting to samba shares from windows. > In the corresponding samba logs I found entries: > .... > [2020/07/23

Am 05.09.19 um 18:37 schrieb Rowland penny via samba: > That what you mean ? ;-) ;-) > You will probably have a keytab now '/etc/krb.keytab', the join should > have recreated it. /etc/krb5.keytab > I take it that you are mounting the users homedirs and require the > 'cifs' keytab to do this, I also take it that the computers short > hostname is

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)

Try net ads keytab add_update_ads cifs/$(hostname -f) -U Administrator And i hope this is not your hostname : lpeda1.muc Because thats a domainname. Also make sure you check the resolving of the A and PTR records Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Georg.Biberger--- via samba > Verzonden:

samba-tool computer remove oldsamba Il giorno mar 5 nov 2019 alle ore 17:04 L.P.H. van Belle <belle at bazuin.nl> ha scritto: > Hai, > > Well that great you found it. > > Ah.. so you removed the entry from the DNS or ADDB? > Can you tell what you exactly did, that might help the next person with a > problem like this. > > And not many list messages today.. ;-)

Sven... What did you do. .. I thought, this was all done/fixed. ;-) > Failed to find > cifs/graz-file.ad.tao.at at AD.TAO.AT(kvno 100) in keytab > MEMORY:cifs_srv_keytab (arcfour-hmac-md5)] You need to add the cifs/spn also to the AD and the keytab. https://wiki.samba.org/index.php/Generating_Keytabs Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Hi guys! I started to have the problem above last October, 2th. I don´t know why and how, because it was saturday. So, my file server stoped to authenticate against the Samba4 AD. Today, all shares was stopped and then i restarted my Samba4 AD and the file server. All became to work again. But it im afraid because the problem started by itself. Thanks! # MY CRONTAB 17 * * * * root cd /

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

Hi guys! I started to have the problem above last October, 2th. I don´t know why and how, because it was saturday. So, my file server stoped to authenticate against the Samba4 AD. Today, all shares was stopped and then i restarted my Samba4 AD and the file server. All became to work again. But it im afraid because the problem started by itself. Thanks! # MY CRONTAB 17 * * * * root cd /

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

Le 27/07/2015 17:02, Rowland Penny a écrit : > On 27/07/15 15:51, zorg wrote: >> Le 27/07/2015 16:16, Rowland Penny a écrit : >>> On 27/07/15 15:13, zorg wrote: >>>> HI, >>>> >>>> I'm using debian jessie >>>> I have followed this instruction >>>> >>>>

Le 27/07/2015 16:16, Rowland Penny a écrit : > On 27/07/15 15:13, zorg wrote: >> HI, >> >> I'm using debian jessie >> I have followed this instruction >> >> https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server >> >> Here is : >> >> [global] >> workgroup = DOM >> realm = DOM.LOCAL >> server