samba - Nov 2015 - Samba4 DC is not visible in network neighborhood

Greetings, All!

Is there at last a solution? I've only found questions, in the list, and on
the network.

The issue is that DC built on Samba4 does not report to network browsers
neither it is participating in election to become browser itself.
Consequently, it is not visible in the neighborhood neither on Windows, nor on
Linux.

I've managed to force a second Linux host (member server) become a local
browser. At least, I can see it and other hosts now. But not the DC itself.


-- 
With best regards,
Andrey Repin
Tuesday, November 17, 2015 20:32:23

Sorry for my terrible english...

On 17.11.2015 19:46, Andrey Repin wrote:
> Greetings, All!
>
> Is there at last a solution? I've only found questions, in the list,
and on
> the network.
>
> The issue is that DC built on Samba4 does not report to network browsers
> neither it is participating in election to become browser itself.
> Consequently, it is not visible in the neighborhood neither on Windows, nor
on
> Linux.
>
> I've managed to force a second Linux host (member server) become a
local
> browser. At least, I can see it and other hosts now. But not the DC itself.
>
>
Hi Andrey,

In that case you did exactly what you were supposed to do. :)

Browsing is turned off for the DC by design, and this will not change. 
Use member servers to implement browsing.

Viktor

Greetings, Viktor Trojanovic!
>> Is there at last a solution? I've only found questions, in the
list, and on
>> the network.
>>
>> The issue is that DC built on Samba4 does not report to network
browsers
>> neither it is participating in election to become browser itself.
>> Consequently, it is not visible in the neighborhood neither on Windows,
nor on
>> Linux.
>>
>> I've managed to force a second Linux host (member server) become a
local
>> browser. At least, I can see it and other hosts now. But not the DC
itself.
>>
>>
> Hi Andrey,
> In that case you did exactly what you were supposed to do. :)
> Browsing is turned off for the DC by design, and this will not change. 
> Use member servers to implement browsing.
And how am I supposed to address the DC then?
For all my attempts, I've had to conclude that member servers can't be
configured to manage shares with native ACL's. No matter what I do, I always
get "access denied" on a member server when trying to setup share
permissions
on a member server using Windows tools.
So far, the only solution was to move ACL-sensitive services to the DC.
But this is really not a solution. Only a workaround.


-- 
With best regards,
Andrey Repin
Saturday, November 21, 2015 21:30:23

Sorry for my terrible english...