similar to: upgraded DC shows IDs instead of usernames

Smbstatus doesn't resolve uids by default. You need to add --resolve-uids :) On 12/05/2020 10:38, Stefan G. Weichinger via samba wrote: > (resent ...) > > Am 12.05.20 um 11:22 schrieb Alex MacCuish via samba: >> Have you checked to make sure the winbind nss symlinks are present and >> correct? >>

(resent ...) Am 12.05.20 um 11:22 schrieb Alex MacCuish via samba: > Have you checked to make sure the winbind nss symlinks are present and > correct? > (https://wiki.samba.org/index.php/Configuring_Winbindd_on_a_Samba_AD_DC#Libnss_winbind_Links) I think I did that years ago ;-) ... but the links were missing again, thanks for the reminder. Created them, and restarted

On 30/08/2019 02:52, David Walling via samba wrote: > We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw

We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw this and connected it to the following open bug in samba

I am running samba 4.5.1 on Ubuntu 16.04. The samba server is running as an AD DC and stores the user profiles, the clients are all windows 10 professional. One user reported being locked out of the profile pretty regularly. After investigating the case I saw that a lot of files in the profile are still locked even after logging out and shutting down the system. After restarting the samba server,

I left in some of the parameters I've been testing commented out. Interestingly, we've noticed another client triggering the same type of symptoms every morning at around the same time. Those symptoms being a line 'lookup_name_smbconf for COMPUTERNAME$ failed' and a flood of failed connection attempts from the same client. The issue seemed to resolve itself after a few minutes

Am 11.05.20 um 14:12 schrieb Rowland penny via samba: > On 11/05/2020 12:49, Stefan G. Weichinger via samba wrote: >> Well, it was quiet and stable for quite a while now .. thanks to all the >> devs ;-) >> >> This weekend I upgraded some Debian servers, from Debian 9.12 to 10.4 >> >> One of these is a Samba-4.10.15 DC and I didn't touch the samba config

(resent) >> On 11/05/2020 15:24, L. van Belle via samba wrote: >>> For all Debian 10 people and strange things after upgrade of debian. >>> apt remove apparmor > I already replied that it isn't installed at all. Any other ideas? Am I the only one with Debian 10.4 and samba seeing this behavior? thx

Hello, I've recently set up Samba (4.12.3) on Arch Linux as the target for Time Machine backups for a couple of Macs. Shortly thereafter I started seeing OOMs whenever a backup would start. I stumbled upon disabling encryption on the server (i.e. changing "smb encrypt" from "required" to "off") to prevent this issue. After further digging, I'm able to

What for me looks a bit off. This is my output ( part of ) smbstatus -a on the AD-DC. PID Username Group Machine IP Protocol Version Encryption Signing 25843 ADDOM\member-vpn1$ ADDOM\domain computers 192.168.0.2 (ipv4:192.168.0.2:36860) SMB3_11 - AES-128-CMAC 34317 root ADDOM\domain users 192.168.0.5

2017-04-21 0:38 GMT-03:00 Epsilon Minus <theepsilonminus at gmail.com>: > > > I'm desperate. My English is terrible, but I will try to be as clear as possible. > > I have Samba 4.4.4 in a Centos 7. > > I have many connections for each ip. > > The command smbstatus -b returns me infinity of these: > > > Samba version 4.4.4 > PID Username

I seem to have found the solution. But I have not the slightest idea what I have to do Does anyone help me? https://bugzilla.samba.org/show_bug.cgi?id=11472 Thanks! 2017-04-21 1:16 GMT-03:00 Epsilon Minus <theepsilonminus at gmail.com>: > 2017-04-21 1:08 GMT-03:00 Epsilon Minus <theepsilonminus at gmail.com>: >> 2017-04-21 0:38 GMT-03:00 Epsilon Minus <theepsilonminus

I'm desperate. My English is terrible, but I will try to be as clear as possible. I have Samba 4.4.4 in a Centos 7. I have many connections for each ip. The command smbstatus -b returns me infinity of these: Samba version 4.4.4 PID Username Group Machine Protocol Version Encryption Signing

For all Debian 10 people and strange things after upgrade of debian. apt remove apparmor Next debian upgrade use : apt dist-upgrade --no-install-recomends That wont install apparmor. Try that.. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: maandag 11 mei 2020

2017-04-21 1:08 GMT-03:00 Epsilon Minus <theepsilonminus at gmail.com>: > 2017-04-21 0:38 GMT-03:00 Epsilon Minus <theepsilonminus at gmail.com>: >> >> >> I'm desperate. My English is terrible, but I will try to be as clear as possible. >> >> I have Samba 4.4.4 in a Centos 7. >> >> I have many connections for each ip. >> >>

Mason, You can set these also on the share. Win7 and10 client min protocol = SMB2 client max protocol = SMB3 The one for the scanner, client min protocol = NT1 client max protocol = SMB2 Part of my smbstatus -a: PID Username Group Machine Protocol Version Encryption Signing 27316 root root

Sorry, here the conf: # testparm -s Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) Server role: ROLE_ACTIVE_DIRECTORY_DC # Global parameters [global] dns forwarder = 8.8.8.8 ldap server require strong auth = No load printers = No passdb backend = samba_dsdb printcap name = /dev/null realm =

Just to update this, I'm going to upgrade to samba4 but it won't be for a few days yet, I'll keep this thread updated with what happens. On 10 Nov 2017 11:23, "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > No, no idee, but really, upgrade to samba, best option, in my opinion. > If thats not possible, it happens.. > > A timeout option can

On Fri, 2024-04-05 at 19:13 +0100, Rowland Penny via samba wrote: > On Fri, 5 Apr 2024 19:58:33 +0200 > Pavel Lis? <pavel.lisy at gmail.com> wrote: > > > So, > > > > I've done some progress. > > > > I've made configuration according this article > > https://fedoramagazine.org/samba-as-ad-and-domain-controller/ > > they use sample

Louis, Please find the o/p below. Have a question, I read somewhere that using hostname lookups = yes in smb.conf helps with this. Is that correct? We followed the samba wiki to setup the DNS. Hostname: winad01 DNS Domain: addom.com FQDN: winad01.addom.com ipaddress: 10.10.10.10 ----------- Samba is running as an AD DC ----------- Checking file: /etc/os-release