Displaying 20 results from an estimated 5000 matches similar to: "Samba 4.2.0: Group write permission not honored"
2015 Apr 14
0
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 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
2015 Apr 13
0
Samba 4.2.0: Group write permission not honored
-----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
2015 Apr 06
1
Samba 4.2.0: Group write permission not honored
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 where the files are owned by various users but
also by a group that the various users are a member of. The group
permissions are set to allow group write access. With Samba 4.1.* and
2015 Feb 23
0
Samba 4.2.0rc4 can't authenticate users
>>> On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote:
>>>> 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 =
2015 Feb 20
0
Samba 4.2.0rc4 can't authenticate users
> > On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote:
> > > 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'
2015 Feb 17
0
Samba 4.2.0rc4 can't authenticate users
> Submitted bug 11098. Debug level 5 logs are attached to the bug along
> with the smb.conf file used.
>
> I am assuming that the problem is with the Wondows 2000 DC because I
> assume that 4.2.0rc4 would not have been made available if it could
> not authenticate against any domain controller.
>
> For us this is a fatal bug.
>
> > This problem shows up on both
2015 Mar 24
0
Samba 4.2.0 install failing with "Couldn't determine size of 'bool'
> Hi!
>
> On Mon, Mar 23, 2015 at 02:25:45PM +0000, Briar Jim wrote:
> > Hi all. I'm trying to install Samba 4.2.0 on a Solaris 64 bit Unix
> > server by doing the following but the configure script fails with
> > "Couldn't determine size of 'bool'", any ideas ? :-
>
> Solaris 10? I just checked, it seems to work on Solaris 11.
>
2015 Feb 12
0
Samba 4.2.0rc4 can't authenticate users
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
2015 Feb 12
1
Samba 4.2.0rc4 can't authenticate users
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 =
2016 Dec 02
0
Share 'IPC$' has wide links and unix extensions enabled
>> 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
2016 Oct 03
0
Share 'IPC$' has wide links and unix extensions enabled
> 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:
>
2006 Apr 12
0
[schulz@adi.com: 0.9.8a: DSA_generate_parameters & RSA_generate_key not in libcrypto]
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:
2016 Sep 30
1
Share 'IPC$' has wide links and unix extensions enabled
> 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$'
2024 Jun 09
2
Format
HI all,
My
I am trying to convert character date (mm/dd/yy) to YYYY-mm-dd date
format in one of the columns of my data file.
The first few lines of the data file looks like as follow
head(Atest,10);dim(Atest)
ddate
1 19/08/21
2 30/04/18
3 28/08/21
4 11/10/21
5 07/09/21
6 15/08/21
7 03/09/21
8 23/07/18
9 17/08/20
10 23/09/20
[1] 1270076 1
I am using the following
2019 Aug 10
0
samba-tool ou create "OU=del-ou, dc=atest, dc=com" fails with /var/lib/samba/private/sam.ldb: No such file or directory
On 10/08/2019 13:14, amitkuma--- via samba wrote:
> Hello,
>
> I am trying to use samba-tool to create OU on active directory.
>
> 1. Joined to domain.
> # net ads join -U <>
>
> 2. Listed GPO's on domain to check samba-tool script can pull the GPOs.
> # samba-tool gpo listall
> GPO : <>
> display name : test-Computers-GPO-1
> path
2019 Aug 10
2
samba-tool ou create "OU=del-ou, dc=atest, dc=com" fails with /var/lib/samba/private/sam.ldb: No such file or directory
Hello,
I am trying to use samba-tool to create OU on active directory.
1. Joined to domain.
# net ads join -U <>
2. Listed GPO's on domain to check samba-tool script can pull the GPOs.
# samba-tool gpo listall
GPO : <>
display name : test-Computers-GPO-1
path : \\atest.com\SysVol\atest.com\Policies\<>
dn :
2015 Oct 27
0
Not showing up in network listing on Win 8.1
> 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.
> >
2015 Oct 27
0
Not showing up in network listing on Win 8.1
>> 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
2015 Feb 17
1
AIX 7.1 Samba 3.6.23 Windows 2003 Server AD
> 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
>>>
2014 Mar 04
0
Dns update not working
I joined a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000
domain controller as an additional domain controller with the command:
samba-tool domain join adi.com DC -Uadministrator --realm=adi.com
--dns-backend=BIND9_DLZ
The messages indicated that this was mostly sucessfull with the exception
of the message:
NO DNS zone information found in source domain, not replicating DNS