similar to: Group mapping not working consistently - addendum

I'm trying to understand why my group mapping doesn't work in a consistent fashion. I've studied "Important Samba-3.0.23 Change Notes" & chapter 13 of TOSHARG but am still struggling. I'm on 3.0.23a-1.fc4.1 (Fedora Core 4) as a PDC, tdbsam backend. 'net groupmap list' gives this: Domain Power Users (S-1-5-21-1365060548-1276164359-2333037906-31037) ->

Hi all, I have an odd situation on my hands: * Two CentOS 5.2 boxes both joined to an AD domain. * Same samba version (3.0.28-1.el5_2.1) smb.conf, only the netbios names differ * Can enumerate users and groups using winbind -{u,g} on both. * nss doesn't enumerate users & groups on one (same lib versions, same conf file). //bentis@testukmcsstor1//:~$ rpm -qa | grep nss-

Hi, I've just upgraded an organisation from 3.0.23a to 3.0.25b on CentOS. Everything went fine excpet they're having an issue with Excel files going RO which perhaps is related to acls. $ ls foo.xls -r--rwxr--+ 1 mr.bogus staff 101376 Apr 8 12:59 08-04-04 foo.xls and getfacl gives: # owner: mr.bogus # group: staff user::r-- user:mr.test:rw- group::rw- mask::rwx other::r-- This is

Hi, there is some progress, even I would'nt call it that. At least they admitted it's caused through some changes from their side. @Rowland: Remember that "old Samba method" part? This is their answer. I don't know what to make of it. Maybe someone with more knowledge about the develoment of Samba can give me a hint:

On 29/06/2023 07:38, Ingo Asche via samba wrote: > Hi, > > there is some progress, even I would'nt call it that. At least they > admitted it's caused through some changes from their side. > > @Rowland: Remember that "old Samba method" part? > > This is their answer. I don't know what to make of it. Maybe someone > with more knowledge about the

Hallo, just my 2 cents: So Samba 4.12 works, but 4.13+ doesnt? Maybe you can use the same strategy here as used for Win XP or older OS: Setup an isolated (virtualized?) DC with samba 4.12 just for the synology to connect to? You could use firewalld/ufw rules to only allow traffic to the samba ports from one single source IP-adress (the synology) to limit the exposure... Just until synology

On 04/05/2018 08:29 PM, Paul R. Ganci via samba wrote: > Back on February 28, 2018, I started a thread "User permissions of > profile/home directory lost" describing a problem occurring with my > wife's user account. Since that time the random problem has persisted > so I turned on some debugging. I have been able to determine that > somehow her account idmap is

Back on February 28, 2018, I started a thread "User permissions of profile/home directory lost" describing a problem occurring with my wife's user account. Since that time the random problem has persisted so I turned on some debugging. I have been able to determine that somehow her account idmap is broken. Here is the entry for my wife's SID as found in the idmap.ldb file

Also, it's important to note that 'du -h' reports the appropriate amount of space used and that the drive appears, in all other regards, to be properly using the space. Is this perhaps a bug with how Windows reads the available space left on SMB shares? (Likely a Windows problem) -Tal

I missed a couple of new features: 1) You can now use the "shorewall show zones" command to display the current contents of the zones. This is particularly useful if you use dynamic zones (DYNAMIC_ZONES=Yes in shorewall.conf). Example: foo:/etc/shorewall # shorewall show zones Shorewall-2.2.0-Beta7 Zones at foo - Sat Nov 27 9:18:05 PST 2004 loc

I neglected to document one additional change in this snapshot: 6. The ADDRESS column in /etc/shorewall/masq may now include a comma-separated list of addresses and/or address ranges. Netfilter will use all listed addresses/ranges in round-robin fashion. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

After a few days of troubleshooting, we finally determined why we were having problems. It seems as though the tftp-hpa daemon requires the MTU of the interface it's running on to be >= 1500. We had the MTU set at 1400 (don't ask why) and the PXE client was receiving fragmented packets and failing. As soon as we set it to over 1500, it worked fine. hpa, Could you please update

I should mention that this version of R has been verified to configure and compile on the following platforms: PLATFORM COMPILER alpha-dec-osf3.2 cc hppa1.1-hp-hpux9.07 gcc or c89 i386-unknown-freebsd2.1.5 gcc i686-unknown-linux gcc mips-sgi-irix6.2 cc

I should mention that this version of R has been verified to configure and compile on the following platforms: PLATFORM COMPILER alpha-dec-osf3.2 cc hppa1.1-hp-hpux9.07 gcc or c89 i386-unknown-freebsd2.1.5 gcc i686-unknown-linux gcc mips-sgi-irix6.2 cc

For those of you who haven't had the pleasure, here is the breakage: Undefined symbols: "_LLVMInitializeX86Target", referenced from: llvm::InitializeAllTargets() in llc.o "_LLVMInitializeX86AsmPrinter", referenced from: _main in llc.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: ***

Almost forgot... I already reported this but a few months ago when I was using openSSH 2.9x, it's the same bug. And no - it's not the server end that is stalling me on a revese lookup: 1. I was doing ssh localhost, localhost resolves perfectly, the same for 127.0.0.1 (reverse) 2. ssh -v shows me: debug1: Reading configuration data /usr/local/etc/ssh_config debug1: Seeding random number

Another thing I am working on is to do the timeout people have been asking about. If they have been on hold for (X minutes) dump out of the Queue App, so that the next priority can be a common mailbox. And I forgot to add the patch to my last email!!! argh!!!! http://pbx.usedontmiss.com/queue_patch John

Don't want the opening line of my post to be misconstrued. "Anyone familiar with the BrookTrout TR1034 Fax Board, supports T.38 and PSTN fax in an Asterisk environment?" That's a question, not a statement. Curious if anyone has played with one of these as an extension of an Asterisk server for T.38 faxing, did not mean to imply it could, should or would play well with

Here is the full "transaction" -- outgoing agentcall, to agent '1001', on 'Local/3044@local-4fee,1' -- Called Agent/1001 -- Executing Macro("Local/3044@local-4fee,2", "sipline|3044") in new stack -- Executing Dial("Local/3044@local-4fee,2", "SIP/3044|20|t") in new stack -- Called 3044 -- SIP/3044-ea92 is

I made a mistake in my original post, --diskspec in snapshot-create-as should have shown "hda ...". I also just noticed that 'virsh edit <VM name>' has the correct information (no backing store, only the external snapshot file shown), I was under the impression that /run/... showed the current state, incorrect?