Displaying 20 results from an estimated 6000 matches similar to: "Log all successful authentications"
2015 Dec 07
0
Log all successful authentications
Am 07.12.2015 um 23:49 schrieb Andrew Martin:
> I am running a Samba 4 AD server on Ubuntu 14.04. Is it possible to log
> whenevever a user successfully logs into a computer or whenever a successful
> LDAP authentication occurs? Ideally this would include both the username and the
> IP address from where the request originated. Is this possible?
consult the manpage for "log
2017 May 26
2
no share-listing
why in the world do i no longer see shares when using
smb://192.168.196.1/ but when i know the sharename and type
smb://192.168.196.1/data/ all is fine?
i first thought it was the security update from yesterday and/or "nt
pipe support = no" but both is not the case and i can't sy how long it's
that way because mostly using bookmarks
Fedora 24/25 and CentOS7 all the same
2016 Jul 26
6
NT_STATUS_INTERNAL_ERROR
Dear Rowland
Strange thing is that I do not receive notification on my email about your answers.
Here we run an internal DNS. Samba was configured with Bind 9 as secondary DNS.
When I put in domain.local settings, it is because we omit the company name. But the name of my domain ends with .local.
I disabled Avahi daemon.
When I try to run the command you quoted:
smbclient -k -L
2018 Jun 13
3
Samba 4.8 RODC not working
On Wed, 13 Jun 2018 11:12:43 +0200 (CEST)
Gaetan SLONGO <gslongo at it-optics.com> wrote:
> Hi,
>
>
> I was just investigating the winbind execution issue :
>
>
> This is what happens when winbind is started by samba
>
>
>
> [root at dmzrodc ~]# winbindd -D --option=server role check:inhibit=yes
> --foreground -S -d 10 Error setting option
2017 May 26
1
no share-listing
please read what i wrote
> i first thought it was the security update from yesterday and/or "nt
> pipe support = no" but both is not the case
no change when set it back to "yes"
Am 26.05.2017 um 15:42 schrieb Andrew Walker:
> That's because you set the parameter "nt pipe support = no".
>
> On Fri, May 26, 2017 at 8:28 AM, Reindl Harald via
2016 Dec 30
2
ADS domain member: winbind fails
On Fri, 30 Dec 2016 18:53:22 +0100
Volker Lendecke via samba <samba at lists.samba.org> wrote:
> On Fri, Dec 30, 2016 at 05:55:58PM +0100, Stefan G. Weichinger via
> samba wrote:
> > Am 2016-12-30 um 17:42 schrieb Rowland Penny via samba:
> >
> > >OK, try this, open a terminal, type 'winbindd -i'
> > >This should directly run winbind in the
2020 May 20
4
smbclient oddness
Are there any logs on the client or server at a higher log level?
Andrew Bartlett
On Wed, 2020-05-20 at 12:39 +1200, Grant Petersen via samba wrote:
> I forgot to mention that using the smbclient option
>
> -A /etc/cred/authfile
>
> behaves the same way as attempting to manually enter the password on
> the command line; failing in 4.12.2 and working in 4.11.0
>
>
2017 Aug 15
2
cannot join windows 7 samba4-ad-dc fresh install, get NT_STATUS_INTERNAL_ERROR
Hello, sorry for the delay,
kinit goes fine, here is the output of
klist :
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: administrator at RONA.LOC
Valid starting Expires Service principal
15.08.2017 13:36:07 15.08.2017 23:36:07 krbtgt/RONA.LOC at RONA.LOC
renew until 16.08.2017 13:36:03
------
here's the output of
smbclient -k -L //sambadc.rona.loc -d9
2018 Jan 16
2
User Permissions issue
Hi
I have two Samba 4 DC’s as below
server-1 with all FSMO roles running Samba 4.6.12 on Ubuntu 12.04
server-2 joined to server-1 as a DC running Samba 4.7.4 Ubuntu 16.04
The problem is when I share files from my Windows 2008 file sharing server
which shows it is logged on to Server-2 DC and the client PC which logs on
to the server-1 DC cannot access the shared folder and gives an error Logon
2018 Jun 13
2
Samba 4.8 RODC not working
On Wed, 13 Jun 2018 11:33:48 +0200 (CEST)
Gaetan SLONGO <gslongo at it-optics.com> wrote:
>
>
>
>
> Here it is. It talks about homes share but I think we don't care ?
> Final error is not explicit to me.. Maybe you?
>
>
>
> INFO: Current debug levels:
> all: 10
> tdb: 10
> printdrivers: 10
> lanman: 10
> smb: 10
> rpc_parse:
2013 Apr 06
1
Samba4 member of an another « Samba4 » domain
Hi,
I have a Samba4 domain controller installed on Debian Wheezy (Domain = CHEZMOI.PRIV). I try to installed an another Samba4 server which is just a member of the CHEZMOI.PRIV domain. But I don't succeed. I have followed this page :
https://wiki.samba.org/index.php/Samba4/Domain_Member
But I have :
~# net ads join -U administrator
Enter administrator's password:
kinit succeeded but
2018 Oct 17
3
Samba v3 works with LDAP, but not Samba v4
On Tue, 2018-10-16 at 15:18 -0700, Emil Henry wrote:
> Hi Andrew!
>
> I included it in one response, but may have not done a Reply All. Am resending it.
>
> Thanks.
It is reading the hashes, so it looks like it is working. Dumb
question, but are you really sure the password is right?
Otherwise, it might be some very odd NTLMv2 thing. Try (on the client)
'client ntlmv2 auth
2019 May 31
2
Inconsistency with LANMAN1 and Samba 4.9
On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote:
> On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote:
> > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password,
> > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash.
> > > >
> > >
2013 Dec 10
2
Can't connect to my NAS after samba 4 update
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 ~]$
2018 Oct 17
4
Samba v3 works with LDAP, but not Samba v4
On Tue, 2018-10-16 at 20:20 -0700, Emil Henry wrote:
> Hi Andrew!
>
> I am not 100% sure that the password is correct. I was told that it
> was changed to the one I am testing. But, when I try the old
> password, I get a different error message (NT_STATUS_INVALID_SID). I
> will attached the output.
Then it is the old password, and you have other issues you need to sort
out.
2016 Apr 01
2
knit and smbclient executed with different users but no error thrown
Hi,
I am using different users while executing kinit and smbclient as shown
below, but I am not getting any error. How can a initial ticket granted to
one user can be used for another user. Can you give some clarification. I
am not an expert hence this doubt. I am using win 2003 AD.
[root at 0050568B7DEB samba-4.3.4]# klist
klist: No credentials cache found (ticket cache FILE:/tmp/krb5cc_0)
2018 Sep 14
2
kpasswd_samdb_set_password: domain\user (S-...) is changing password of user@domain
Is there a way to translate the userSid into a human readable format, so I
don't have to look it up each time?
For now, my workaround for now is to set my log level to 5, but then turn
lots of stuff down to 1 manually. Like this:
log level = 5 tdb:1 printdrivers:1 lanman:1 smb:1 rpc_parse:1 rpc_srv:1
rpc_cli:1 passdb:1 sam:1 auth:1 winbind:1 vfs:1 idmap:1 quota:1 acls:1
locking:1 msdfs:1
2017 Sep 04
5
SPNEGO login failed: An internal error occurred
Hi,
I setup a test envirement on a dedicatet server.
OS: debian stretch
samba: 4.5.8
smbclient: 4.5.8
I set it up as DC, the provision work well, yes I've delete the
smb.conf in advance.
When I test kinit I got an kerberos ticket, but I've problems with
smbclient either I use kerberos or password auth.
Myabee someone could help me?
my smb.conf:
# Global parameters
[global]
2013 May 28
2
Samba4 + Shared Folders
Hello dear,
Could help me?
I have configured a server with CentOS and Samba4, both Linux and
Windows stations joined to the domain with successfully. However, I
can not share access to a single set in Samba4, except share folder
default (sysvol and netlogon). The error returned is "Permission
Denied".
Follow my smb.conf:
# Global parameters
[global]
workgroup = TEST
realm = test.local
2014 May 14
2
Intermittent failure
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