similar to: rpc_pipe_open_ncalrpc: connect(/run/samba/ncalrpc/EPMAPPER) failed: No such file or directory

02.10.2023 15:22, Norbert Hanke via samba: > on two of my DCs: > > > samba -V > Version 4.17.10-Debian > > file /run/samba/ncalrpc/EPMAPPER > /run/samba/ncalrpc/EPMAPPER: socket Yes, this socket does exist on a DC. It is being listened by "samba: task[rpc] pre-forked worker(0)". It does not exist on a member server, where I observe these log messages. Here,

On 31/01/2023 06:59, Peter Milesson via samba wrote: > Hi folks, > > The smb.conf and other information after specification of the problems. > > The journal on a AD domain member server is cluttered with permission > denied entries of this message pair: > > ?? Jan 31 07:02:26 konsrvfast smbd[436004]: [2023/01/31 > ?? 07:02:26.083500,? 0, effective(11025, 10515),

Hi folks, The smb.conf and other information after specification of the problems. The journal on a AD domain member server is cluttered with permission denied entries of this message pair: Jan 31 07:02:26 konsrvfast smbd[436004]: [2023/01/31 07:02:26.083500,? 0, effective(11025, 10515), real(11025, 0)] ../../source3/smbd/smb2_service.c:168(chdir_current_service) Jan 31

In my never-ending quest of removing clutter from the log files, I notice that we in /var/log/messages get a lot of: > Jul 25 13:08:30 filur00 winbindd[88603]: [2023/07/25 13:08:30.756462, 1] ../../source3/winbindd/winbindd_lookupname.c:122(winbindd_lookupname_recv) > Jul 25 13:08:30 filur00 winbindd[88603]: Could not convert SID S-0-0, error is NT_STATUS_NONE_MAPPED Seems to happen

Rowland penny via samba ha scritto il 27/08/20 alle 16:43: > [...] > Netbios is intrinsically tied to SMBv1 and? LLMNR (Link-Local Multicast > Name Resolution) is also connected in a way, it allows name resolutions > without a nameserver. So, if you are using it, I personally wouldn't, > ever heard of MITM ? Just to understand a little more... NetBIOS with a wins server

Hi All, I've samba (4.11.2) on centos 8 connected to IPA. All works as expected but I see these errors in log: Aug 28 09:12:02 satan8 smbd[889]: [2020/08/28 09:12:02.656514, 0, pid=889] ../../source3/rpc_client/cli_pipe.c:2937(rpc_pipe_open_ncalrpc) Aug 28 09:12:02 satan8 smbd[889]: connect(/run/samba/ncalrpc/EPMAPPER) failed: No such file or directory Aug 28 09:12:02 satan8 smbd[889]:

I am installing a new Samba 4.2 Active Directory server on CentOS 7. I followed the Wiki instructions on how to create the server. I am using sernet-samba 4.2 binaries. Everything seems to be OK on the Linux side but I cannot get any windows client to successfully join the domain. Each attempt returns the following error message "RPC Server in not available". Below are the config file

I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10 client to the Samba domain without any issues. The

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Hello all, I've googled this but couldn't find anything relevant and the list's archives didn't turn anything either, so pretty please someone take a look at this if you can spare a moment. My Samba server shares its CUPS printer, but Windows clients cannot print to it (I haven't tried other CIFS clients). I have the point-n-print driver all set up, so the Windows XP Pro

Hi guys I have setup a NT4 Domain, using Freeipa as a ipasam backend... Normal user authentication and shares seems to work, but i'm getting an error when trying to join a Windows 7 machine to the domain (see below)... To me it seems to be the same error as here: https://bugzilla.samba.org/show_bug.cgi?id=11245.... Does anyone know if this patch have been implemented in the samba in

Am 28.03.23 um 10:40 schrieb Rowland Penny via samba: > > > On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: >> Hello >> >> >> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using >> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository >> >> >> everything is running fine but i have few log files in /var/log/samba/

Release Announcements ===================== This is the second release candidate of Samba 4.16.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.16 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the second release candidate of Samba 4.16.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.16 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Hello. I'm gradually replacing my 4.17 installations with 4.19 (on FreeBSD). As soon as I do this, I'm starting to see gobs of messages in the log like the followings: rpcd_lsad[54129]: rpcd_lsad version 4.19.5 started. samba-dcerpcd[14381]: samba-dcerpcd version 4.19.5 started. I actually experience no troubles (so far) and there are no error messages actually, but is this

AD DC default shares are okay after provisioning - smbclient -L localhost -U%: Domain=[CONPAGO] OS=[Unix] Server=[Samba 4.1.17-SerNet-RedHat-11.el7] Sharename Type Comment --------- ---- ------- netlogon Disk sysvol Disk IPC$ IPC IPC Service (Samba 4.1.17-SerNet-RedHat-11.el7) Domain=[CONPAGO]

On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: > Hello > > > i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using > www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository > > > everything is running fine but i have few log files in /var/log/samba/ > are not handl by /etc/logrotate.d/samba > > log.samba-dcerpcd > >

Hello i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository everything is running fine but i have few log files in /var/log/samba/ are not handl by /etc/logrotate.d/samba log.samba-dcerpcd log.rpcd_classic log.rpcd_winreg log.samba-bgqd log.rpcd_spoolss i guess those files size will not grow more than max log

Release Announcements --------------------- This is the first stable release of the Samba 4.16 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== New samba-dcerpcd binary to provide DCERPC in the member server setup --------------------------------------------------------------------- In order to make it much easier to break out

Release Announcements --------------------- This is the first stable release of the Samba 4.16 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== New samba-dcerpcd binary to provide DCERPC in the member server setup --------------------------------------------------------------------- In order to make it much easier to break out