similar to: Oracle 11 nts authentication againts samba4 AD DC

Hi again. I apologize for my vague previous question. After some investigation I can be much more precise in my consult. Furthermore, I think I found a bug... Context: -Samba4 AD DC working fine with many user and machine accouns. -Windows7 client trying to connect via sqlplus to an oracle database residing in a Windows2008 server. Both machines are in the domain. -Server database is using

On 03/03/15 09:56, Izan D?ez S?nchez wrote: > Hi again. I apologize for my vague previous question. After some > investigation I can be much more precise in my consult. Furthermore, I > think I found a bug... > > Context: > -Samba4 AD DC working fine with many user and machine accouns. > -Windows7 client trying to connect via sqlplus to an oracle database > residing in a

Hi guys, about a one or two weeks ago I've updated my samba to v4.1.7 which might or might not relate to the problem at hand. However lately we've seen some issues with users not able to login to workstations (win 7). Windows servers (2008 r2 and newer) were also affected. Sometimes one or two reboots would solve this problems, on few occasions I had to rejoin the computer account to the

Well, in my option, you the have found your problem. https://technet.microsoft.com/en-us/library/cc721940(v=ws.10).aspx 3) ..... After the unique system information is removed, .... And https://blogs.msdn.microsoft.com/aaron_margosis/2009/11/05/machine-sids-and-domain-sids/ Says: Mark?s point is that SIDs must be unique within the authority in which they are used. So while DEMOSYSTEM

Hello to the samba users list again. I've got an emergency here, a Samba AD DC I've got deployed has crashed again, this is the third time since 12/17/2015 that this domain has failed completely. No power outages or unexpected shutdowns, samba simply fails to start, it appears my database is yet again corrupt: [2016/03/02 11:27:17.025235, 0]

schnaggy <schnaggy <at> schnaggy.de> writes: > > > > On 05 Mar 2015, at 10:45, Rowland Penny <rowlandpenny <at> googlemail.com> wrote: > > > > On 03/03/15 09:56, Izan D?ez S?nchez wrote: > >> Hi again. I apologize for my vague previous question. After some investigation I can be much more precise > in my consult. Furthermore, I

On 02/03/16 20:46, IT Admin wrote: > Any further information required? Any troubleshooting steps? I need to > get this domain functional ASAP. > > Please advise. > > JS > On Mar 2, 2016 11:39 AM, "IT Admin" <it at cliffbells.com> wrote: > >> Hello to the samba users list again. I've got an emergency here, a Samba >> AD DC I've got

We have setup Samba 4.1 as a PDC. We have successfully connected several Windows 2008 Servers to the domain and created various users/groups. During an application installation on the Windows server, it runs the command in SQL server: master..xp_logininfo 'MYDOMAIN\useraccount' SQLserver is running as a service user created on the domain (here called MYDOMAIN) This returns: Msg

Thank you Rowland!! Sorry about my ignorance. I guess I tried many different things and polluted the smb.conf file. I've removed every single line you mentioned off my smb.conf. Still the problem persists: MYDOMAIN\Administrator (S-1-5-21-1965676298-842383976-2353361141-500) is changing password of user2 at MYDOMAIN.org.ar [2017/04/21 12:05:42.233899, 3]

Hi again, Am Montag, 14. März 2016, 00:44:47 CET schrieb Markus Dellermann: > Am Donnerstag, 10. März 2016, 10:41:34 CET schrieb mathias dufresne: > Hi, Mathias and all > thank you for your answer. > > > Hi all, > > > > SPN = servicePrincipalName > > > > A simple search returning all servicePrincipalName declared in your AD: > > ldbsearch -H $sam

Hello, After noticing some odd behavior on my domain, I realized that many of my DNS records are incorrect and that clients are no longer properly updating DNS. While looking into this, I also discovered that I am unable to delete MX records via AD DNS Manager or samba-tool. Both tools "see" the record but report it does not exist when I attempt to delete it. I can create new MX

Hi, I had Samba 4.2.14 working as AD DC with shares. After upgrade to version 4.3.11 AD DC authentication, ADUC, etc, stopped working. Shares still work fine. OS. Oracle Linux 6.x with UEK, uptodate. Samba compiled from source. Upgrade procedure (nothing special): ./configure --enable-selftest make make install Testparm output: # Global parameters [global] workgroup = EXAMPLE realm =

On 05/03/15 15:23, Izan D?ezS?nchez wrote: > > > schnaggy <schnaggy <at> schnaggy.de> writes: > >> >>> On 05 Mar 2015, at 10:45, Rowland Penny <rowlandpenny <at> > googlemail.com> wrote: >>> On 03/03/15 09:56, Izan D?ez S?nchez wrote: >>>> Hi again. I apologize for my vague previous question. After some > investigation I

Hi all, I am currently trying to set up a new samba server based on Samba 4.1.6 / CentOS 6.5 / CUPS in a production environment . Everything seems to be ok for AD DC setup . I am now in the step of making the print server running with Point?n?Print . I have followed as close as possible the HowTo : https://wiki.samba.org/index.php/Samba_as_a_print_server Everything is OK until the uploading

Hello all, ? this is my first Post in a Mailing List I hope everything goes fine. ? We are running a Samba 4 DC (4.0.14, Version 4.1.4 has the same problem) as a second DC in our Windows Environment. This server is in a second site. ? So after a while Samba 4 hangs and it is not possible to talk to the server via the RPC Protocol. So all samba-tools Commands like ?samba-tool drs showrepl? run

Dear all, I am testeing the dfs functions with Samba4. In my global section: host msdfs=yes vfs objects = dfs_samba4 Later on setting a dfs root: [dfs] path = /windows/dfs read only = No msdfs root = Yes ls -s the shares in this root. lrwxrwxrwx 1 root root 19 2. Dez 09:29 difaem -> msdfs:linux2\difaem lrwxrwxrwx 1 root root 20 2. Dez 09:29 leitung ->

We have 3 ADCs based on Samba-4.7.4 (compiled from source,internal DNS)/ CentOS7: dcdo1,dcnh1 and dcge1. dcge1 holds all FSMO roles. The 3 ADCs are on different locations connected via IPSec based VPN. No traffic is filtered out. All 3 ADCs replicate fine except dcdo1 -->dcnh1. Symptom: [root at dcdo1 ~]# samba-tool drs replicate dcnh1.ad.kdu.com dcdo1.ad.kdu.com dc=ad,dc=kdu,dc=com

Hello Rowland, Find the _*smb.conf :*_ [global] netbios name = DC4 realm = KTKBANKLTD.COM server role = active directory domain controller workgroup = KTKBANKLTD [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [netlogon] path = /usr/local/samba/var/locks/sysvol/ktkbankltd.com/scripts ??????read only = No *Logs:* {"timestamp":

> On 05 Mar 2015, at 10:45, Rowland Penny <rowlandpenny at googlemail.com> wrote: > > On 03/03/15 09:56, Izan D?ez S?nchez wrote: >> Hi again. I apologize for my vague previous question. After some investigation I can be much more precise in my consult. Furthermore, I think I found a bug? >> ... >> >> User "ids" is requesting a ticket to connect

Good evening, We have been dealing with an incident for several weeks during peak load times, either due to authentications or service accesses that rely on Samba 4 AD. Below are the details of the current Samba version and OS: **Samba version 4.19.2** ```bash ~$ uname -r 5.15.0-41-generic ~$ sudo lsb_release No LSB modules are available. ~$ sudo lsb_release -a No LSB modules are available.