similar to: sysvolcheck and aclcheck generates error

Hi all, Can somebody give insights on this issue with the one-way interdomain trust. It seems the trust working as I can get the users of the trusted domain (SANDBOX) from the trusting domain (LUMAD) Current Configurations: Windows 2016 Standard (SANDBOX) - Active Directory functional level (Windows Server 2008 R2) Samba 4.7.5 (LUMAD) samba-tool domain level show Domain and forest function

Hi, I'm doing Samba PDC (named as LUMAD, 192.168.2.154 on Fedora 27) using samba 4.7.4 with Windows 2016 AD (named as SANDBOX, ip 192.168.2.144) as the trusted domain, but there's some issue with it. I *can't login *using Windows AD credentials but on the *Samba PDC account works well *on Windows 7 as initial test and it's mimicking with our production server. I used to classic

George, I have the detailed log below. (Resending after trimming the email to 40KB.) The sequence below just repeats ad-nauseam. Is this a SIP trunk issue? Thanks! --------------------- Transmitting SIP request (885 bytes) to UDP:65.254.44.194:5060 ---> INVITE sip:12025551212 at 65.254.44.194:5060 SIP/2.0 Via: SIP/2.0/UDP 18.18.19.123:5060

On Sun, Mar 15, 2015 at 5:56 PM, Sonny Rajagopalan <sonny.rajagopalan at gmail.com> wrote: > George, > > I have the detailed log below. (Resending after trimming the email to 40KB.) > > The sequence below just repeats ad-nauseam. Is this a SIP trunk issue? > > Thanks! > I don't see anything obvious. The registration works though, right? You might want to compare

Hello, I was hoping to reprovision the same domain by specifying the domain GUID in the command line tool 'samba-tool domain provision' but I am not sure if I missed something or if there is a bug but the specified domain GUID is not the one which is created for my domain. Specifying the domain SID seems to work as I would expect. I tested it with Samba shipped by Debian 11 (samba2

Hi, Hope can someone give insights or what to do next, regarding with issue encountered regarding with the upgrade of Samba3 to Samba4 NT4-style domain with OpenLDAP backend. It seems the upgrade went well as I could join the domain on the Windows 7 workstations, except adding still the registry mentioned on the link: https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains and

I'm trying to upgrade from samba3 -> 4. I ran this command: WORKDIR=/usr/local/mobius /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=$WORKDIR/var --use-xattrs=yes --realm=infinityhealthcare.com $WORKDIR/smb.conf but it failed with the error given in this email's subject. What does it mean, and how do I fix it? This is just another is a growing line of errors that

I recently ran into a problem accessing Samba shares from SFU. From SFU's /net directory, I could read from files, move files, create directories and even append to files using >>. But, when I tried to create a file, I received a "Permission Denied" message. After looking at the logs I found something which looked out of place. I am currently using (I tried many different

ClassicUpgrade of my samba3 data to samba4 fails, with this error: ERROR(<class 'passdb.error'>): uncaught exception - Unable to get id for sid Full log of the classicupgrade is at the end of this email. Project member on this list, Andrew Barlett, wrote that the issue is probably that my Samba 3 passdb was passable in an NT 4 DC mode, but is actually 'invalid' :

Whenever I try to add or remove a user for access to a file I get the following error: "Unable to save permission change on <filename>. Access is denied". I took a look at my smbd log file and found this: [2002/08/29 10:40:00, 5] smbd/posix_acls.c:unpack_nt_owners(433) unpack_nt_owners: validating owner_sids. [2002/08/29 10:40:00, 5] smbd/posix_acls.c:unpack_nt_owners(474)

Hi, I've a question about a problem using a samba share in a UNIX AIX server. In my scenarious there is a fileNET server (running on a win2000 server) which use a samba share on a AIX sever for cacheing file, this share is configured for allow access to a particular user (pangol). It seams that user have access permission but an error is returned when fileNET try to write a file. Thanks in

I am running Samba 2.2.3a on Solaris 8 with NT4 and windows 2000 clients (both NT4 and w2k have the same problem). I have a situation where by I have a windows NT application installed onto the samba share. When i try to start the application it crashes with an error complaining that it is unable to read a file. The debug log shows the following with relation to the file

On Thu, 2017-10-26 at 11:38 +0200, mj via samba wrote: > Hi, > > I joined a new samba-4.7 DC to our AD, replicated everything over, then > turned off the old DCs, seized fsmo roles, and added two extra 4.7 DCs. > > Everything above succeeded without warnings, and everything seems to be > running very well finally, except for the sysvolcheck / sysvolreset. > >

Hi list, I'd like to raise the issue discussed in the thread below. I've faced exactly the same problem and came to exactly the same way out - shutdown winbindd and use "force unknown acl user". We use "simple" mapping in the environment - all AD accounts have corresponding NIS accounts (the same name) and the mapping is being done by smbd. The problem here is that

Hi all, I have a 2.2.7a member server (on Debian unstable), acting as a file server for a W2k domain (which also has some NT4 clients, ie. mixed mode). I'm also using ACLs. Imagine I have a file on the server with an ownership of DOMAIN+foo (full permission - rwx). I also have a user ACL on that file of DOMAIN+bar, also rwx. This all works fine. I was initially running into a problem

Hi all I'm having some problems trying to configure ACLs from a Win2000 SP3 client. I'm running Samba 2.2.5 on kernel 2.4.18 (with acl + ext attr), Samba is compiled with acl support etc. Samba is configured with security=domain, and is running with local groups etc rather than thru winbind, I haven't been game enough to tread those waters yet. With the debug level set to 5

Hello! Any idea ? Regards Em 31-05-2017 12:00, Carlos A. P. Cunha escreveu: > > Hi > > My configuration: > > smb.conf > > # Global parameters > [global] > workgroup = MYSERVER > realm = interno.mydomain.com.br > netbios name = DC-LINUX > server role = active directory domain controller > server services = s3fs,

I have been using samba 2.0.X for over a year with solaris 2.6 and windows NT4. I have a windows application installed onto a Unix share which is mapped to the NT clients using samba. Everything has worked perfectly with the windows application untill i reciently tried upgrading to a 2.2.X version of Samba. ( I have tried 2.2.2, 2.2.3, 2.2.3a). Now when i try to start the windows application, it

Dear all We run Samba 3.5.8 on a Solaris 11 box on top of ZFS We got the impression that the VFS module acl_xattr provides the best way of keeping Windows ACLs. We don't have concurrent NFS or local users so it's Windows only. The clients as well as the Samba server are members of an AD domain. Creating files/directories works as expected and also manipulating permissions for the initial

Hi, I joined a new samba-4.7 DC to our AD, replicated everything over, then turned off the old DCs, seized fsmo roles, and added two extra 4.7 DCs. Everything above succeeded without warnings, and everything seems to be running very well finally, except for the sysvolcheck / sysvolreset. We're on xfs, and the File System Support checks on the samba wiki page all pass, although at the