similar to: Users can login current and one previous password

On Tue, 26 Dec 2023 14:28:00 +0530 Anantha Raghava via samba <samba at lists.samba.org> wrote: > Hi, > > We are running Samba-AD version 4.18.1 and are observing a peculiar > behaviour. > > Our environment contains 5 AD Domain Controllers. Users are able to > login to AD domain with "Current" and one "Previous" password. That > is, if I change

Hi, Can we change this behaviour? Thanks & Regards, Anantha Raghava On 26/12/23 2:56 pm, Rowland Penny via samba wrote: > On Tue, 26 Dec 2023 14:28:00 +0530 > Anantha Raghava via samba<samba at lists.samba.org> wrote: > >> Hi, >> >> We are running Samba-AD version 4.18.1 and are observing a peculiar >> behaviour. >> >> Our environment

Hi, In samba logs I see these entries. {"timestamp": "2024-03-22T17:00:13.553400+0530", "type": "Authentication", "Authentication": {"version": {"major": 1, "minor": 2}, "eventId": 4624, "logonId": "d42e868adc3300ef", "logonType": 3, "status":

Hello Marc, Upgrade DNS worked properly as you can see below. --------- samba_upgradedns --dns-backend=BIND9_DLZ Reading domain information DNS accounts already exist No zone file /usr/local/samba/private/dns/EXZA.LOCAL.zone # is this the culprit? DNS records will be automatically created DNS partitions already exist dns-dc account already exists See

Hello.. We have samba-ad version 4.18.1 running in our environment. We use static IP in our environment for all workstations and serves. Samba is installed on RHEL 8. Off late, we have been observing that, when we try to access any network shared resource using their IP address, we get the error "\\x.x.x.x is not accessible. You might not have permission to use this resource. Contact

Hi, We provide DC Host's IP address and port as 3268 and user DN of administrator as CN=Administrator,CN=Users,DC=ktkbank,DC=com and supply password. But proxy reports "unable to connect to directory". However, the Proxy's Content Gateway is a member of AD DC and it uses integrated windows authentication. -- Thanks & Regards, Anantha Raghava DISCLAIMER: This

Hello Andrew, A gentle reminder for the patch. Can you share the patch as you mentioned? -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees. On 29/10/17 11:57 AM, Andrew Bartlett wrote: > On Sun, 2017-10-29 at 09:11 +0530, Anantha Raghava wrote: >> Hi, >> >> I did upgrade the server to Windows Server 2008 R2

On 8/04/23 14:13, Anantha Raghava via samba wrote: > Hello, > > Just yesterday, we installed the new samba version - 4.18.1 - and configured AD > domain controllers. Samba service started without any issues. But with in 10 > minutes of starting the service entered failed state. Restarting the service is > also resulting in the same issue. Service enters failed state with in

Hello Rowland, ldap search command throws error as below. I am unable to search ldap. ------- ldap_initialize( ldap://dc.exza.local:3268 ) ldap_start_tls: Can't contact LDAP server (-1) Enter LDAP Password: ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) ---------- I am using BIND_DLZ dns back end. and server is listening on 3268 and 3269 -- Thanks & Regards, Anantha

Hello Rowland, ldbsearch command is returning 0 records. # returned 0 records # 0 entries # 0 referrals On the backup front, I take the back up using samba-tool backup command and it was successful. Can I create a new ForestZone using samba-tool? I asking this question as RSAT is not connecting to DNS server. Thanks & Regards, Anantha Raghava H A This e-mail communication and any

Hi, Although Samba is listening on port 3268, proxy returns error "unable to connect" Any suggestions to fix this? -- Thanks & Regards, Anantha Raghava DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology Consulting & Services, and are intended only for the use of the recipients named above If you are not the

Hi, After upgrading to BIND9_DLZ, BIND service is properly starting. However, DNS updates are failing. When I try to force the DNS update, I get the following error. Even kinit command returns "kinit: Cannot find KDC for realm "EXZA.LOCAL" while getting initial credentials" --------------------------------------- [root at dc ~]# samba_dnsupdate --verbose --all-names IPs:

Hi, Setting up a test environment for 4.19 rc2. However, can't we raise the lowest functional level higher than 2008 R2 in 4.18.x? Thanks & Regards, Anantha Raghava H A DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to Exzatech Consulting And Services Pvt. Ltd., Bangalore, and are intended only for the use of the recipients named above

Hello Rowland, 1. We always have been using self compiled samba not the binaries. In fact, when we started we started on CentOS and then when CentOS became an upstream edition, we moved to RHEL, but continued with self compiled samba, never moved to prebuilt binaries. 2. SSSD - We are not using sssd anywhere. We have many Linux Servers but those are not members of AD domain. Only the web

Hi, Let me just check this and revert back. -- Thanks & Regards, Anantha Raghava DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology Consulting & Services, and are intended only for the use of the recipients named above If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have

Hello Andrew & Louis, Yesterday by around 1:30 PM we had the same issue. Samba AD kicked all of us out and RSAT did not connect to any domain controllers. /*Incidentally the RSAT that caused this error was running on Windows 7 Professional 64 Bit edition.*/ When I restarted the samba-ad-dc service, all started working well again. However, as mentioned again, I could not trace the error

Hi, String of peculiar behavior continues... Samba Version 4.7.5, Bind Version 9.8 No. of Samba-AD-DC Servers : 4 (dc1, dc2, dc3 & dc4). All FSMO roles are on dc1. All the while all things were perfect. Yesterday, due to some reason, the BIND Service on dc2 stopped. This resulted in none of the other domain controllers could resolve the names. On dc2, only named service was stopped but

Hello, We are observing on some domain members we are observing, when we open the user or group's properties, we are not seeing either the real user names (Member Names) or group names instead only SIDs are shown. Not able to figure out where the issue is. Your guidance is highly appreciated. Our Samba AD version 4.18.1 -- Thanks & Regards, Anantha Raghava H A DISCLAIMER: This

Hi, We were running Samba-AD - Version 4.7.6 for over 2 years without any errors. We have 4 Domain Controllers in our setup and DNS is BIND_DLZ (BIND 9.9.4). Off late (since 8th June 2019) we upgraded the Samba-AD version to 4.10.4 and all of sudden we started receiving the error "RPC Server not available" when we are trying to join the new PCs to domain. After multiple attempts

Hello.. Can we promote the Samba AD DC (Version 4.6) to be a global catalogue server? We need to integrate Websense Proxy with this and Proxy server searches Global Catalogue on Port 3268. -- Thanks & Regards, Anantha Raghava eXzaTech Consulting And Services Pvt. Ltd. DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to eXza Technology