search for: wadama

...blem 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, clear the SMB cache and then it should work again. Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 13.04.2023 um 21:37: > 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 > &g...

...he 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: > 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 >...

...ian to Debian bookworm. It has several advantages: - All Debian packages are immediately available - There are no differences between the distros anymore - Debian has 64-bit available, so it also moves from 32 to 64-bit, which is nice - Kees. > > 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 Bullseye-Backports getting 4.17.12, too? >>> >>> I saw, Bookworm is already update...

..., > works via ip no via dns name" > > I've already openend a ticket with Synology. > > So be careful before updating the SMB-Service, maybe test it first on a > not so important system. > > Regard > Ingo > > -- > Regards > Ingo > https://github.com/WAdama > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >

...h problems. Also an old Synology DS413 with Samba 4.4.18 (don't laugh) works perfectly, too. So I would think this patch has to be installed on the machines with the error. Maybe someone can shed some light on this bug, so I can react the right way to this. Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 24.05.2023 um 09:47: > 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 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 um 09:54: > > Hi Ingo, > Just one other thought, You are having problems with the SID S-1-18-1 > and the patch on that bug report does not mention that SID, so even if > you do manage to patch something, it isn't likely to help you...

...:4.21.3+dfsg-5~bpo12+1 samba-dsdb-modules 2:4.21.3+dfsg-5~bpo12+1 samba-libs 2:4.21.3+dfsg-5~bpo12+1 smbclient 2:4.21.3+dfsg-5~bpo12+1 tdb-tools 2:1.4.12+samba4.21.3+dfsg-5~bpo12+1 winbind 2:4.21.3+dfsg-5~bpo12+1 It's all corrected to "dfsg-5"... Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 12.01.2025 um 14:55: > On Sun, 12 Jan 2025 13:41:54 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > Whatever happened, it happened this morning. This morning I updated my > main computer, among the updates was: > &g...

...hat I thought already. At least what they say about using an old Samba version. Another thought just accured to me: But why they changed it after three years the change is already in use. Why now? But as you said, that's something only Synology can answer. Regards Ingo https://github.com/WAdama <https://github.com/WAdama> Rowland Penny via samba schrieb am 29.06.2023 um 10:00: > > My reading of the above (which could be wrong) is: > > A respected member of the Samba team decided that using 'lookupsids' > wasn't required just to find out if the SID was a...

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 everything is running. >> The config...

...rver joined to a samba domain accessed by windows 10-11 clients, works via ip no via dns name" I've already openend a ticket with Synology. So be careful before updating the SMB-Service, maybe test it first on a not so important system. Regard Ingo -- Regards Ingo https://github.com/WAdama

...one SID which can't be dissolved by winbind: S-1-18-1. As I wrote in my last mail, this SID don't exist under 2008R2 and earlier. I'm afraid you have to read the hole trail to get all informations. So do you use IP addresses or hostnames for access? Regards Ingo https://github.com/WAdama vincent at cojot.name schrieb am 07.07.2023 um 02:42: > > Hi Ingo, > Sorry for the late reply but I just gave it a test tonight and > everything worked fine for me: > - Domain Controllers run RHEL8.8 + samba 4.17.8 > - DSM 7.1.1 VM and DSM 7.2 physical box (DS3622xs) > I can...

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 Bullseye-Backports getting 4.17.12, too? >> >> I saw, Bookworm is already updated... > > Since oldstable-bp...

...my answer from April 23th. Kees has written a script especially for this: See "dc_password_change" on https://github.com/kvvloten/samba_integrations/tree/main/domain_controller/manage_scripts This script works in my AD without problems for some time... Regards Ingo https://github.com/WAdama Kacper Wirski via samba schrieb am 02.05.2025 um 22:15: > Hello, > > net ads changetrustpw > > this command works fine on domain members, but on domain controller > there is hard fail with: > > ads_change_trust_account_password: Machine account password change > only...

...t; On the first DC it's running like I expacted, but on the second one I'm having the provlem. > As like 9.16 I use the "dlz_bind9_18.so" entry in named.conf. > > If you need further information to compare just ask. > > Regards > Ingo > https://github.com/WAdama > > Rowland Penny via samba schrieb am 16.01.2023 um 20:05: >> >> >> On 16/01/2023 18:56, Rowland Penny via samba wrote: >>> >>> >>> On 16/01/2023 18:27, Stefan Kania via samba wrote: >>>> >>>> >>>> Am 16.01.23...

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: Samba 4.17.4 and bind 9.18 from the >> bullseye-backports. >> >> I my case "samba_dnsupd...

...ve certain considerations and thus not suggesting User to apply the code since they are not officially released. Who will guarantee code that hasn't been officially released yet? ================================================================================ Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 21.06.2023 um 10:30: > 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 >...

...ba 4.17.4 and bind 9.18 from the bullseye-backports. I my case "samba_dnsupdate --verbose --all-names" runs without any errors. As like 9.16 I use the "dlz_bind9_18.so" entry in named.conf. If you need further information to compare just ask. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um 20:05: > > > On 16/01/2023 18:56, Rowland Penny via samba wrote: >> >> >> On 16/01/2023 18:27, Stefan Kania via samba wrote: >>> >>> >>> Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >...

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 everything is running. The > configuration is always the same. > > I am getting confused now (not that it takes much) Are you saying that none of your 4.17.x DC's work with Bind 9.18 ? Ingo seems to be

...m with getting access rights to shares through groups. Only with Windows workstations, not from Linux workstations. I found out with changing a Library from an older Version it works again, but they couldn't second it, because they still test from Linux. -- Regards Ingo https://github.com/WAdama

On 20/06/2023 19:48, Ingo Asche via samba wrote: > 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. Multiple users having the same problem always help. > > Maybe the maintainers who has answered to the bug report can give