similar to: Cannot contact any KDC for realm

If this is a new setup. And if this reflex your primary dns domain for your AD-DC. realm = EXAMPLE.COM Then i hope your really good with DNS setups, to easy to make errors here. Cannot contact any KDC for realm can be one of them. My advice use something like : realm = INTERNAL.EXAMPLE.COM Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Hi Rowland, Sorry I missed out on the OS. CentOS Linux release 7.6.1810 (Core) smb.conf # Global parameters [global] bind interfaces only = Yes interfaces = lo ens192 netbios name = SERVER1 realm = EXAMPLE.COM server role = active directory domain controller workgroup = WORKGROUP idmap_ldb:use rfc2307 = yes ldap server require

On 12/08/2020 02:28, Alfonso Conner via samba wrote: > Hello Samba Community, > > I would like to seek advice as my Samba AD tends to consume high memory > usage caused by KDC service. > This issue will always come back within a couple of days after I restart > samba-ad-dc service. > It does not help by increasing memory. > > From message log: > kernel: Out of

> It looks like you have built Samba yourself, Yes. I followed the guide and built Samba myself. > so did you run this script: https://git.samba.org/?p=samba.git;a=blob_plain;f=bootstrap/generated-dists/centos7/bootstrap.sh;hb=master >Before you built Samba ? No. I was not aware of this step. >Have you installed and started 'krb5-server' ? No. I have checked and only

Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: > On Wed, 18 Jul 2018 13:49:39 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > > Hmm, your REALM is 'SMBDOMAIN.FILE.DUCK' but your dnsdomain appears to > be just 'duck' > > Rowland > I read https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ - but I am not sure that my

Hi Rowland, Noted with thanks. Regards On Mon, Jul 22, 2019 at 4:31 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 22/07/2019 09:23, Alfonso Conner wrote: > > Hi Rowland, > > > > In fact currently in my test environment using the same version of OS > > 6.10 and Samba 4.8.5. > > I ran 'netstat -plaunt | egrep

Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > On Wed, 18 Jul 2018 23:21:41 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: >> > It is touched on here: > > https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Parameter_Explanation >

Hi Rowland, Currently using Samba 4.8.5 2 x DCs running on CentOS 6.10 (Final) Configured 1 DC via classic upgrade, and the latter DC join AD forest. Would it be alright if I were to redo the classic upgrade? Hope to hear from you soon. Thanks and Regards On Fri, Jul 19, 2019 at 7:06 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 19/07/2019 11:13, Alfonso Conner

Hi Rowland, In fact currently in my test environment using the same version of OS 6.10 and Samba 4.8.5. I ran 'netstat -plaunt | egrep "ntp|bind|named|samba|?mbd"', I have :::3268, :::3269, I do not see 0.0.0.0:3268 and 0.0.0.03269. While I use a Windows PC join to my test domain, I have no issues with GC. Not sure how the GC problem can happen but seems to me it looks like a

On Thu, 19 Jul 2018 17:33:46 +0200 Anton Blau via samba <samba at lists.samba.org> wrote: > Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > > On Wed, 18 Jul 2018 23:21:41 +0200 > > Anton Blau via samba <samba at lists.samba.org> wrote: > > > >> Am 18.07.2018 um 14:17 schrieb Rowland Penny via samba: > >> > > It is touched on here:

On 22/07/2019 10:24, Alfonso Conner wrote: > Hi Rowland, > > Just a curious question. > Since the origin of my AD comes from PDC. If I were to try and do a > classicupgrade, using same IP, same hostname, same realm, will my > windows pc have login issues? > To be honest, I am not entirely sure, you should get the same results every time you run the classicupgrade, so your

Hi, Thanks for the advice, I know these are already EOL but please bear with me on that. I also do use CentOS 7 and Windows 10 for further testing. Anyway, I found out is due to my "idmap DOMAIN : range" value in smb.conf was not set to the correct range. Another thing is libnss-winbind package must make sure to be installed properly. After these things are resolved, I managed to see

Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > On Thu, 19 Jul 2018 17:33:46 +0200 > Anton Blau via samba <samba at lists.samba.org> wrote: > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: >>> On Wed, 18 Jul 2018 23:21:41 +0200 >>> Anton Blau via samba <samba at lists.samba.org> wrote: >>> >>>> Am 18.07.2018 um

On Mon, 23 Jul 2018 23:09:58 +0200 Anton Blau via samba <samba at lists.samba.org> wrote: > Am 19.07.2018 um 17:50 schrieb Rowland Penny via samba: > > On Thu, 19 Jul 2018 17:33:46 +0200 > > Anton Blau via samba <samba at lists.samba.org> wrote: > > > >> Am 19.07.2018 um 10:03 schrieb Rowland Penny via samba: > >>> On Wed, 18 Jul 2018 23:21:41

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

Hai, Now this part. > On my Linux machines, currently all is done manually by local > user account > creation and by adding the command lines into individual home > directory > ~/.bash_profile I dont know your system, but on my debian im adding things like that in /etc/profile.d/ Now its for every user, put your scripts in there, give "domain users" a GID. Make a

Hi, Thank you for replying. User home directory creation is working without the need to edit /etc/pam.d/common-session The logon script I mentioned here is a in-house script to handle directory mounting for file server access, and create shortcut on the account desktop for different logins. On my Linux machines, currently all is done manually by local user account creation and by adding the

We have two Samba AD-DC. One is version 4.5.12 (debian) and 4.5.11 (ubuntu). On both, the rpc_server is using one core to the max 99-100% all the time. I see the PID by samba-tool processes and I see something like dnsupdate 19526 cldap_server 19520 rpc_server 19515 rpc_server 19515 rpc_server 19515 rpc_server 19515

I am in the process of trying to setup a Samba 4.0.6 AD DC on Fedora 18, but dnsupdate is not updating the DNS records since I changed the addresses that I have assigned to my NICs. At first I thought the internal server didn't want to work, so I tried getting things setup with Bind (which is working just not with Samba yet). I am wanting to replace our Windows Server 2003 with RHEL 7 (or

I had freshly installed an Ubuntu Server 12.04lts and Samba 4.0.1 using the internal DNS. I followed the official HowTo until "kinit administrator at DOMAIN.LOCAL" It didn't work (cannot contact any kdc...) A "netstat" showed that "avahi-daemon" was running at: 807/avahi-daemon: r udp 0 0 10.0.0.20:389 0.0.0.0:* After removing that package