similar to: Samba 4 configuration with multiple Windows version

On 08.04.19 16:20, L.P.H. van Belle via samba wrote: > Hai Basti, > > Anything in the windows even logs? > This might be related to smb1 and windows automaticly removing it. smbstatus say that all open connections are SMB2_10 and SMB3_11 the windows log say: german text and errorcode C0000006 > > Or something else. > Can you check with mtr from a windows pc to the

I recently discovered that only the Default Domain Policy is being applied. All other GPOs seem to be ignored. All Sysvol filesystem objects have the right permissions. Both DCs are running Samba 4.4.3 over CentOS 7. There are no related errors in logs or Windows Event Viewer. Other policies did work before. I noticed that the corresponding filesystem objects were lastly placed on users’ desktops

I am using Samba as Active Directory Domain Controller as well as file server, serving a network of Windows clients. I recently upgraded a bunch of computers from Windows 7 to Windows 10 release 1909. I just discovered that Under Windows 10, as a Domain Admin, when I try to add a new permission to a folder or file on Samba shares through the Advanced security tab I cannot do it because the

Hi, We have a NAS server with OpenMediaVault on a Debian system. Mainly we work directly with documents from the LibreOffice and Office tools. Sometimes we note at the opening of a LO document that the file is corrupted and not repairable. We know LO documents are a bunch of files embeded in a compressed ZIP archive. The most of time we can repair them in replacing the corrupted elements

*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at

hello, we have a samba AD DC and some samba fileservers. Version: 4.5.16-Debian (van belle repo) Debaian version: 9.8 Some clients windows 7 and windows 10 randomly lost connection to share. Loglevel is set to 3. But i can't find any relevant entries in the log. How can i debug the connection lost? Best regards;

On Fri, Jan 23, 2015 at 01:08:31PM -0800, Jeremy Allison wrote: > On Fri, Jan 23, 2015 at 10:05:44PM +0100, Markus Doits wrote: > > > > On 23.01.15 19:57, Miguel Medalha wrote: > > > I am using Samba 4.1.16 with smb2/3 and symbolic links are working alright. > > > > > > Following the smb.conf man page, I use: > > > > > > unix extensions

I don't have any lines in my configuration file for any of the servers, how can I tell what the default protocols are? Are the defaults controlled by samba or the kernel? Chris On 6/15/2020 2:13 PM, Fred Smith wrote: > On Mon, Jun 15, 2020 at 11:23:54AM -0500, Christopher Wensink wrote: >> I have a handful of Linux Servers, running Centos 6.10, and 6.8 with the >> main host

Dne 2017/03/20 v 10:05 Rowland Penny napsal(a): > On Sun, 19 Mar 2017 23:23:58 +0100 > Michal Kavan via samba <samba at lists.samba.org> wrote: > >> yes, its looks like win7/10 problem (but only on samba 4.x) to me, >> but i have no idea what to do (except downgrade to 3.6.x) >> >> >> server max protocol = SMB3 >> client max protocol = NT1

Hello, I have try windows 10 in an Samba 4.4.5 NT4-style domain. With some registry hacks (DomainCompatibilityMode and DNSNameResolutionRequired) it can be an member of the domain. When i try to login with domain member i get the error "There are currently no logon servers available to service the logon request" At

> > => many protocols from different clients (Windows 7 and 10 and Debian 9, > 10 and 12) : SMB2_02, SMB2_10, SMB3_11, NT1 A long time ago, we had a problem with oplocks causing system hangs. It COULD be related, and I think we ended up downgrading the kernel to 4.9. https://bugzilla.kernel.org/show_bug.cgi?id=198349#c42 But I've since upgraded to OMV 6+ without any problems.

Samba Guru's, As a point of clarification in our Samba setup... We are currently running Samba 4.3.11 on Ubuntu Server 16.04. When running smbstatus it shows the following... Windows 7 machines connect showing SMB2_10. Windows 10 machines connect showing Unknown (0x0311). Supposedly Windows 10 machines should show SMB3_11. Curious if they are connecting correctly and/or if changes

Let me be the first (maybe): CentOS 5.2 is here (at least): http://mirror.chpc.utah.edu/pub/centos/5.2/ Thank you all who worked on it! -------------- next part -------------- No virus found in this outgoing message. Checked by AVG. Version: 8.0.100 / Virus Database: 270.4.1/1513 - Release Date: 22-06-2008 7:52

On Fri, 11 Oct 2024 15:46:23 +0200 "lnj.sam--- via samba" <samba at lists.samba.org> wrote: > Hi, > > We have a NAS server with OpenMediaVault on a Debian system. > > Mainly we work directly with documents from the LibreOffice and > Office tools. > > Sometimes we note at the opening of a LO document that the file is > corrupted and not repairable.

Hi, Can I request some suggestions regarding the following? Issue1 In our AD server, we are not seeing the hostname of the machine in smbstatus, it only shows IP. How can we see the hostname? The server can ping/resolve the hosts in question. PID Username COM Machine Protocol Version Encryption Signing

On Tue, Mar 13, 2018 at 09:08:36PM +0000, Miguel Medalha via samba wrote: > > > On 13-03-2018 19:22, Karolin Seeger via samba-technical wrote: > > ======================================================== > > "It is time that we all see gender as a > > spectrum instead of two sets of > > opposing ideals. We should stop > > defining each other

On Tue, Mar 13, 2018 at 09:08:36PM +0000, Miguel Medalha via samba wrote: > > > On 13-03-2018 19:22, Karolin Seeger via samba-technical wrote: > > ======================================================== > > "It is time that we all see gender as a > > spectrum instead of two sets of > > opposing ideals. We should stop > > defining each other

The Wiki page you pointed to describes a modification to the *Default Domain Policy*. This is probably why you never met the issue I described. As I reported on my previous post, the Default Domain Policy was the only one that kept working after the Microsoft update. All the other GPOs that I had set stopped being applied.

I am about to install a new server running CentOS 5.4. The server will contain pretty critical data that we can't afford to corrupt. I would like to benefit from the extra speed and features of a ext4 filesystem but I don't have any experience with it. Is there some member of the list who can enlighten me on whether ext4 is mature enough to be used on a production server without too

I'm struggling with trying to create a unified, ldap-backed for my home network. I have an existing directory that handles my posix logins correctly and I'm able to auth smb users against those accounts, but I'm not able to join any machines to the directory. It would be profoundly helpful to see a ldif dump of a working configuration. Surely others have created similar setups at home