similar to: Can Logon & Join NT4-style Domain, Can't Change Password

Hallo All, After updating Windows 10 to the latest versions i can confirm Windows 10 is also unable to change passwords. I found this information: https://support.microsoft.com/en-us/kb/3167679 ---- Known issues in this security update This security update disables the ability of the Negotiate process to fall back to NTLM when Kerberos authentication fails for password change operations.

Il giorno 17/ago/2016, alle ore 21:30, Bill Baird via samba <samba at lists.samba.org> ha scritto: > Uninstalling MS16-101 fixed our issue. > > https://technet.microsoft.com/library/security/MS16-101 > > I ran "wusa /uninstall /kb:3167679", rebooting, and now we are back to > normal. Hi, After removing and masking on 19 sep 2016 the KB3167679 the same problem

Same here. Uninstalled the updates, rebooted the workstation, still cannot change the passwords. On Tue, Sep 27, 2016 at 6:44 AM, Paul Tietjens via samba < samba at lists.samba.org> wrote: > On Sun, Sep 18, 2016 at 6:40 PM, Daniele Palumbo via samba < > samba at lists.samba.org> wrote: > > > Il giorno 17/ago/2016, alle ore 21:30, Bill Baird via samba < > >

Hi All, Our users started having issues late last week when trying to change their passwords. They receive the following message: "The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you." Client computers are running Windows 7 Ultimate & Enterprise x64. We are still running (I know, I know) and NT4-style

The following article by Microsoft was updated on 2016-10-14: https://support.microsoft.com/en-us/kb/3167679 It acknowledges the problem and proposes to set a registry key to enable NTLM authentification. Fot the details see paragraph "Known issue 7" in the article linked above. - Under "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa" - Create the key

Hello: Platform: CentOS 6.7 x86-64 $ rpm -qa | grep samba samba-common-3.6.23-30.el6_7.x86_64 samba4-libs-4.2.10-6.el6_7.x86_64 ie-samba-utils-3.6.13-7.x86_64 samba-winbind-3.6.23-30.el6_7.x86_64 samba-client-3.6.23-30.el6_7.x86_64 samba-winbind-clients-3.6.23-30.el6_7.i686 samba-winbind-clients-3.6.23-30.el6_7.x86_64 Problems began after requiring SMB signing (I forgot the specifics but it was

Hi All, I am running Samba 3.6 in PDC mode (i know, i know...AD upgrade is in the works). The most recent update for CentOS 6 (samba-3.6.23-30.el6_7.x86_64) appears to have caused issues and I was forced to downgrade back to samba-3.6.23-25.el6_7.x86_64. When 3.6.23-30 is installed, users running Windows 7 x64 receive the following error when trying access shares: "The trust relationship

A couple of other issues to keep in mind... Aside from the fact that the errors suggest your W10 box is trying to join an AD domain, W10 also defaults to a protocol of SMB 3.3 which Samba 3.x does not support. If you resolve the issue wherein W10 thinks it is joining an AD domain, there's a strong possibility (if not certainty) you will then see errors in the log of the W10 box indicating

On Sun, Sep 18, 2016 at 6:40 PM, Daniele Palumbo via samba < samba at lists.samba.org> wrote: > Il giorno 17/ago/2016, alle ore 21:30, Bill Baird via samba < > samba at lists.samba.org> ha scritto: > > Uninstalling MS16-101 fixed our issue. > > > > https://technet.microsoft.com/library/security/MS16-101 > > > > I ran "wusa /uninstall

Hi, I resolved NMBD errors, but still same error in windows 10 pro, Could please suggest any changes in windows 10 PC. Applied registry changes suggested by samba wiki but no improvement. I am able to join windows 7 clients without error. Regards, Ram On Mon, May 16, 2016 at 8:11 PM, Ram Prasad Bikkina <parvathiprasadb at gmail.com> wrote: > Hi Gaiseric, > > Thank you for

Uninstalling MS16-101 fixed our issue. https://technet.microsoft.com/library/security/MS16-101 I ran "wusa /uninstall /kb:3167679", rebooting, and now we are back to normal. On Wed, Aug 17, 2016 at 1:43 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > Hi All, > > Our users started having issues late last week when trying to change their > passwords. They

hi everybody I have a win10 which is (from what I see) a good member of samba domain except for one thing - it does not seem to a few simply things from a logon.bat, or does not do anything with it. would you share your thoughts? many thanks L.

hi all I have two different Samba versions as PDC and BDC and depending on which one is "domain master" users which are domain admins are not recognized as such. Everything seems normal with 3.6.23-25.el6_7 as "domain master" but when I configure them so 4.2.10 is the master then I login to Win7 fine but Windows tells me that the user is not an Admin and I need to supply

Hello, I run a CentOS 6 machine with samba, serving approx. 150 Windows users with samba running as an NT-like PDC. After today's samba update (samba-3.6.23-30.el6_7.x86_64 etc.), nobody can log in. They all get the "Trust relationship failed" error message. If I downgrade: yum downgrade samba-common samba-winbind samba-winbind-clients samba-client samba samba-doc

A new Debian(unstable) machine with Samba 4.5.2 is trying to join an NT4-style Samba domain hosted on a Debian(wheezy) Server with 3.6.6 which can't be changed but has been working for some years now with a couple of windows clients. Joining the domain was quite easy (only surprise was "client ipc signing"), and "wbinfo -u" gives me a list with all domain users. BUT

On a server Centos 7 with samba-4.2.3-11.el7_2.x86_64, joined to a server samba-3.6.23-24.el6_7.x86_64 PDC on Centos 6.7 up to date, after 7 days I want restart winbind service because the users are not autenticate anymore. This is the error into log file: > Feb  4 10:15:26 s-graph smbd[28960]: [2016/02/04 10:15:26.529467,  0] > ../auth/ntlmssp/ntlmssp_sign.c:236(ntlmssp_check_packet) >

All, We were running samba4-4.0.0-68.el6_7.rc4.x86_64 on our CentOS 6 box serving printers and joined to our domain. No issues whatsoever and quite happy. We upgraded to samba4-4.2.10-6.el6_7.x86_64 and have had ongoing issues since it was installed. Everything runs along just fine for a while (an hour or so) and then our logs start filling with [2016/04/13 17:51:21.635283, 0]

Hi. Guys I have a big issue, working with my domain member running samba Version 3.6.23-42.el6_9. As member of my domain running samba -- LIving the dream...

What info could help? Centos 6 is still not EOL yet (2020 right?). On Mon, May 29, 2017 at 2:25 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 29 May 2017 14:12:34 -0700 > Alberto Moreno via samba <samba at lists.samba.org> wrote: > > > Hi. > > > > Guys I have a big issue, working with my domain member running > > samba

Hi Good Morning, Thank you for everyone and supported me, I struggled a lot to resolve the problem. However I got a solution for joining windows 10 clients to Samba PDC (Samba Version 3.6.23) . I changed workgroup name is from "example.com" to "example" ( I removed "." from workgroup name), then i can able to join windows 10 clients to Samba PDC without any other