similar to: Samba shares no longer visible

Rowland, Thanks for getting back with me. Fortunately, I was able to fix the problem. I started noticing bits in some of the messages coming off Samba that it wasn't in a domain, or at least I didn't think so. It looks like another admin may have removed domain info from smb.conf. Putting that in got the server working again. -- Jason Lewis Senior Systems Engineer @ Micro

On Mon, 14 Jan 2019 20:11:15 +0000 "Jason W. Lewis via samba" <samba at lists.samba.org> wrote: > All, > I came into work to find a strange problem today: The shares on a > Samba server were no longer accessible. After working on it for a > while, I finally turned up logging and found the following in the > client connection logs: > > [2019/01/14

Hi Team, Issue :- I am not able to access samba share on windows client machine with domain name but able to access with IP Further Details:- We had 2 old samba 3.6.6 setup on hp-ux 11iv3, configured as Active Directory member server, We upgraded both hp-ux samba to 4.9.0 version. For a week both setup works fine, In which we were able to access share of both hp-ux machines by domain name from

Hello everyone since now a certain time I pull my hair and do not understand the source of my problem. after a samba 3 pdc migration to samba 4.8.5 AD, when a windows client starts the gpo computer is not applied to the boot. in the windows logs there are 1058 GPO errors and server side samba here are the logs: GSS server Update (krb5) (1) Update failed: Miscellaneous failure (see text): Failed

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)

Bonjour à tous depuis maintenant un certain temps je tire mes cheveux et ne comprends pas la source de mon problème. après une migration de samba 3 pdc vers samba 4.8.5 AD, au démarrage d’un client Windows, l’ordinateur gpo n’est pas appliqué au démarrage. Dans les journaux Windows, il y a 1058 erreurs d'objet de stratégie de groupe et samba côté serveur. Voici les journaux: Mise à jour du

what do I miss here: wbinfo -u / -g -/ -pPt works [2019/09/05 17:15:25.963590, 1] ../source3/librpc/crypto/gse.c:658(gse_get_server_auth_token) gss_accept_sec_context failed with [ Miscellaneous failure (see text): Failed to find cifs/SAMBA.noras.intra at NORAS.INTRA(kvno 54) in keytab MEMORY:cifs_srv_keytab (aes256-cts-hmac-sha1-96)] [2019/09/05 17:15:25.963681, 1]

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)

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)

Hai, Did you set in the GPO (computer policy) Under System\Logon, "Always wait for the network at computer startup and logon" = Enabled" If its a script, also add these. "Configure Network Options preference extension policy processing" is "Enabled" "Configure Logon Script Delay" = Enabled and set to 0 And, after setting the GPO, reboot 2 x !

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

THANK YOU FOR YOUR REPLY THE RESULT : KVNO Principal ---- -------------------------------------------------------------------------- 1 HOST/samba4 at FSS.LAN (des-cbc-crc) 1 HOST/samba4.fss.lan at FSS.LAN (des-cbc-crc) 1 SAMBA4$@FSS.LAN (des-cbc-crc) 1 HOST/samba4 at FSS.LAN (des-cbc-md5) 1 HOST/samba4.fss.lan at FSS.LAN (des-cbc-md5) 1 SAMBA4$@FSS.LAN (des-cbc-md5) 1

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, 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

Sorry for the translation. actually my first installation is a samba put into production, to avoid errors, I cloned on a new VM not to break my current system. on this one I redid an installation with DEB packages "https://dev.tranquil.it" I then made a restoration. I presice that the supply is a samba3 pdc migration to samba4 dc "samba-tool domain samba3upgrade". I only have

Hi @ll ! I am trying to set up a samba fileserver in SuSe 42.3 as domain member in a debian based Samba4 AD. The join seems to be ok, as I can get /wbinfo -u/ and /-g/, and /getent group/ and /passwd/. I can also list all browsable shares with /smbclient -L \\SambaFS -Uusername/, but when i add -k, I get following errors : /SPNEGO(gse_krb5) creating NEG_TOKEN_INIT for cifs/Samba1 failed

additional note: # kinit sgw Password for sgw at customer.INTRA: # smbclient \\\\u1customer\\IT -U sgw -k SPNEGO(gse_krb5) creating NEG_TOKEN_INIT for cifs/u1customer failed (next[(null)]): NT_STATUS_INVALID_PARAMETER SPNEGO: Could not find a suitable mechtype in NEG_TOKEN_INIT session setup failed: NT_STATUS_INVALID_PARAMETER (krb5.conf already reduced to minimum, btw) Does that point to

Hello, I needed to replace an old Samba AD PDC with a new one, so I've installed the new one (Ubuntu 20.04 + Samba 4.15.13 from Ubuntu repository), joined it to the AD domain, demoted the primary, then removed it. All steps have been done following the Samba official howtos: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory and

On Tue, 26 Feb 2019 15:57:03 +0100 David Jehin via samba <samba at lists.samba.org> wrote: > Hello everyone > since now a certain time I pull my hair and do not understand the > source of my problem. > after a samba 3 pdc migration to samba 4.8.5 AD, when a windows client > starts the gpo computer is not applied to the boot. > in the windows logs there are 1058 GPO errors

On Tue, 2019-02-26 at 15:57 +0100, David Jehin via samba wrote: > Hello everyone > since now a certain time I pull my hair and do not understand the > source of > my problem. > after a samba 3 pdc migration to samba 4.8.5 AD, when a windows > client > starts the gpo computer is not applied to the boot. > in the windows logs there are 1058 GPO errors and server side samba