[Samba] setting up a new ADS infrastructure

[Rowland penny]

On 14/06/2019 05:50, Stefan Froehlich via samba wrote:
> On Thu, Jun 13, 2019 at 08:10:01PM +0100, Rowland penny via samba wrote:
>> On 13/06/2019 19:57, Stefan Froehlich via samba wrote:
>
>> It already might have ;-)
>>
>> wbinfo reads directly from AD, but doesn't mean that  the OS knows
>> your users & groups, does 'getent passwd test' produce the same
>> output ?
> Fortunately yes, and as I can do ssh logins with this account, even
> based on group membership, the unix side of the job seems to be
> quite settled. The windows side will have to wait a little bit as it
> requires my physical presence.
Windows should just work
>
> The only cosmetic thing is that I still get this in my log files:
>
> | [2019/06/14 06:04:22.007350,  4] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
> |   dump_workgroups()
> |    dump workgroup on subnet    192.168.1.13: netmask=  255.255.255.0:
> |         WORKGROUP(1) current master browser = CONTROLLER
> |                 CONTROLLER 40849a03 (Samba 4.9.5-Debian)
> |                 MAC01 40001003 (Mac01)
> |                 RNP002673E572C4 40000203 ()
> | [2019/06/14 06:04:22.007420,  4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
> |   find_workgroup_on_subnet: workgroup search for SAMDOM on subnet 192.168.1.13: not found.
> | [2019/06/14 06:04:22.007432,  0] ../source3/nmbd/nmbd_serverlistdb.c:340(write_browse_list)
> |   write_browse_list: Fatal error - cannot find my workgroup SAMDOM
> | [2019/06/14 06:04:22.007448,  4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
> |   find_workgroup_on_subnet: workgroup search for SAMDOM on subnet UNICAST_SUBNET: not found.
> | [2019/06/14 06:04:22.007457,  0] ../source3/nmbd/nmbd_browsesync.c:595(collect_all_workgroup_names_from_wins_server)
> |   collect_all_workgroup_names_from_wins_server:
> |   Cannot find my workgroup SAMDOM on subnet UNICAST_SUBNET.
> | [2019/06/14 06:04:22.007469,  4] ../source3/nmbd/nmbd_workgroupdb.c:165(find_workgroup_on_subnet)
> |   find_workgroup_on_subnet: workgroup search for SAMDOM on subnet UNICAST_SUBNET: not found.
>
> I do not see any practical problems resulting from this up to now,
> so I won't further investigate it, but if this is pointing to
> something really obvious mistake, I'd of course fix it.
>
I wouldn't worry about it, it is probably an artefact of SMBv1 being 
turned off and/or the log level being set too high.

Rowland