similar to: Windows 7 login fails after server crash

Suggested changes applied to smb.conf (and yes, server role is classic PDC): server max protocol = NT1 client signing = auto client ipc signing = auto server signing = auto With no apparent change to the behaviour or resolution to the problem(s). I'm particularly mystified by the logging-in behaviour (that is, if I manage to do it quickly I can log in, but if I

Hi all, A - I thought badlock mitigation was about encrypting SMB traffic, at least most part of it. And this encryption of most part of data transfer could (or should) lower performances. It seems I was wrong: smallest part (something like commands) are encrypted but not SMB traffic (ie file transfer). This for SMB protocol prior to SMB3 (which comes with windows 8). B - According to what I

I have had a very odd problem for a while now, and am hoping this will ring a bell for someone who can point me in the right direction. I had a previous Samba DC (v3.5.6) in my home network, running on a command-line Slackware box. For a variety of reasons I decided to switch to Debian Jessie, which included an upgrade to Samba 4.2.10. I did NOT properly migrate my samba files to the new

On 20/06/16 19:53, Dale Schroeder wrote: > On 06/17/2016 4:31 PM, peter lawrie wrote: >> Hi all >> About 18 months ago I connected 14 new Windows 7 PCs to a Centos5.1 >> server >> with samba3x as domain members. There are no other servers on site. >> Today, I had to visit to connect up a PC in a new location. As I would >> normally do I checked for Centos

I disabled client signing from the client side, via OS X's global nsmb.conf file: https://discussions.apple.com/message/30282470#30282470 The performance was back to over 600 MB/s, as compared to 60 MB/s with signing. It just seems a bit weird to me that Apple, in response to the Badlock bug, would have changed the OS X client default to something with such drastic performance implications,

As an update to fix the badlock vulnerability I applied some updates to our (RHEL5-based) samba printer server last night, taking it from version 0:3.5.10-0.109.el5_8 to 0:3.6.23-12.el5_11 (rpm package versions). After this change attempts to add printer drivers with cupsaddsmb produced errors of the form: Running command: rpcclient localhost -N -A /tmp/cupsc7GVnF -c 'adddriver

Running a mix of samba versions (3.6.25 and 4.5.1) in two domains- one "classic" (with samba domain controllers) and one AD (with windows domain controllers.) The eventual goal is to drop the classic domain in favor of the AD domain. Also trying to move from samba 3.x to 4.x since Samba 3 is EOL'd. the "wbinfo -u" command will list users in the servers domain

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although

ORACLE have released this patch for Solaris 10 - Samba v3.6.25: IDR152387-03 addressing CVE-2016-2118 (BADLOCK) and other CVEs for S10 SPARC Which has addressed our issue. Thanks -----Original Message----- From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gaiseric Vandal Sent: 07 June 2016 14:51 To: samba at lists.samba.org Subject: Re: [Samba] Solaris 10 Configure failure

I'm seeing these problems with a samba-4.5.x that I wish to be a member of a samba-3.6.x PDC (NT4 style domain controller). =========================== net rpc join -S PDC ... smb_signing_good: BAD SIG: seq 1 Failed to join domain: failed to lookup DC info for domain 'EXAMPLE' over rpc: Access denied =========================== =========================== net rpc info ...

I have a Fedora Core 23 Linux machine configured as a samba member of a "classic" domain. The DC's Samba 3.6.25 NOT patched for badlock. Since upgrading to Samba 4.3.8 and (I think from 4.3.6 or 4.3.4) , domain users can no longer access resources. (upgraded to 4.3.9, same problem) Since I had to roll back my Synology appliance to a previous OS, and reviewing other

On Fri, 21 Apr 2017 12:00:59 -0400 Eleuterio Contracampo via samba <samba at lists.samba.org> wrote: > [2017/04/21 12:47:55.219297, 0] > ../auth/gensec/gensec.c:257(gensec_verify_dcerpc_auth_level) > > Did not manage to negotiate mandetory feature SIGN for dcerpc > auth_level 6 > I think you may be running into an artefact of the badlock patches, for which Win7 will

On Fri, May 27, 2016 at 3:55 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote: > Is the netapp a member of the domain? Yes. > My assumption is that you can have domain members that are patched with domain controllers that are not. I don't know what you mean by that. This worked before the samba CVE changes took effect in the latest samba3 RPMs distributed by the CentOS

On both Samba 4.5.1 member server and Samba 3.6.25 member server I tried the following command wbinfo –set-uid-mapping=35049,S-1-5-21-xx-xx-xxx-xxx this should have created a mapping entry consistent with the one on the domain controller for a trusted user But I got the following error failed to call wbcSetUidMapping: WBC_ERR_NOT_IMPLEMENTED As far as I can tell from network

That is really weird. I think what is happening is that if you log in immediately you are using cached credentials. If you wait a little bit then your network connections are up and you are truly doing network authentication. If you were do unplug from the network, reboot, login with cached credentials, and then reconnect network cable I would suspect your access to shares would be OK. I

Just a follow-up. Still, no resolution. I've tried different combinations with "client ipc signing" without luck. A traffic dump shows the problem as: i) windows XP client sends a DCE/RPC SAMR command GetDomPwInfo ii) samba DC responds with DCE/RPC Fault nca_proto_error I've also tried fiddling with Local Security Policy registry values at the Win XP machine, but got nothing

>> >> Short summary; this is on a old Solaris 10 system, the virtual host >> is a Solaris zone, or two instance of the zone on two hosts for >> failover. The config is years old and I had no part in this, but we >> needed to upgrade Solaris Oracle has only managed to release 3.5.8 or >> something close to that as patches. I could of course compile my own

Do you know why Red Hat updated libtdb as part of their remediation for Badlock on Samba4? https://rhn.redhat.com/errata/RHSA-2016-0612.html On Thu, Jun 2, 2016 at 2:37 PM, Jeremy Allison <jra at samba.org> wrote: > On Thu, Jun 02, 2016 at 11:29:25AM -0500, Sam Gardner wrote: > > Does mitigation of the so-called BADLOCK CVE (CVE-2016-2118) for Samba > 3.x > > imply an

Hi, Due to "Red Hat Vulnerability Response: BADLOCK", an automatic samba package RHEL5 update was apply on our system. This broke "The trust relationship between this workstation and the primary domain failed" (error message logon client) in my environnement production. So, I use now 3.6.23-12.el5_11, I see they are new directive for smb.conf and some others more restrict

I have a Synology NAS array appliance. It is linux based and uses samba for file sharing. Normally the config is done via a gui interface but you can ssh to the array. The domain controllers are running Samba 3.6.x in classic domain mode. I have member servers running 3.6.x and 4.3.8. no problem. I recently updated the Synology "OS." The current version of samba is