[Samba] Samba AD DC and browsing of shares

[Rowland Penny]

On 20/03/15 13:00, Jānis wrote:
>
> ----- Vēstule no Rowland Penny <rowlandpenny at googlemail.com> ---------
>   Datums: Fri, 20 Mar 2015 09:19:10 +0000
> Sūtītājs: Rowland Penny <rowlandpenny at googlemail.com>
>   Temats: Re: [Samba] Samba AD DC and browsing of shares
> Saņēmējs: samba at lists.samba.org
>
>>>> You can recompile it if you want to, but if you use packages from 
>>>> your distro, you shouldn't have to. What distro are you using?
>>>
>>> Slackware(64-14.1), so I am used to re-building things to my liking :)
>>>
>>> Janis
>>>
>>> P.S. If the client still wants _AD_ DC - can i just build fileserver 
>>> using the same samba4 build I have for DC (I re-built it after 
>>> installation of heimdal 1.5.2), join it to the domain and have the 
>>> shares on FS browsable? Any howtos/hints for such configuration? For 
>>> the purpose of finding the best solution I already have virtual 
>>> network of 4 virtual machines (ADDC + 3 types of clients), virtual 
>>> file server will be fifth.
>>>
>>
>> You are your own there with slackware, never ever used it, sorry :-)
>>
>> When you say that you have installed heimdal, I hope this was as a 
>> client, samba4 in AD DC mode comes with its own keberos server.
>>
>> From my limited testing, you only need to compile samba4 one way, it 
>> is then how you use the binaries that dictates what type of samba 
>> server you get.
>
> the necessity for external heimdal even for Samba 4 in case of 
> Slackware I found somehwere in solutions and it incidentally 
> co-incided with getting samba AD DC working.
> Browsing the original Slackware package I can not locate a thing like 
> kinit, for example, while krb5.conf is there
>
> OK, but his is not the problem.
>
> T
>

You started out asking if you could have network browsing with a samba 
AD DC like there is with samba3, well the answer to this is 'no'

I am not saying you shouldn't have kerberos installed, just the opposite 
in fact, you just cannot run the server part of it.

Try running this:

netstat -tapn | grep ':88' | grep 'samba'

If you do not get a response, you have a big problem.

Rowland