similar to: Prevent read locks on shares

Thanks Jeremy but I don't understand why the lock is being applied at all when it's not being asked for. Your advice to not disable locking if applications legitimately share file access to me seems to be the inverse of what is needed. After all, the fact that our application shares file access is the very reason we don't want file locking. regards, John On 28/01/16 10:37,

On Thu, Jan 28, 2016 at 09:25:20AM +1100, John Gardeniers wrote: > I really don't know if this is a Samba or Linux issue but after > migrating one of our file shares from a Samba 3 server to a Samba 4 > server we discovered a problem that never existed before. On this > share we have a couple of ini files which is periodically read by a > Windows application on client machines.

We're upgrading (Sernet) Samba 4.2 to 4.4. As recommended on this page: https://wiki.samba.org/index.php/Updating_Samba, I have upgraded one of out 2 DCs, the one that does not have any FSMO roles. We will spend the next week making sure everything works as expected. So far, so good. One thing I'm not clear on is whether I should move the FSMO roles to the upgraded DC before upgrading

Hi Andrew, I don't understand why 2 systems running the exact same version of Samba have different behaviour. Is this an option I can disable? regards, John On 19/04/16 11:29, Andrew Bartlett wrote: > On Tue, 2016-04-19 at 10:29 +1000, John Gardeniers wrote: >> I'm setting up a test domain in order to try out Sudoers LDAP and >> have >> run into a problem that has

Hi, testparm -v | grep 'ldap serve' Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[netlogon]" Processing section "[sysvol]" Loaded services file OK. Server role: ROLE_ACTIVE_DIRECTORY_DC Press enter to see a dump of your service definitions ldap server require

Hi Jeremy, No, I don't mean "deadtime". I mean auto disconnect. Specifically, the command "net config server /autodisconnect:-1" was run on each client machine. If deadtime is a server configuration item perhaps you could point me in the direction of some documentation where that is covered. The documentation for smb.conf is, to put it very mildly, incomplete.

I see this was created as bug 7259 but I did not see anything in the mailing list about this problem. Does anyone else have a problem like this? Is there something in my configuration that is incorrect? We have two domain controllers, and if we reboot either one of them, winbind hangs, and we cannot lookup any ids, and since logins are requiring group lookups, it makes logging in as a local user

We're using the Sernet Samba v4.2.4 with internal DNS and I can't find the DNS logs. Where does the Samba 4 internal DNS log queries? Thanks. regards, John

On 11/4/2015 4:13 PM, John Gardeniers wrote: > Nobody? Surely somebody knows where Samba 4 logs its DNS queries, or > was this was a huge oversight and the internal DNS doesn't get logged > at all, as appears to be suggested by my utter failure to locate such > logs. > > On 28/10/15 14:28, John Gardeniers wrote: >> We're using the Sernet Samba v4.2.4 with

IMHO: no real need to move FSMO before upgrading FSMO owner if no real load. FSMO are roles which make one DC different of others DC on one specific point (for each role). As long as you don't do something which requires FSMO role you won't use FSMO roles, so no matter. Things which triggers FSMO usage are modifying the schema (don't do that during upgrade), reaching RID pool limit on

Has anyone here managed to get sudo working with Samba 4 AD users, using either ldap or sssd, with sssd preferred? If so, can you please point me in the direction of whatever instructions you used? It seems like there are a bunch of tutorials on the subject, each with different, and sometimes conflicting, information but none of those I've tried work for me. regards, John

Hi Rowland, I Upgraded from Samba 4.4.2 and we have tried the FQDN without success. regards, John On 21/11/16 08:02, Rowland Penny via samba wrote: > On Mon, 21 Nov 2016 07:42:30 +1100 > John Gardeniers via samba <samba at lists.samba.org> wrote: > >> Hi Louis, >> >> While it wasn't spelled out, it was firmly implied in my previous >> message that

Hello - I am trying to migrate my dovecot installation from an older server running version 1.x to the latest 2.0.3 When I run configure --with-vpopmail, it bombs pretty quick as follows: ./configure --with-vpopmail checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for

no DNS server on that planet logs normal queries just because there si not enough disk space in most setups, there is not benefit log anything except erros and warnings for normal operations what is the problem you like to solve and if there is no problem why do you want logging normal operations? in other words: what do you try to solve except https://wiki.samba.org/index.php/DNS Am

Hi Rowland, Perhaps I misled you with my wording. Each user has just one email address, which was not migrated across. From where I'm sitting that looks like a very serious bug. regards, John On 31/08/15 19:07, Rowland Penny wrote: > On 31/08/15 07:27, John Gardeniers wrote: >> I've been running through a bunch of tests after migrating from >> Samba > 3 to Samba 4

Probably a ld issue. It might have not run in the rpm's post script. Do a ldd /usr/lib64/samba/libsmbregistry-samba4.so /usr/lib64/samba/vfs/acl_xattr.so and check if either are reporting missing dependencies. Em 07/02/2017 21:25, John Gardeniers via samba escreveu: > This is really weird. The error below occurred for about 10 minutes after the > post-update reboot and then went

Hi Klaus, I haven't used that tool for at least 13 years but I do recall that, among other things, it read from the registry. Coupled with the fact that Samba 4 AD is not a complete implementation of AD I can't imagine that it could possibly work. More to the point, I'd be seriously concerned about the results. This is not something I'm prepared to test in a production

Hi Rowland, Thanks for the suggestion. So far, since adding 'ntlm auth' to smb.conf on the DCs we are no longer having this problem. Only time will tell if it stays working but at least I'm no longer getting complaints from the users. regards, John On 21/11/16 10:00, Rowland Penny via samba wrote: > On Mon, 21 Nov 2016 09:31:28 +1100 > John Gardeniers via samba <samba

We recently completed our Samba 3 to Samba 4 transition without too many serious problems but one rather annoying issue has cropped up since the migration. Network shares on our file server become disconnected overnight, whether idle or not. This was never a problem with Samba 3 but since upgrading Samba on the server to version 4 and joining it to the Samba 4 AD domain this problem is

Hi Volker, Thanks for the response. The clients are Win 7, Win 10 and various flavours of Linux, with Samba client versions ranging from 3.6 to 4.5.3. There is no perceptible difference between any of them. Network latency is never above 0.2s and mostly sits at around 0.1s. If that's a problem it is so only for Samba. I did as you suggested with the smb options but that just made it