similar to: Samba 3.6 -> 4.2 upgrade on FreeBSD

On 04/07/15 11:35, Andrea Venturoli wrote: > Hello. > > I know this is half OS-specific: I already asked on freebsd-ports@, > but got no answer so far... > > Since 3.6 has been EOLed I'd like to upgrade all my such Samba > installations to 4.2. > Right now I don't want to switch any of them to AD; I just want to > keep running as I do now, but with a supported

On 07/04/15 13:04, Rowland Penny wrote: > Hi, never used freebsd, but 4.2 is not just an AD DC, it is also > supposed to be a replacement for the old 3.6 series and work in the same > way. That's what I'm trying to achieve. > There are some changes to what can and cannot go into smb.conf, but > these are minor and can easily be identified by reading the smb.conf >

Hello, I have attempted to install samba36 on a base install of FreeBSD 9.2 I have installed this same package about 30 days ago and had no problems what so ever. after the install, I add the line to FreeBSD /etc/rc.conf file - samba_enable="YES" Reboot the server and an error appears - WARNING /var/db/samba is not a directory I make the basic smb.conf changes like I have always

I posted this a while ago on the FreeBSD forums but received no response so I thought I'd ask here. If things are out of date, it's simply due to the length of time between my original post and now. A few updates I've noted since the saga began. I'm trying to do a long overdue upgrade from samba 3.6 to 4.x (I've tried all available 4.x releases from ports, 4.2, 4.3, and 4.4

On 05/07/15 14:59, Andrea Venturoli wrote: > On 07/04/15 13:04, Rowland Penny wrote: > >> Hi, never used freebsd, but 4.2 is not just an AD DC, it is also >> supposed to be a replacement for the old 3.6 series and work in the same >> way. > > That's what I'm trying to achieve. > > > >> There are some changes to what can and cannot go into

On 07/05/15 16:19, Rowland Penny wrote: > Did the smb.conf above work on samba 3.6 ? Absolutely! It's still working now. > I would have expected the ldap lines to be something like these: > ldap suffix="dc=ventu" > ldap admin dn="cn=root,dc=ventu" I have these. > ldap machine suffix = ou=machines > ldap user suffix = ou=users > ldap group

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, i try to use a glusterfs with "vfs objects = glusterfs" settings in smb.conf. But if I try to access the volume I allways getting "tree connect failed: NT_STATUS_BAD_NETWORK_NAME" If I add another Share directly inside the mountet glusterfs I can access the share und read and wirte alle the data. Here is my smb.conf: -

On 11/07/15 10:16, Rowland Penny wrote: > On 11/07/15 04:06, Lee Brown wrote: >> Hi Everyone, my first foray into Samba and AD both. >> >> Not sure if this is an OS or configuration problem. I've found similar >> issues, but nothing either recent enough (is related to samba 3) or >> close >> enough. >> >> FreeBSD-10.1-RELENG, Samba 4.2.2.

On 07/06/15 10:17, Rowland Penny wrote: >> > ldap machine suffix = ou=machines >> > ldap user suffix = ou=users >> > ldap group suffix = ou=groups >> >> 3.6 works without these, why shouldn't 4.2? >> AFAIK, these can help performance, but with 3 PCs and 5 users they >> should practically make no difference. >> BTW, in my case

Hi, I'm having some troubles with my samba configuration: I'm running a FreeBSD 8 file server with samba version 3.2.15. The port was compilated with WinBIND and UTMP support. Samba is started by the /etc/rc.conf option: samba_enable="YES" so that all smbd, nmbd and winbindd daemons are launched. There is no fw on the box. I used the smb.conf.default configuration file.

On 06/07/15 08:21, Andrea Venturoli wrote: > On 07/05/15 16:19, Rowland Penny wrote: > >> Did the smb.conf above work on samba 3.6 ? > > Absolutely! It's still working now. > > > > > >> I would have expected the ldap lines to be something like these: > > ldap suffix="dc=ventu" > > ldap admin dn="cn=root,dc=ventu" > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 13.02.2015 um 12:21 schrieb Ralph B?hme: > Hi Stefan, > > On Fri, Feb 13, 2015 at 12:02:20PM +0100, Stefan Kania wrote: >> [daten] comment = Daten im Cluster path = /glusterfs/daten/ read >> only = No kernel share modes = No >> >> >> [daten2] comment = Daten im Cluster ?ber gluster-vfs path = / > >

It's me again :-) Now we have DDNS with DHCP running but we have a problem on one of our two DCs. Btw we used the setup and the script from wiki. Doing a "dhclient" on a host we are getting the following messages: ------------- Mai 16 12:13:28 samba41 dhcpd[3961]: Commit: IP: 192.168.0.249 DHCID: 1:50:5b:5d:1c:ab:aa Name: horst Mai 16 12:13:28 samba41 dhcpd[3961]: execute_statement

I need some help in configuring samba on a FreeBSD 8.0 server. I've used the following as a base. My goal is to have a samba share where I can set permissions for Active Directory users. I don't care about SSHing into the server using Active Directory account information. http://forums.freebsd.org/showthread.php?p=64144&#post64144

I have Googled my brains out without success, and I'm hoping that someone here can give me some tips. I'm trying to build a new file server, and I've concluded that ZFS is the technology that I want to use. After doing some research I settled on FreeBSD 10 as the platform to provide it. I have an existing AD domain (two Samba 4.1.4 DCs running on Debian) and the file server will be

The DDNS setup from the wiki uses the keytab of the seperate "Unprivileged user for TSIG-GSSAPI DNS updates via ISC DHCP server" you have to Check this one not the one which BIND uses. Regards Am 16.05.2018 um 12:45 schrieb Rowland Penny via samba: > On Wed, 16 May 2018 12:32:52 +0200 Stefan Kania via samba > <samba at lists.samba.org> wrote: > >> It's me

I am rather at a loss as things seem to change by themselves on this Vista machine. Here's the setup: Vista client, FreeBSD 6.2 server with samba 3.0.25; also a FreeBSD 4.11 machine (server) with samba 2.2.12 Vista connected to samba 3 with password and the machines were present on the network. Then the machines would not show up on Vista at all; they could be pinged and they could be

On Sat, 12 Aug 2017 19:48:16 -0500 Ian T via samba <samba at lists.samba.org> wrote: > I posted this a while ago on the FreeBSD forums but received no > response so I thought I'd ask here. If things are out of date, it's > simply due to the length of time between my original post and now. A > few updates I've noted since the saga began. > > I'm trying to

On Tue, Jan 31, 2017 at 2:45 PM, Rowland Penny via samba <samba at lists.samba.org> wrote: >> /etc/resolv.conf: >> root at nickel:~ # cat /etc/resolv.conf >> nameserver 192.168.11.5 >> nameserver 192.168.1.4 >> domain mydomain.local >> > > I take it at least one of the above nameservers is the AD DC, is the > other another AD DC ? If it isn't,

Hi all, I'm on FreeBSD11 and I install samba36. I have some users and groups. user1, user2 -> group1 user3->group3 user4,user5->group4 I have a share: /extra/samba-test Access to the share is : user1->writable user4->readable group4->writable group3->writable My config file is: [samba-share] comment= aa path= /extra/samba-test public= no browsable= yes writable=no