similar to: [Announce] Samba 4.12.0rc3 Available for Download

A little summary of building Samba 4.12.0rc3 on OmniOS: The following 4 (5) small patches are needed in order to compile and run Samba 4.12.0rc3 on the latest OmniOS r151032p (OpenSolaris/Illumos variant): 1. ARRAY_SIZE is already defined in <sys/sysmacros.h> on OmniOS, put an #ifndef around it in lib/replace/replace.h (can be ignored but causes a gazillion compiler warnings :-):

On a fresh installed Illumos/Solaris in a VirtualBox Guest I get the following error after starting up samba 4.10: [2019/04/01 09:51:41.112485, 0] ../../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) tdb(/var/samba/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for /var/samba/lock/gencache.tdb: Device busy [2019/04/01 09:51:41.141396, 0] ../../lib/util/become_daemon.c:136(daemon_ready)

Hi Jeremy,   I got some info on that topic from the illumos devs:   > It's a sporadic issue, you're lucky enough to not encounter it on 4.9.5. > > I confirmed in 4.10.2, it happens: > > winbindd.log:  tdb(/tmw-nas-3p/samba/var/lock/gencache.tdb): tdb_open_ex: tdb_mutex_init failed for /tmw-nas-3p/samba/var/lock/gencache.tdb: Device busy > > So either apply OS fix, or

Hi, I've tested that samba (smbclient 3.4) cannot connect to a windows 7 share but however it is possible to mount such share with smbmount. When I try to connect specifying username and password I got a success but nothing happens: smbclient //s28/backupinfook -U backup Enter backup's password: session setup failed: SUCCESS - 0 while from

Hi all, I am running an smbclient 3.4.7 on a ubuntu server 10.04. This is a local network whose hostnames in the network are setup manually through /etc/hosts. Zeus is a server which contains a music share which I am trying to access. I haven't created any users or passwords. The idea is that anyone within the local network should be able to access the share with read permissions, so I

i've been integrating a Samba server into a mixed windows 2000/2003 authentication environment for use as a NAS device. i finally have things working for the most part, but in the process of debugging authentication i noticed an error when performing the following command: hmason@mpinas1:~$ smbclient -L localhost the error shows up when loglevel = 5 in smb.conf: Netbios name list:-

On Tue, 4 Sep 2018 15:13:10 +0200 Peter Eriksson via samba <samba at lists.samba.org> wrote: > I’m going to try to upgrade from 4.7.6 to 4.7.7 on one of our servers > soon and see if things break or not. With 4.7.6 things are stable at > least. > > Our file servers are in a Microsoft Windows domain (consisting of 6 > Microsoft Windows 2016 AD servers). > > >

Hello. I'm in need of some help to shed some light on a strange problem. The box is running Samba 4.1.7 on FreeBSD 9.2/amd64 and I suspect (though I'm not sure) all troubles started after the upgrade from 4.1.6. The setup is quite simple: no AD, no LDAP, only one server. A command as simple as "smbclient -U user //SERVER/SHARE", if fired up several times in a row on the

Hello, I've followed two or three articles on how to configure samba 4 as a member server. One of these articles is from the samba wiki: https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server The server joins, but it cannot authenticate users. I don't care about nss, winbind, etc. unless it is REALLY necessary. All I want is to use this server as a file server for workstations

On a recommendation from this list I checked the junklog file, the output from which I attached below. It looks as if it does not even see the linux machine as it indicates not seeing "explorer" which is the local netbios name. The Win XP machine does not even show in the log. Here is the last entry for nmbd.log: ***** [2003/11/21 06:24:58, 0] nmbd/nmbd.c:terminate(54) Got SIGTERM:

Hello all. I have been given an assignment to mount a share automatically for each user using a given Linux machine (Mandrake 10 in this case). This is working fine, thanks to pam_mount, BUT: The mounted share contains national characters like this: ? ? ?. The problem I'm having is that when I mount these on Linux the '?' looks like 'o' but cannot be accessed like that. It

Hello, I updated my system to samba 4: [richard at chakra ~]$ uname -a Linux chakra 3.10.18-1-CHAKRA #1 SMP PREEMPT Sat Nov 9 20:18:15 UTC 2013 x86_64 GNU/Linux [richard at chakra ~]$ samba --version Version 4.1.1 [richard at chakra ~]$ smbclient --version Version 4.1.1 And now all of sudden I cannot any longer connect to my NAS, this is the message I get in console: [richard at chakra ~]$

Hello, I am trying to set up samba on this host and testing it locally is giving me headaches right away. tom at hversa:~:~$ smbclient -L localhost -U% Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.8] Sharename Type Comment --------- ---- ------- homes Disk Home Directories print$ Disk Printer Drivers

Hello, I am investigating some strange authentication problems with our network. I am attempting to access a share on a DC with smbclient. If I authenticate with kerberos (kinit, then smbclient -k) then everything works fine. If, instead I use -U administrator -W DOMAIN, or just -U administrator, I get session setup failed: NT_STATUS_LOGON_FAILURE This is samba 3.3.2. Here is the d5 output

Experts, We've just migrated from samba 2.2.8a to samba 3.0.20b in a very large corporate environment. Everything was really fine in our lab, but we began experiment serious load problems on the productive servers the morning after the procedure took place. I'll try (briefly) to describe the characteristics of the scenario: Resources: Old Environment: Hardware:

FreeNAS / FreeBSD have native NFSv4 ACLs. They do however lack kernel oplock support so there are perhaps some caveats in that regard. On Thu, Jul 2, 2020 at 3:07 PM Strahil Nikolov via samba < samba at lists.samba.org> wrote: > Hi Kraus, > > I know that Gluster can be exported over NFS-Ganesha (supports v4.X), > Samba (protocol 1.0 in order to get 'real'

Hi Matej, I've cc'ed the developers mailing list for now... thanks for your report. Could you please send in some driver debug traces (starting it manually, using "usbhid-ups -DDDDD ...")? That would help in troubleshooting the issue. thx and cheers, Arno 2014-12-19 8:48 GMT+01:00 Matej Sekoranja <matej.sekoranja at gmail.com>: > > Update: driver is not stable. I

hi all, I have a strange problem using the libsmbclient api.. retrieving or stating files named with percents in is for some of them impossible. Example: a file located at "smb://test/test/%7C2.txt" cannot be retrieved with my code, smbc_open fails with the code NT_STATUS_OBJECT_NAME_INVALID. I am not sure but, url encoding/decoding that would escape strings with "percent"

Arno, what version of Solaris or libusb required the interrupt pipe hack? - Charles On Dec 19, 2014, at 7:00 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > Hi Matej, > > I've cc'ed the developers mailing list for now... > > thanks for your report. Could you please send in some driver debug traces (starting it manually, using "usbhid-ups -DDDDD

Hello, Sorry for take so long to answer, but I was not able to do the tests because the computer is in use and out of my office. Finally I've progressed in this topic with realmd, sssd and autofs, but now I'm locked on mounting shares from my member server. I'm able to use autofs and smbclient to mount and connect to sysvol share on my DC server, but when I try to connect to my