similar to: Sharing an nfs mounted directory from two different samba servers?

Hello, I'm testing windows 7 with samba 3.4.7 and I'm using PrintUIEntry to connect the printers. With some of those printers the connection fails (client side) with error 0x000003e6. The strange thing is that: 1) trying the same connection against samba 3.0.11 works (alas, no domain functionality with that old version) and 2) two of the failing printers share the same driver with

Hello, last friday I switched my users from an old server running 2.2.12 to a new one running 3.0.10 (that I've been testing myself and with smbtorture). After a while I had to switch back to the old server because some users were having serious problems. This is one of the logs (the others are very similar): [2005/03/04 12:25:05, 0] tdb/tdbutil.c:tdb_log(725)

Hello, I'm trying to upgrade samba (TPTB are going to introduce win7 workstations) on my old server (mandrake 10.0) currently running 3.0.11. I setup a virtual machine to do some testing and I built rpms for 3.5.2 (apart from the other problems it has this one https://bugzilla.samba.org/show_bug.cgi?id=7263) then for 3.4.7 and finally for 3.3.12. Each one of them has problems, the most

Ok, I finally deployed samba 3.5.2 (upgrading from 3.0.11) on the real server after testing for a while in virtualbox. There's a strange problem with printing: sometimes an application gives an error printing (of course the error message is meaningless, this is windows after all) and/or the job gets lost in transit. After that stopping and restarting the local print spool service solves the

El 11/10/19 a les 16:59, Luca Olivetti via samba ha escrit: > El 11/10/19 a les 16:12, Rowland penny via samba ha escrit: >> Try running this on a DC: >> >> samba-tool ldapcmp ldap://DC1 ldap://DC2 >> --filter='whenChanged,dc,DC,cn,CN,ou,OU' >> >> Replace 'DC1' and 'DC2' with your actual DC short hostnames >> >> It should

El 12/03/16 a les 18:27, Jeremy Allison ha escrit: > On Sat, Mar 12, 2016 at 06:07:25PM +0100, Luca Olivetti wrote: >> Unfortunately it seems it is using a really old version of samba [...] >> Version 1.9.16p10 >> -D become a daemon >> -p port listen on the specified port >> -d debuglevel set the

Hi Luca, thank you very much for the tip. I’ve tried to run it with the filter the web page suggests and I got an empty set. I took a look at one of the user objects and I couldn’t see any samAccountType there. > On 04 Apr 2017, at 19:54, Luca Olivetti via samba <samba at lists.samba.org> wrote: > > El 04/04/17 a les 16:17, Juan García-Pardo via samba ha escrit: >> The

El 2/9/18 a les 01:03, Luca Olivetti via samba ha escrit: > El 1/9/18 a les 03:03, Jamie Jackson via samba ha escrit: >> Hi folks, >> >> Every couple days any one of my project's 10 or so RHEL VMs can't be >> logged >> into with a domain account (active directory integration). Our admin goes >> in with a local account and restarts winbind to fix it.

El 24/06/15 a les 17:02, James ha escrit: > On 6/24/2015 10:13 AM, Rowland Penny wrote: >> On 24/06/15 14:17, Luca Olivetti wrote: >>> El 24/06/15 a les 14:30, James ha escrit: >>>> Hello, >>>> >>>> Is it possible to use isc-dhcp for DDNS with Samba internal DNS? I >>>> would rather not use bind as I understand you can't

El 3/9/18 a les 16:35, Jamie Jackson via samba ha escrit: > I didn't set this up, but I assume the sysadmins didn't run it because > they, like Luca, probably assumed that smbd was for server functionality I didn't assume, it's the documentation that says so. In fact, the winbindd man page says that the winbind daemon provides services to smbd and ntlm_auth, not the

El 3/9/18 a les 17:13, Rowland Penny via samba ha escrit: > Yes, but it depends on how you run Samba. If you run Samba as a > standalone server you only need to run 'smbd', but running 'nmbd' as > well would be a good idea. > > If you run Samba as a PDC or BDC, the same as a standalone server goes. > > Anything else needs both smbd and winbind running. It

Today I noticed something that has been going on for some weeks: I have 2 dc, (dc1 and dc2) both debian buster with the distro provided samba (4.9.5), recently upgraded from stretch. samba-tool drs showrepl on dc2 says DC=DomainDnsZones,DC=samba,DC=wetron,DC=es Default-First-Site-Name\DC1 via RPC DSA object GUID: 89812346-9037-43b0-86ab-c5052f55125d

El 12/03/16 a les 17:08, Jeremy Allison ha escrit: > On Sat, Mar 12, 2016 at 12:50:50PM +0100, Luca Olivetti wrote: >> El 12/03/16 a les 12:37, Rowland penny ha escrit: >> >>> Well yes, but these are usually a mass market product and will no doubt, >>> in the fullness of time, get to use a version of Samba 4 seeing as how >>> 3.6 has been EOL since March

On 11/10/2019 14:58, Luca Olivetti via samba wrote: > El 10/10/19 a les 20:23, Luca Olivetti via samba ha escrit: >> Today I noticed something that has been going on for some weeks: >> >> I have 2 dc, (dc1 and dc2) both debian buster with the distro >> provided samba (4.9.5), recently upgraded from stretch. >> >> samba-tool drs showrepl on dc2 says >>

Hello, my isp provided me with an ont+wireless router combo. The router can share via samba a mounted usb thumb drive. The problem is that it's a very old samba version (apparently 1.9.16p10) and I cannot access it from Linux: luca at seis:~$ smbclient -s /dev/null -L 192.168.10.1 Enter luca's password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 1.9.16p10] tree connect failed:

El 10/10/19 a les 21:07, Rowland penny via samba ha escrit: >> > It works in a similar way to how I update dns records and I have similar > records in AD and they replicate. Oh, but they do. Until the replication chokes on those deleted records. Never happened until September 25 (though I realized only today when a manually added host resolved erratically). > > Can you post

El 10/10/19 a les 20:41, Rowland penny via samba ha escrit: >> It turns out that dc2 chokes on "\0ADEL" dns records, supposedly >> deleted objects. > > What you have there is known as a tombstone record and Samba has a tool > to remove them: > > samba-tool domain tombstones expunge NC > --tombstone-lifetime=TOMBSTONE_LIFETIME > > Where

El 12/03/16 a les 12:37, Rowland penny ha escrit: > Well yes, but these are usually a mass market product and will no doubt, > in the fullness of time, get to use a version of Samba 4 seeing as how > 3.6 has been EOL since March 2015. You'd be surprised to see what old shi^H^H^H "carefully crafted with backported fixes packages" router vendors put in their products. In a

El 2/9/18 a les 10:39, Rowland Penny via samba ha escrit: > All of this is just a sticking plaster on the problem, if winbind is > crashing on a regular basis, we need to know this and will need > level 10 logs, debug info etc. Without this info, it will never get > fixed. Meanwhile, I need my server to keep running, so the plaster looks fine. Besides, winbind isn't crashing,

On Mon, 3 Sep 2018 15:37:03 +0200 Luca Olivetti via samba <samba at lists.samba.org> wrote: > El 3/9/18 a les 15:23, Robert Marcano via samba ha escrit: > > >> > >> I run this cron job every minute. Winbind usually crashes once or > >> twice a day > >> > >> #!/bin/bash > >> getent group | grep -q 513 && exit 0 >