similar to: Trust relationship between workstation & server

Hi, Yes, we have 4 DCs & the Replication is the issue. It is taking time. But have no clue as to how to fix it. Suggestions are welcome. -- Thanks & Regards, Anantha Raghava Do not print this e-mail unless required. Save Paper & trees. On 04/04/18 10:31 PM, lingpanda101 wrote: > On 4/4/2018 12:50 PM, Anantha Raghava via samba wrote: >> Hi, >> >> On Windows

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

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 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

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

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, Can we export the samba audit logs (Authentication & Authorisation Logs) to Windows Event Viewer? I am trying to export the authentication & authorisation logs to a Windows Server to be shown in Windows Event Viewer. I read the link - https://wiki.samba.org/index.php/Event_Logging. But couldn't follow much. Can someone throw more light on the procedure, if it is possible? --

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 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 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, 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:

Now, its getting more detailed for the samba devs and more out of my scope.   But a small last question from me. Are you moving OU's with users and are there GPO's liked to these OU's? If yes, detach the GPO link and try moving without GPO's attached.   Still errors? Are these users logged in or not? If still logged in, try an OU without users logged in.     I also did read

Hello Rowland, > On Sat, 30 Jun 2018 14:51:48 +0530 > Anantha Raghava via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> We have been using Samba File Server (Version 4.3.11 Ubuntu 14.04 >> LTS) for quite sometime now. We recently installed Samba-AD (Samba AD >> Version 4.7.6) and made the file server a member of the Domain. >> Everything

Dear all, will it be possible to upgrade/update an existing samba 4.17.10 domain to samba 4.19 ? What are the points to pay attention to!? Greetings Daniel

> On Sat, 30 Jun 2018 21:09:07 +0530 > Anantha Raghava via samba <samba at lists.samba.org> wrote: > >> Hello Rowland, >>> On Sat, 30 Jun 2018 14:51:48 +0530 >>> Anantha Raghava via samba <samba at lists.samba.org> wrote: >>> >>>> Hi, >>>> >>>> We have been using Samba File Server (Version 4.3.11 Ubuntu 14.04

Hi Anantha, > The upgrade from 4.6.5 broke all the servers. Although the services were > running and there is no error message, DNS resolution failed. Even from > inside the domain controllers, DNS queries failed. > > Samba Version 4.7.1 and Named Version 9.9.4. The same issue happened > with samba version 4.7.3 and 4.7.4 > > We had to revert back to 4.6.5 to bring the

Hello Samba List, I have a desktop with a clean full install of Windows 10 Pro 1709. I have an entry in the Samba 4.7 AD for the machine account (from when it was Windows 7 Pro). Windows 10 appears to join the Domain successfully. When I try to log in with the DOMAIN\Administrator account I get the Windows error:- "The security database on the server does not have a computer account for

hi all i still struggling for the last 2 month to figure out what happen with my samba 4 AD server Installation almost all my client mostly win 7 and 10 having same problem with trust relationship i have check the time on PC client all fine ..but the trust relationship problem still happen here is my samba server conf *# Global parameters[global]

Hai, Was this pc a member of any NT4 Domain in the past? You can try the following. Login as a Local Administrator on the pc. ( you may need to create one first. ) Open PowerShell as administrator ( you need powershell 3.0 for this ) Run: Reset-ComputerMachinePassword -Server AD_DC.DOMAIN.TLD -Credential YOUR_AD_DOM\Adminstrator Restart-Computer No powershell V3. netdom.exe resetpwd

Hai, Im joining this one if you dont mind. My setup: Debian 8 (Jessie) ADDC's : samba 4.6.6 Member with profiles : samba 4.6.6 This problem is here seen also on a Windows7 Pro 64bit client. The client here, is related to the user profile, this one is having a corrupted user profile in my case. Due to this, my GPO fails and i see event id: 4098 , error code : 0x8007000E insufficions