similar to: samba documentation error

On Wed, 27 Mar 2019 13:00:42 +0100 Franta Hanzlík <franta at hanzlici.cz> wrote: > Yes, is no difference between '-UAdministrator' and '-U > Administrator'. But it seems, as ldbsearch in 4.9.5 is different than > 4.9.4-. (I was furious with that, because I found lot articles on > net, where -U _username_ was stated. > > My ldbsearch is from pure

I noticed lots of smbclient options are missing in Samba 3.0.14a when compared to 3.0.13 - notably, all user/authentication options - so I can't connect now as a specified user anymore. Is it just my build, or is it "official"? Samba 3.0.14a: # smbclient --usage Usage: [-?] [-?|--help] [--usage] [-R|--name-resolve NAME-RESOLVE-ORDER] [-M|--message HOST] [-I|--ip-address IP]

Hi all, Situation: We use smbtar for backups, incrementals done using -N <last date file>, and this has worked well with samba 2.2.x After upgrading to 3.0b3, using the -N (newer) option to smbtar causes a bad interaction with smbclient. Eg,: # smbtar -s PC -x Share -u User -p Pwd -d / -t - -N last-backup -v gives (if you print out the eval at the end of smbtar script): eval

On Fri, 29 Mar 2019 09:28:37 +0100 Franta Hanzlík <franta at hanzlici.cz> wrote: > On Wed, 27 Mar 2019 13:11:08 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Wed, 27 Mar 2019 13:00:42 +0100 > > Franta Hanzlík <franta at hanzlici.cz> wrote: > > > > > Yes, is no difference between '-UAdministrator' and

hce <webmail.hce@gmail.com> wrote: > I built the samba from source samba-3.0.26a on FC6. But when I run > "nmbd -F --debuglevel=5 --configfile=/home/test/smb.conf > --log-basename=/home/test/log.txt", nothing happens. The process is > not there, the log file is not created. What could I be missing here? Not really samba-specific, but whenever I need to track down

Hi. We are using samba4 as our production AD for a while in a mixed (XP, win2k3, win7, win2k8) environment. This post: http://lists.samba.org/archive/samba-technical/2011-February/076525.html mentions that to raise the functional level one should use this command: samba-tool domainl evel raise --domain=2008 --forest=2008 but in our current git version this command doesn't work due to the

On Wed, 27 Mar 2019 13:11:08 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 27 Mar 2019 13:00:42 +0100 > Franta Hanzlík <franta at hanzlici.cz> wrote: > > > Yes, is no difference between '-UAdministrator' and '-U > > Administrator'. But it seems, as ldbsearch in 4.9.5 is different than > > 4.9.4-. (I was furious

On Fri, 29 Mar 2019 09:00:08 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 29 Mar 2019 09:28:37 +0100 > Franta Hanzlík <franta at hanzlici.cz> wrote: > > > On Wed, 27 Mar 2019 13:11:08 +0000 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > On Wed, 27 Mar 2019 13:00:42 +0100 > > >

Hello all, I'm having trouble logging into swat. Not even root can login! I'm using Rocks 4.1 (linux cluster based on CentOS) Has anybody experienced this? Thanks in advance! Santiago

On Wed, 27 Mar 2019 09:45:18 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > > I dont think one noticed this.. > > ldbsearch -H ldap://dc4 -UAdministrator > ldbsearch -H ldap://dc1 -U Administrator > > So whats the difference when you see this responce of the command: > Invalid option -U: unknown ... >

Hi, I'm trying to use SmbClientParser to implement a simple SMB crawler. After a lot of effort, I still could not get it to work. Here is my small test script: [CODE] #!/usr/bin/perl use POSIX; use Filesys::SmbClientParser; use DBI(); use Socket; use Sys::Hostname; use strict; my $host; my $smb = new Filesys::SmbClientParser (undef, ( user => '', password

Hi! Two problems: 1) I can access shares by IP but not by name, so I assume that WINS doesn't do its job for some reason, smb.conf: [global] wins support = yes name resolve order = lmhosts wins hosts bcast 2) I don't quite get it how smbclient works. As I mentioned name resolve does't work and hance smbclient -M MACHINE doesn't either but an IP should work: # nmblookup -A

Hallo, in 3.0.8pre2 the smbstatus command always shows connections _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for showing locks only: test2 # smbstatus --help Usage: [OPTION...] -p, --processes Show processes only -v, --verbose Be verbose -L, --locks

El 12/03/16 a les 17:08, Jeremy Allison ha escrit: > On Sat, Mar 12, 2016 at 12:50:50PM +0100, Luca Olivetti wrote: >> El 12/03/16 a les 12:37, Rowland penny ha escrit: >> >>> Well yes, but these are usually a mass market product and will no doubt, >>> in the fullness of time, get to use a version of Samba 4 seeing as how >>> 3.6 has been EOL since March

Hi, Thanks for answering my question on the new smbmount not working. I tried all variety of combinations on the commands you suggested, but they all simply do this: % smbmount -c //server/share 'mount /mnt/samba-share -n CLIENT -U user' Usage: smbmount service <password> [-p port] [-d debuglevel] [-l log] Version 2.0.3 -p port connect to the specified port

I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in the log.wb-<DOMAIN> file: ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) I suspect that this may caused by an ip4 address assignment clash as I am using the configuration and data structures copied from our running Samba-4.13 DC. When I run winbindd interactively I see this: #

Hi I use suse 10.0 and have problems to set up ntlm_auth for squid. It uses samba 3.0.20 and squid 2.5.stable10 I have set up winbind and everyhting seems to work. I've changes groupownerchip of /var/lib/samba/winbindd_privileged to squid. squid runs as group squid. Everyhting is working fine for several minutes. After a while it doesn't work anymore proxy:/var/log/samba #

Rowland Penny rpenny at samba.org Fri Aug 9 15:25:00 UTC 2024 On Fri, 9 Aug 2024 10:40:18 -0400 "James B. Byrne via samba" <samba at lists.samba.org> wrote: >> I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in >> the log.wb-<DOMAIN> file: >> >> ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) >> >>

El 12/03/16 a les 18:27, Jeremy Allison ha escrit: > On Sat, Mar 12, 2016 at 06:07:25PM +0100, Luca Olivetti wrote: >> Unfortunately it seems it is using a really old version of samba [...] >> Version 1.9.16p10 >> -D become a daemon >> -p port listen on the specified port >> -d debuglevel set the

Hi, Samba-friends I am not very deep in Samba *file* services, so please bear with me. The network admins of my employer alarmed me (being the local "Linux Guy") with this problem: * they run a 2-node fileserver cluster, based on RedHat (version?) with a Samba version announcing itself "2.2.7-security-rollout" or similar. * Samba runs in a chrooted environment. It was