similar to: invalid NTLMSSP_MIC / SPNEGO login failed: NT_STATUS_INVALID_PARAMETER

Hello, since I upgraded my NT4 domain Samba 4.2.11 to 4.2.14 I can no longer authenticate when I access any share. After that I even upgraded to Samba 4.4.5 but still get the same error: [2016/10/15 04:42:19.786198, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [xx] -> [xx] -> [xx] succeeded [2016/10/15 04:42:19.789933, 1]

On 24/10/16 18:03, Boris S. via samba wrote: > > Hello, > > since I upgraded my NT4 domain Samba 4.2.11 to 4.2.14 I can no longer > authenticate > when I access any share. > After that I even upgraded to Samba 4.4.5 but still get the same error: > > > [2016/10/15 04:42:19.786198, 2] > ../source3/auth/auth.c:305(auth_check_ntlm_password) > check_ntlm_password:

Hi List, As the subject states, I'm running a CTDB cluster. Samba is Sernet 4.4.5 in an NT-Style Samba domain (DCs are Centos 6 packaged samba, 3.6.22) Every so often, users are unable to connect to network shares. Most of the problems seem to happen on Windows 7 domain members, but smbclient will also fail to connect. I see these lines in the logs for every attempted connection:

Hello, i have migrate a Samba (3.0.20b-3.19-1616-SUSE) to debian 9 (4.5.16-Debian). On the old suse users are created with smbpasswd -an foo On Windows (10) users have a User account with also empthy passwords. No AD or NT4-Domain (round about 10 Users) Then I try to connect to the share smbclient -NL \\192.xxx.xxx.xxx work. Connect from Windows to share with no password dosed work. Set a

Domain users using Windows 7 systems lose the ability to connect to Samba shares. Some users can connect one day but then lose the ability the next. When the problem starts to occur the log.smbd displays: =============================================== check_ntlm_password: authentication for user [user1] -> [user1] -> [MYDOMAIN\user1] succeeded ntlmssp_server_postauth: invalid

On Thu, 22 Sep 2016 10:58:18 +0100 Alex Crow via samba <samba at lists.samba.org> wrote: > Hi List, > > As the subject states, I'm running a CTDB cluster. Samba is Sernet > 4.4.5 in an NT-Style Samba domain (DCs are Centos 6 packaged samba, > 3.6.22) > > Every so often, users are unable to connect to network shares. Most of > the problems seem to happen on

This sounds very like this bug: >> >> https://bugzilla.samba.org/show_bug.cgi?id=11847 >> >> But it is supposed to be fixed ? >> >> Rowland >> > I have "map to guest = bad user". Sorry, I must have missed pasting > that in. > > However the bug only seems to reference guest share access. This is > happening on normal, restricted

We actrually have the same problem. However, we are running a normal fileserver (also Sernet 4.4.5) no cluster in an NT-Style domain with Centos 5 (Samba 3.6.23) as the DC. IT works OK for some days then just stops. Any idea how to debug? Regards Christian --

On 22/09/16 12:12, Rowland Penny via samba wrote: > On Thu, 22 Sep 2016 10:58:18 +0100 > Alex Crow via samba <samba at lists.samba.org> wrote: > >> Hi List, >> >> As the subject states, I'm running a CTDB cluster. Samba is Sernet >> 4.4.5 in an NT-Style Samba domain (DCs are Centos 6 packaged samba, >> 3.6.22) >> >> Every so often, users

There is bug for this: https://bugzilla.samba.org/show_bug.cgi?id=12303 I am testing this option to resolve this: client ipc signing = No But I am not yet sure if it works. Regards Christian Am Mittwoch, den 16.11.2016, 15:41 -0500 schrieb Sonic via samba: > Domain users using Windows 7 systems lose the ability to connect to > Samba shares. Some users can connect one day but then

On 05.09.19 16:14, Rowland penny via samba wrote: > try adding 'null passwords = yes' to your smb.conf. I have try. but can't connect (NT_STATUS_CONNECTION_RESET). Log append. Config: [global] workgroup = workgroup dns proxy = no log file = /var/log/samba/log.%m max log size = 5000 log level = 3 passdb:5 auth:5 syslog = 0 panic action =

Hello everybody, I am trying to keep my samba pdc working with windows 7 pro clients. After my upgrade: 2016-12-15 15:10:16 upgrade samba:amd64 2:3.6.6-6+deb7u7 2:3.6.6-6+deb7u10 Some of the Windows 7 client can not login anymore and respond with: The trust relationship between this workstation and the primary domain failed Changing the setting client use spnego = no will make the Windows

Ubuntu Server 7.04 Apache/2.2.3 (Ubuntu) PHP/5.2.1 mod_perl/2.0.2 Perl/v5.8.8 mod_auth_ntml_winbind from svn June 5, 2007. samba 3.0.24-2ubuntu1.2 winbind is working, I can log into the machine as an AD domain user. graham@wtldevapp1:~$ sudo ntlm_auth --username=gdunn01 password: NT_STATUS_OK: Success (0x0) from the conf.d/twiki.conf: AuthName "NTLM Authentication" NTLMAuth

I see strange errors when samba client tries to shrink file to 0 bytes. Samba runs on Ubuntu 12.04, client also Ubuntu. Samba sits on top of POSIX file system (FUSE implementation). I can see truncate is called correctly and no error is returned from my implementation. Any ideas? [2014/02/04 12:34:49.806813, 3] smbd/process.c:1467(switch_message) switch message SMBtrans2 (pid 28426) conn

On 8/13/2017 8:40 AM, Rowland Penny via samba wrote: > Nothing really wrong with the [global] portion of your smb.conf (there > are a few lines I would remove) but I do not see a profiles share. I > would expect to see something like this: > > ... snip ... > > What I do see is something that looks like a users home directory > '[testuser]' That's correct.

On 2017-05-24, Duncan Murdoch wrote: [...] > Okay, how about if we weaken the test? [...] > try > > stopifnot(path.expand(paste0("~/", filename)) == > paste0(path.expand("~/"), filename)) > Nope: > ## path.expand shouldn't translate to local encoding PR#17120 > filename <- "\U9b3c.R" > >

I have a samba PDC (using samba 3.0.24). When I try to establish trust with a win2003 domain, I got signing error, see the log below. Trust with NT domain and win2000 domain works. Any help are appreciated. Thanks, Lin [2007/04/04 17:00:13, 5] lib/debug.c:debug_dump_status(391) INFO: Current debug levels: all: True/10 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0

Dear samba users & developers, I was hoping to seek some assistance on a problem I?ve been investigating for a number of weeks now. A brief summary would be that we have a number of Windows servers accessing UNC paths. In turn, these servers intermittently lose their ability to access the UNC paths. When this happens, restarting the application (IIS6 / 7) on the affected windows webserver

Hi, I'm trying to access a share on my work network using smbclient. We have an Windows Active Directory network. My client computer is running Solaris 10 u8. The computer hosting the share says it's running Acopia ARX(3.0.0b1) According to Active Directory (not familiar with this OS, i think it is a NAS) I run this command to get the Kerberos ticket. bash-3.00$ kinit jtmb at

I have a Samba DC connected to two Windows 2008 R2 DC's. On the Samba machine, if I run `ldbsearch -H ldaps://*SAMBA-DC-IP* -U administrator` It asks for my password and then works great. I can use any domain user and this works. However, if I instead run: `ldbsearch -H ldaps://10.120.160.12 -k1 --krb5-ccache=/tmp/krb5cc_0` I get this: Failed to bind - LDAP client internal error: