similar to: @Michael Tokarev: Samba 4.17.12

Op 18-10-2023 om 11:32 schreef Ingo Asche via samba: > Hi Michael, > > thanks for the info - and your work... > > As Bookworm for Raspberry isn't that far away, I can live with that. > This is "just" my playground... I have recently migrated my Raspberry Pi machines from Raspbian to Debian bookworm. It has several advantages: - All Debian packages are

Hi Michael, thanks for the info - and your work... As Bookworm for Raspberry isn't that far away, I can live with that. This is "just" my playground... Regards Ingo https://github.com/WAdama Michael Tokarev via samba schrieb am 18.10.2023 um 09:17: > 16.10.2023 15:50, Ingo Asche via samba wrote: >> Hi Michael, >> >> short question: will the

16.10.2023 15:50, Ingo Asche via samba wrote: > Hi Michael, > > short question: will the Bullseye-Backports getting 4.17.12, too? > > I saw, Bookworm is already updated... Since oldstable-bpo archive in debian is always subject to manual backports-policy processing (all uploads are processed manually), I don't push stuff to oldstable-bpo often. On the other hand, this

18.10.2023 10:17, Michael Tokarev via samba: > Since oldstable-bpo archive in debian is always subject to manual > backports-policy processing (all uploads are processed manually), > I don't push stuff to oldstable-bpo often.? On the other hand, this > security update definitely should go to oldstable-bpo. https://ftp-master.debian.org/backports-new.html - samba is in bullseye

On Wed, 18 Oct 2023 11:32:45 +0200 Ingo Asche via samba <samba at lists.samba.org> wrote: > Hi Michael, > > thanks for the info - and your work... > > As Bookworm for Raspberry isn't that far away, I can live with that. > This is "just" my playground... > You must not have played with your Raspberry pi lately, Raspberry pi OS based on Bookworm came

Hi Travis, are you still there? ;-) How are your Synos do? Do have in the mean time installed the actual SMBService? If you have and have with the actual SMBService the same problem as before the Beta version there is a workaround: In "/usr/local/packages/@appstore/SMBService/usr/lib/samba" you have to change the "libidmap-samba4.so" to the one from the beta version,

Hi Travis, I know, but this is now the released version (4.15.9-0919 beta > 4.15.9-0631), see the history page for SMB-Service: https://www.synology.com/en-us/releaseNote/SMBService?model=DS918%2B#7_x_series With the beta version it still works. But we can't stay on the beta forever I think. Regards Ingo https://github.com/WAdama Travis Wenks via samba schrieb am 13.04.2023 um 21:29:

Hi All, the Synology support is claiming this bug is the reason for the access problems via hostname (Kerberos): https://bugzilla.samba.org/show_bug.cgi?id=14213 These log entries in log.wb-ADNAME are given as evidence: ../../source3/winbindd/winbindd_msrpc.c:307: [2023/06/14 22:13:42.913399, winbind 3, pid=10150] msrpc_sid_to_name msrpc_sid_to_name: S-1-18-1 f?r Dom?ne ADNAME

The only way I have found to fix that is to enable the beta updates in plugins and install the beta version of samba on the Synology. Thank you, Travis Wenks Rose City Solutions Owner [image: Rose City Skyline Logo] * Phone *503.821.7000 <3464881845> * Website *rosecitysolutions.com <https://rosecitysolutions.com> * Email * travis at rosecitysolutions.com On Thu, Apr 13, 2023

Ah, ok, just saw it. Sorry, I missed that. I can only add then, all three DC's in my little net are installed with bind 9.18 and working all the same without errors. Regards Ingo https://github.com/WAdama Stefan Kania via samba schrieb am 16.01.2023 um 20:47: > > > Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: >> Hi Stefan, >> >> I have exact that running:

We're running Dovecot 2.2.21 from Stephan Bosch's build service on Dovecot 7.x. Everything's up2date. # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (71e908a) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 root at mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30

Yes, in my opinion quite an arrogancy... This is the translation of what I got from the supporter: "Our developers have discussed and have concluded that we stand by our previous statement and define the problem as a problem of Samba AD Server (4.17.*). Although Synology is an open source product based on Samba, but we don't always stick to it and adapt our own code in many

That's exactly what I'm saying. I can add output from all three DC's if necessary. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um 22:02: > > > On 16/01/2023 20:52, Stefan Kania via samba wrote: >> As I said, both DC are installed via Vagrent, starting the setup with >> 9.18 I have the problem, starting with 9.16

Hi, to all of you which are using Synology NAS systems. With SMB-Service 4.15.9-0631 no longer shares are accessible via domain group rights from a Samba 4.17.7 domain. It seems the same error described in the following mail trails: "No longer access to shares after upgrade to 4.17.3" "File server joined to a samba domain accessed by windows 10-11 clients, works via ip no via

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:

Hi Rowland, good point... That seems to be the only SID which popps up in the logs from the Synology device. I found no other. I'm just looking at the same log on my working machines if this is popping up there, too. At least you gave me good hints, how I can answer their request. Thanks for that... Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 21.06.2023

Hi All, I have a - maybe dumb - question: What is the difference between an access to a Samba share from Linux and from Windows? Is there a difference in protocol or getting share rights or anything else? I think I remember that there is. Maybe someone can push into the direction of a documentation. Base for this question is a ticket I have open with Synology. There is in newer versions of

This is the essence of the last message from Synology: For Synology the problem is no problem... They simply say now, we never claimed we are compatible with Samba AD, only with Windows AD, Azure AD and Synology Directory Server: ?? ?"Domain/LDAP ?? ?Features ??? Seamless integration with Windows AD, Azure AD Domain Service, and LDAP servers" See:

There was a Travis Wenks here, who has/had the same problems. I'm still hoping, he's reading the Samba mail list and tell me if he has still the same problems and we maybe can ally for this. Maybe the maintainers who has answered to the bug report can give some advice, too. The problem for me is that the developers from Synology think it can't be their fault. It's a little

Rowland Penny via samba schrieb am 20.06.2023 um 21:01: > Try adding to the bug report. Would that be ok even it's happening on a Synology? Just don't want to mess around. > I don't think that it is their fault, but we will never know, I don't > think we will ever see what modifications they have made to the Samba > code. However, you do not seem to get the problem