Ingo Asche
2023-Aug-03 14:21 UTC
[Samba] Error for I_NetLogonGetCapabilities with 0xc003000c (RPC_NT_BAD_STUB_DATA)
Hi Kristian, with this version of SMB-Service you will not have much luck that they will resolve that. You have to update to DSM 7.2 (if not already done) and install SMB-Server 4.15.13-0795. Then it schould work again. You have to update to DSM 7.2 because this SMB-Service version is only available for DSM 7.2. Regards Ingo https://github.com/WAdama Kristian via samba schrieb am 03.08.2023 um 15:07:> Thanks for the hints, I will take a look. Support ticket to Synology is > out, let's hope they respond with anything useful and this is not the first > "signs" of Samba breaking, as it was suggested in the thread you mentioned. > If there is any solution I will post it here anyways for archival purpose. > >> I cannot print my thoughts on synology, I would really upset them. > I can only imagine. It is all good and easy if it works, but as soon as you > face a problem like this, you waste the effort tenfold, that it would have > cost you, to set it up vanilla in the first place. > > Thanks again & have a good one. Kristian > > Am Do., 3. Aug. 2023 um 14:38 Uhr schrieb Rowland Penny via samba < > samba at lists.samba.org>: > >> >> On 03/08/2023 13:20, Kristian via samba wrote: >>> Hey Rowland, thanks for the quick reply. Yes, it is a Synology DS >>> unfortunately and I didn't expect that they'd mangle with the Samba code, >>> but thought they take stock Samba and just configure it. Lesson learned I >>> guess. Thanks for the hint. This is also why I am stuck at 4.15.9, as >> this >>> is what the Synology package comes with right now. Based on your previous >>> comment I guess any attempt upgrading it on my own is worthless then. I >>> will try to reach out to Synology support, but I guess they won't dig as >>> deep as I am already, let's see. Thanks anyways. >> Try reading this: >> https://lists.samba.org/archive/samba/2023-July/245691.html >> >>>> This list strips attachments, if you require someone on this list to >>>> look at your logs, you will need to post them somewhere and then post a >>>> link here. >>> The logs don't show very much more interesting in terms of the error >>> unfortunately. I thought I could "reverse engineer" myself into why the >>> machine thinks it received a RPC_NT_BAD_STUB_DATA, but I guess there is >> no >>> longs on Samba side for that, right? Thanks again, Kristian >>> >> That error message seems to appear in only one place in the standard >> Samba code: >> >> libcli/util/ntstatus_err_table.txt >> >> Where you will find this (at line 8022): >> >> 0xC003000C >> >> RPC_NT_BAD_STUB_DATA >> >> >> The stub received bad data. >> >> I cannot find it anywhere else in the code, this doesn't mean it isn't >> used by Samba, just that I cannot trace any use of it. >> >> I cannot print my thoughts on synology, I would really upset them. >> >> Rowland >> >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >>
Ingo Asche
2023-Aug-03 14:38 UTC
[Samba] Error for I_NetLogonGetCapabilities with 0xc003000c (RPC_NT_BAD_STUB_DATA)
Hi Kristian, and I forgot that there was also a patch to deal with the hick-up caused through the last MS updates: https://community.synology.com/enu/forum/1/post/161649?page=1 I haven't tested it because it doesn't seems to be necessary in my little Samba domain. Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 03.08.2023 um 16:21:> Hi Kristian, > > with this version of SMB-Service you will not have much luck that they > will resolve that. > > You have to update to DSM 7.2 (if not already done) and install > SMB-Server 4.15.13-0795. Then it schould work again. > > You have to update to DSM 7.2 because this SMB-Service version is only > available for DSM 7.2. > > Regards > Ingo > https://github.com/WAdama > > Kristian via samba schrieb am 03.08.2023 um 15:07: >> Thanks for the hints, I will take a look. Support ticket to Synology is >> out, let's hope they respond with anything useful and this is not the >> first >> "signs" of Samba breaking, as it was suggested in the thread you >> mentioned. >> If there is any solution I will post it here anyways for archival >> purpose.