similar to: Samba 4.2.0 install failing with "Couldn't determine size of 'bool'

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 ? :- # gunzip samba-latest.tar.gz # tar -xvf samba-latest.tar # cd samba-4.2.0 # ./configure ... ... Checking for blksize_t : ok Checking for blkcnt_t

-----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

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

> 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: >

>> 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 &lt;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 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$'

I am trying to do something apparently unsupported in trying to use Samba 4.1.6 as an additional Active Directory Domain Controller with a Windows Server 2000 controller. I find that inbound replication works but outbound replication does not. Also DNS replication is not supported (this was noted during provisioning). In an effort to get outbound replication working, I manually entered all of the

> 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 >>>

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:

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

> > Good morning. > > I am looking to resolve the above vulnerability on our T-4 Solaris boxes. I have not worked or patch Samba before and not sure of the process. > > When I find and apply the patch will it resolve the issue on the version that we are running or do I need to bring our current version more up to date? > > Any assistance would be greatly appreciated.

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 =

Arter managing to build Samba 4.1.5 on Solaris 10 i386. I tried to join an existing Windows 2000 Server Active Directory domain as an additional domain controller. The join started to work and then died with the error: Error: Samba was compiled without the posix ACL support that s3fs requires. Try installing libacl1-dev or libacl-devel, then re-run configure and make. I downloaded acl-2.2.52 and

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. The domain controller is a Windows 2000 machine. I can manually map network drives to the servers

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$' has wide links and unix extensions enabled. These parameters are incompatible. Wide links will be disabled for this share. I assume that Share 'IPC$' is some sort of

When Samba goes up a more major version (such as from 4.4.* to 4.5.*), they sometimes rearrange what files go in what directories. The best way to avoid trouble is to clean out the old version before installing the new one. If you build Samba to be installed in something like /usr/local then it is easy to remove the old files before installing the new ones. If you build Samba to go into the system