On 10/02/2023 10:01, Stefan G. Weichinger via samba
wrote:> Am 10.02.23 um 10:34 schrieb Rowland Penny via samba:
>
>>> I asked the windows admin and told him that I don't get correct
>>> replies when doing "dig @DC1 ..." on samba. No reply yet
from him.
>>
>> He is probably rushing around trying to find out what is up with his
>> DC ;-)
>
> I don't think so ;-) he told me to take that DC away as DNS server ...
> it's planned to replace that DC anway according to him.
Hmm, so there is a DC that is having some dns problems and the windows
admin isn't bothered that this 'may' be replicating to his other
DC's ????
>
>>> I don't want to edit the settings on his machines right now.
>
>> No, I guess you wouldn't
>
> Did now after he told me so. Didn't change anything around these
warnings.
I didn't think it would.
>
> I think I let that for now and don't do anything until the update in
the
> evening.
>
> I don't expect this to be fixed by the updates but it's good to
stay up
> to date anyway.
>
Yes, good to keep up to date, but like you, I don't think updating will
fix this problem.
If you actually have files that are owned by 'Administrator:SOME_GROUP'
on Linux, then you I would suggest you look at them using 'ls' with the
'-n' switch. I think you will find that they are not owned by
'0:SOME_GROUP_IDNUMBER'
Rowland