Displaying 20 results from an estimated 3000 matches similar to: "Memory leak samba 4.4.5 and authentications errors"
2016 Aug 18
0
winbind max clients = 2000 ( samba 4.5rc.x) crash problem
samba 4.4..x version no problem.
samba 4.5.rc1 4.5.rc2 4.5.-test all versions problem.
winbind max clients = 2000 line.
server crashes in 1 day.. :(((
my smb file here.
winbindd:use external pipes = true
winbind cache time = 300
winbind reconnect delay = 30
winbind request timeout = 60
winbind max clients = 2000
# winbind max clients = 200
winbind max domain
2016 Jul 12
4
Option configure
Am 12.07.2016 um 23:21 schrieb Reindl Harald:
>
>
> Am 12.07.2016 um 22:55 schrieb Achim Gottinger:
>> Funny current debian service files use a wrong PIDFile path (should be
>> /var/run/amba/samba.pid).
>>
>> If I use Type=forking and an wrong PIDFile systemctl start samba must be
>> CTRL-C'ed.
>>
>> Type=notify works with or without an proper
2017 Dec 19
0
wbinfo quits working on samba AD DC
Hi,
I have a Samba AD domain running 2 self compiled 4.7.3 DC's running on Centos 7.
Every morning if I run wbinfo -u on DC1 I do not get any info back. I have
tried reloading samba but that does not get it working. Restarting samba seems
to be the only way to get it working again.
DC2 continues to work normally.
DC1 holds the FSMO roles and also runs bind DLZ and ISC dhcp configured
per
2017 May 09
0
samba process use 100% cpu
Anybody?
2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta:
> Hi!
>
>
> I need some help.
>
> We use samba4 as AD, and now when clients connect to server, samba
> process stuck at 100% cpu.
>
> samba Version: 4.3.4 Release: 13.el6
>
>
> top:
>
> 3777 root 20 0 131m 46m 28m R 99.7 0.3 219:20.53
> /usr/local/samba4//sbin/samba -D
2016 Aug 30
0
L2tp and winbind - server role active directory domain controller
You funny guy.. ;-)
.. i'll correct..
Winbindd can not run solo on the AD DC, but it does on a member server.
Its started by samba itself on the AD DC..
And dont cheat in the commands.. ;-)
ps fax | egrep "samba|winbind"
27389 ? Ss 0:00 /usr/sbin/samba
27390 ? S 0:00 \_ /usr/sbin/samba
27391 ? S 33:11 \_ /usr/sbin/samba
27393 ? S
2019 Aug 03
0
DNS Update Failed
Hi
I disabled even the windows server firewall to see if this is what it was
blocking, but it didn't solve it.
There appear to be Kerberos key errors, but the kinit administrator command
works correctly.
/usr/sbin/samba_dnsupdate:; TSIG error with server: tsig verify failure
Regards,
M?rcio Bacci
Em sex, 2 de ago de 2019 ?s 15:51, Marcio Demetrio Bacci <
marciobacci at gmail.com>
2017 May 09
0
samba process use 100% cpu
Here is the smb.conf:
https://pastebin.com/LUf4MUF0
Thank you very much.
2017. 05. 09. 18:15 keltezéssel, Dante F. B. Colò via samba írta:
> Did you install it from binary packages ? compiled from source ? Post your smb.conf here.
>
>
> ----- Original Message -----
> From: "samba" <samba at lists.samba.org>
> To: "samba" <samba at
2017 Dec 28
0
2nd samba DC: NT_STATUS_NO_LOGON_SERVERS
Hai Stephan,
You need also this in smb.conf
# enable offline logins
winbind offline logon = yes
I did also test my logins with one DC turned off.
And login on the DM is no problem or my pcs, no problem.
I did not test the AD logins thats because these have only linux logins for maintainance.
And that always works.
In a 2 DC setup, setup your nameservers first to the LAN ip of the
2019 Aug 12
0
Problems joining Samba 4 in the domain
Hi
As described in (
https://wiki.samba.org/index.php/Distribution-specific_Package_Installation)
I haven't installed the follows packages: libpam-winbind libnss-winbind
libpam-krb5
Can this be the problem?
M?rcio Bacci
Em seg, 12 de ago de 2019 ?s 15:42, Marcio Demetrio Bacci <
marciobacci at gmail.com> escreveu:
> Hi,
>
> I have restarted, but it didn't solve the
2016 Jul 13
0
Option configure
Am 12.07.2016 um 23:58 schrieb Achim Gottinger:
> With
>
> Type=notify
> NotifyAccess=all
>
> systemctl status samba-ad-dc
> ● samba-ad-dc.service - Samba AD Daemon
> Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled)
> Active: active (running) since Tue 2016-07-12 23:48:50 CEST; 2s ago
> Docs: man:samba(8)
> man:samba(7)
>
2013 May 14
1
Samba 4 + Zimbra 8
Hello!
I have a setup - Samba 4 for AD functionality and Zimbra 8 for e-mail and collaboration.
Configured in Zimbra that for authentication Samba 4 has to be used.?Basically it works, but now randomly one time in two or three days authentication just stops working.?Nobody?is able to log in to Zimbra e-mail.
Had to restart samba and everything goes as nothing ever happened! :(
Last entry in
2019 Aug 02
2
DNS Update Failed
Hi
I believe I am having DNS upgrade issues, as noticed below:
/etc/init.d/samba-ad-dc status
? samba-ad-dc.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor
preset: enabled)
Active: active (running) since Fri 2019-08-02 10:04:24 -03; 5h 20min ago
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Main PID: 9284
2019 Feb 14
0
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
On Thu, 14 Feb 2019 19:14:19 +0200
Ashley via samba <samba at lists.samba.org> wrote:
> Hi there
>
> I have migrated from an older version of Samba DC to Samba 4.9.4 AD.
> Running Centos 7. One server with everything on... (AD and file
> server) Bind 9.9.4
>
> Built from source.
> Followed directions in the wiki.
> All seems to go fine, but when I startup
2016 Jul 12
0
Option configure
On Tue, Jul 12, 2016 at 5:58 PM, Achim Gottinger <achim at ag-web.biz> wrote:
> With type=forking it shows (8591 is the pid in /var/run/samba/samba.pid)
>
> systemctl status samba-ad-dc
> ● samba-ad-dc.service - Samba AD Daemon
I get this:
=================================================================
# systemctl status samba.service
● samba.service - Samba AD server
2017 Jun 13
2
Problems with Windind Authentication
Hi,
I have a File Server as Domain Member and it was working properly.
Recently I changed my DCs and after I am not getting authenticate users
with winbind.
I'm using Samba 4.6.3 as DC and Samba 4.1.17 as File Server.
When I restart Samba Service, this message appears:
root at dc1:/root# /etc/init.d/samba4 status
● samba4.service - LSB: start Samba4 daemons
Loaded: loaded
2018 Feb 03
0
a quick small howto to get samba 4.7.4 on ubuntu 16.04.
This worked for me until here:
root at dtmbr0tst:~# mkdir sources
root at dtmbr0tst:~# cd sources
root at dtmbr0tst:~/sources# apt-get build-dep samba
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
Suggestions?
On Thu, Feb 1, 2018 at 7:04 AM, L.P.H. van Belle via samba <
samba at lists.samba.org> wrote:
> Hai,
>
> I've had a
2019 Feb 14
0
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
On Thu, 14 Feb 2019 21:43:43 +0200
Ashley via samba <samba at lists.samba.org> wrote:
>
> On 2019/02/14 21:12, Rowland Penny via samba wrote:
> > On Thu, 14 Feb 2019 19:14:19 +0200
> > Ashley via samba <samba at lists.samba.org> wrote:
> >
> >> Hi there
> >>
> >> I have migrated from an older version of Samba DC to Samba 4.9.4
>
2018 Jan 22
0
SAMBA 4.7.4 with MIT Keberos
There is a script in /etc/init.d/krb5-kdc". Do i need remove this? Because this is trying to start automatic krb5kdc at reboot.
Output from pstree and ps:
# pstree | grep samba
|-3*[samba]
|-samba-+-samba---samba---smbd-+-cleanupd
| |-10*[samba]
| |-samba---samba---krb5kdc
| `-samba---samba---winbindd---winbindd
# ps axf
2129 ? Ss 0:00 samba
2130 ? S 0:00 \_ samba
2132 ? S 0:00 | \_ samba
2019 Jul 19
2
Samba4 - global catalog (GC) cannot be contacted using Windows 7 RSAT
Hi Samba Team,
Have recently followed Samba guide and successfully migrate from PDC to AD
and from BDC to join AD forest.
Need some advice here as I encountered global catalog (GC) cannot be
contacted issue when using RSAT.
This message pops up when I click "member of" tab while viewing user
properties although it will display correctly after I acknowledged the
error.
Another similar
2016 Aug 22
1
RPC server is unavailable when using ADUC
Hello.
We're running Samba 4.3.9 AD on two Ubuntu 16.04 LTS machines. I'm managing
AD users and DNS from Windows 10 joined to the domain, by using ADUC.
Last week I noticed the following error when starting ADUC as Administrator
of the AD domain:
----
Naming information cannot be located because:
The RPC server is unavailable.
Contact your system administrator to verify that your domain