similar to: 2nd samba DC: NT_STATUS_NO_LOGON_SERVERS

Displaying 20 results from an estimated 8000 matches similar to: "2nd samba DC: NT_STATUS_NO_LOGON_SERVERS"

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
2017 Dec 28
1
2nd samba DC: NT_STATUS_NO_LOGON_SERVERS
Am 2017-12-28 um 15:55 schrieb L.P.H. van Belle via samba: > Hai Stephan, > > You need also this in smb.conf > > # enable offline logins > winbind offline logon = yes On which server(s)? The DCs? the DM? > 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
2018 May 17
2
DNS entry for resolving the DC
We already "solved" this by using the long form of the domain name, but I want to learn if we should do something additional: We had a mixed setup in the field, some PCs had a WINS server configured, some not. We removed the WINS info from DHCP and saw no new problems (we wanted to have things the same way on all clients). Yesterday the local admin tried to join a new PC and entered
2016 Dec 30
2
ADS domain member: winbind fails
And in addition to Rowlands comments.. Correct you hosts file to /etc/hosts 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # This server name and ip. 10.0.0.221 main.arbeitsgruppe.secret.tld main 10.0.0.224 backup.arbeitsgruppe.secret.tld backup Second. Post you
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
2016 Dec 30
7
ADS domain member: winbind fails
On Fri, 30 Dec 2016 13:54:42 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-12-30 um 13:20 schrieb L.P.H. van Belle via samba: > > And in addition to Rowlands comments.. > > > > Correct you hosts file to > > /etc/hosts > > 127.0.0.1 localhost > > # The following lines are desirable for IPv6 capable
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
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
2016 Dec 30
2
ADS domain member: winbind fails
Am 2016-12-30 um 12:10 schrieb Rowland Penny via samba: > Was Samba running before the join ? I can't tell that anymore as I did hundreds of things inbetween. > Remove this line from your smb.conf: > > idmap config ARBEITSGRUPPE:schema_mode = rfc2307 > > It is not required as you are using the winbind 'rid' backend. "rid" was just a try as "ad"
2017 May 02
2
samba process use 100% cpu
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 24541 csertam 20 0 49260 11m 9048 S 25.1 0.1 0:01.56 smbd -D 7080 squid 20 0 926m 908m 6428 S 9.9 6.2 11:43.50
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
2017 May 09
2
samba process use 100% cpu
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 lists.samba.org> Sent: Tuesday, May 9, 2017 1:01:10 PM Subject: Re: [Samba] samba process use 100% cpu Anybody? 2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta: > Hi!
2014 Nov 11
1
smbd changeling and strange firewall logs
I found in my firewall logs something that looked somewhat like a port scan originating from my AD DC. So I started to check the machine and already found something strange using ps aux: root at samba:/# samba -V Version 4.1.11-Debian root at samba:/# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND [...] root 10675 0.0 2.8 457368 29620 ? S Nov04
2019 Feb 14
2
Migrating to Samba 4.9.4 AD, kinit administrator -> kinit: Cannot contact any KDC for realm...
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 samba-ad-dc it shows a few errors.    ([kdc failed to setup interfaces]) The initial tests (in the directions in wiki) go fine until I get to 
2016 Jul 13
2
Option configure
Am 13.07.2016 um 12:09 schrieb Reindl Harald: > > > 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 Dec 30
3
ADS domain member: winbind fails
On Fri, 30 Dec 2016 14:26:01 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-12-30 um 14:07 schrieb Rowland Penny via samba: > > Is this the smb.conf you got when you ran the classicupgrade ? > > I don't think it is, can I suggest you remove any and all lines you > > have added and restart samba > > that was the
2018 Feb 01
2
a quick small howto to get samba 4.7.4 on ubuntu 16.04.
Hai,   I've had a few min left in my lunch so ...   This is a quick setup for samba 4.7.4, tested on Ubuntu 16.04 LTS, should work on Ubuntu 17.10 also, .. UIuntu 17.04 is unmaintaint so upgrade to 17.10 or stay at 16.04.   Do a nUbuntu server minimal install. No dhcp ip, setup static ip.     # Setup apt. echo "deb http://apt.van-belle.nl/debian unstable main contrib non-free" |
2019 Aug 12
3
Problems joining Samba 4 in the domain
Hi, I have restarted, but it didn't solve the problem. /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 Mon 2019-08-12 15:32:18 -03; 9s ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Main PID: 575 (samba)
2019 Aug 11
2
Bind9 doesn't updated - TSIG error with server: tsig verify failure
Hi Rowland, I've added 'dns update command' on global section of smb.conf file and I've configured namesever on '/etc/resolv.conf' as 127.0.0.1 (I've tried with 'kings' IP address too), but I don't know if this has worked. I've seen some dns updates errors on 'systemctl status samba-ad-dc' though the same command has returned status 'Active