similar to: nmbd keeping old data

We are having a problem that I suspect is due to nmbd giving out obsolete information. Unfortunately the problem can not be reproduced consistently. We have a build system that runs on our Solaris machines where the final files are copied into a distribution directory after being built. Note that copying a new file on top of an old one does not change the file ID. PC users sometimes will see the

Hi Marc, I'm a little confused. The values I provided for client and server max protocol are default values. At least according to the command 'samba-tool testparm -v'. I have not explicitly set them in my smb.conf file. I assume SMB3 became the default at some point with a release? I'm worried now that I must make explicit changes to my smb.conf file when default values are

On 06/03/15 13:36, James wrote: > Hi Marc, > > I'm a little confused. The values I provided for client and server > max protocol are default values. At least according to the command > 'samba-tool testparm -v'. I have not explicitly set them in my smb.conf > file. I assume SMB3 became the default at some point with a release? I'm > worried now that I must

Using Wireshark I see the protocol used as SMB2. Using a Windows workstation I tested by navigating to files and folders on my member server or to my sysvol folder on a DC. On 3/6/2015 8:56 AM, Rowland Penny wrote: > On 06/03/15 13:36, James wrote: >> Hi Marc, >> >> I'm a little confused. The values I provided for client and server >> max protocol are default

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

>> On Fri, 30 Sep 2016 12:14:44 -0400 (EDT) >> schulz at adi.com (Thomas Schulz) wrote: >> >>>> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) >>>> Thomas Schulz via samba <samba at lists.samba.org> wrote: >>>> >>>>> We are running Samba 4.4.6 as a file server. >>>>> In the logs for a few client machines I

> On Fri, 30 Sep 2016 12:14:44 -0400 (EDT) > schulz at adi.com (Thomas Schulz) wrote: > > > > On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) > > > Thomas Schulz via samba <samba at lists.samba.org> wrote: > > > > > > > We are running Samba 4.4.6 as a file server. > > > > In the logs for a few client machines I see entries such as: >

hi, i've a debian sarge setup with samba 3.0.10 with ldap as SAM backend. every thing used to work as expected, but last week the machine went down. an analysis of the problem has showen, that with increasing uptime there is a growing number of smbd processes that caus 100% CPU utilation. tests have showen, that i can kill these processes without harming smb conecctivtiy. this is a

> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) > Thomas Schulz via samba <samba at lists.samba.org> wrote: > > > We are running Samba 4.4.6 as a file server. > > In the logs for a few client machines I see entries such as: > > > > [2016/09/29 22:36:58.862575, 0] > > ../source3/param/loadparm.c:4402(widelinks_warning) > > Share 'IPC$'

Forwarded to respective mailing lists Regards, Lutz ----- Forwarded message from Thomas Schulz <schulz at adi.com> ----- X-Original-To: jaenicke at serv01.aet.tu-cottbus.de X-Original-To: rt at aet.tu-cottbus.de Delivered-To: rt at master.openssl.org Date: Wed, 12 Apr 2006 14:42:27 -0400 (EDT) From: Thomas Schulz <schulz at adi.com> To: openssl-bugs at openssl.org Subject: 0.9.8a:

> On 26/10/15 18:26, Thomas Schulz wrote: > > This may not be a Samba problem, but perhaps people here know the answer. > > > > We are installing some Windows 8.1 Pro computers. The servers running Samba > > 4.2.19 and 4.3.0 are not showing up in the Network display. Our domain > > controller is also not showing up. The Windows 7 computers are showing up. > >

>> On 26/10/15 18:26, Thomas Schulz wrote: >>> This may not be a Samba problem, but perhaps people here know the answer. >>> >>> We are installing some Windows 8.1 Pro computers. The servers running Samba >>> 4.2.19 and 4.3.0 are not showing up in the Network display. Our domain >>> controller is also not showing up. The Windows 7 computers are

> On 2/16/2015 10:14 AM, Thomas Schulz wrote: >>> My apologies for being too new to this whole process... >>> >>> Server was AIX 5.3/Samba 2.2.7, authenticating only against the AD. No >>> single sign-on, kerberos, or LDAP to my knowledge; smbd processes never >>> load kerberos or LDAP libraries. Upgraded to AIX 7.1/Samba 3.3.12, which >>>

-----Urspr?ngliche Nachricht----- > Von:schulz at adi.com <schulz at adi.com> > Gesendet: Mon 6 April 2015 19:17 > An: mmuehlfeld at samba.org; samba at lists.samba.org > Betreff: Re: [Samba] Samba 4.2.0: Group write permission not honored > > > Hello Thomas > > > > Am 06.04.2015 um 17:22 schrieb Thomas Schulz: > > > For anyone considering using

>>> Hello Thomas >>> >>> Am 06.04.2015 um 17:22 schrieb Thomas Schulz: >>>> For anyone considering using Samba 4.2.0, be aware that there is a >>>> problem with group write permission not being honored. >>>> >>>> This is seen on both Linux and Solaris. We have a setup where we have >>>> project directory trees

>>>> Hello Thomas >>>> >>>> Am 06.04.2015 um 17:22 schrieb Thomas Schulz: >>>>> For anyone considering using Samba 4.2.0, be aware that there is a >>>>> problem with group write permission not being honored. >>>>> >>>>> This is seen on both Linux and Solaris. We have a setup where we have

> On Wed, Jun 29, 2016 at 12:11:51PM -0400, Thomas Schulz wrote: > > > > Here is what I could find. The iso file is created on a Solaris system on > > a file system that is NFS mounted from our main file server. Then it is > > burned to a CD on a Windows 7 PC through a Samba server running on a > > different Solaris machine (Solaris 10) that is also NFS mounting

Hi all. Is it possible to change DC administrator name from 'Administrator' to something else, for example, to 'DomaAdministr' ? If it is, is it possible via command-line or via LDAP browsers only ? If it do via LDAP browser (of course cn will be changed) , will Samba4 contunue to work correctly ? Also, I offer to add new switch to Samba4 DC provision such as 'adminname' ,

Hi Timothy, On Thu, 2019-05-23 at 14:03 +1000, Timothy Lee wrote: > I can provide zh-CN, zh-HK and zh-TW translations of the content. That's awesome! The files you need to edit are the following: - Rolling notes of CentOS installer https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-CN.po https://git.centos.org/centos/Artwork/blob/c8/f/rnotes/PO/zh-HK.po