search for: domainaccounts

Hi experts, I have a Samba4/AD scenario which is driving me crazy. On some servers, I have the same volume mounted on /share. I am using some different servers as gateways to export this content using HTTP, NFS, FTP and CIFS. AD authentication is a must. On the Linux machine where Samba is running, I have joined it to the domain using PBIS (domainjoin-cli join [DomainName [DomainAccount]).

Hi all ! I'm using Samba 2.2.3a on a Redhat Linux 7.2 as a Primary Domain Controller ! My users are mostly use win2000 and the profile directory can be really large after some month, so in this case I need a lot of Extra storage to store them on the PDC ! We don't need this feature basically, so is it possible somehow to switch of this feature ? Best Regards ! Viktor Posta

Hello, I have been running Samba4 on a Ubuntu 12.10 for a few months. Using this setup script, I have also been using PBIS (Open-wise 7.1) to connect Linux clients to it. I have has this setup for serveral months. Now if I connect to a windows computer I get access denied and it still works on linux via PBIS. If I login to the windows computer with a local account, I can

On 11/11/2020 02:40, Andr? Aun via samba wrote: > Hi experts, > > I have a Samba4/AD scenario which is driving me crazy. > > On some servers, I have the same volume mounted on /share. I am using some > different servers as gateways to export this content using HTTP, NFS, FTP > and CIFS. AD authentication is a must. > > On the Linux machine where Samba is running, I have

I have a mostly working set of modules to replace our kickstart and about a dozen scripts. I am having issues with attempting to populate my AD account-owned user folders in the initial puppet run. The machines i am testing with are all CentOS 5.5 so far. I have defined 3 additional stages, Stage [init] -> Stage [pre] -> Stage [main] -> Stage [post] to attempt to fix this to no avail.

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

On 2015-05-20 09:21, Timo Altun wrote: > Hi Davor, > > most of the domain accounts were part of an old NT4 domain. I did a > classicupgrade. > > Your theory with the NTUSER.DAT-files seemed so promising, > unfortunately that was not it. I created new accounts on an XP machine > and a Win7 machine and tried to join with them, but still receive the > same error. One of

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain