Thanks for the reply.
Both dnsmasq and samba are set up by me, but the config I gave below could
easily imply something I don't intend - I'm not 100% sure on it. Maybe at best
60% :(
Shouldn't dnsmasq and the gateway DHCP server be the domain controller? And so
samba should be subordinate - OK, I see now that setting up samba with "domain
master = yes" could be bad.
What I'm fundamentally unclear about is what the workgroup is - is it just a
samba-style name for the domain - and therefore should be 'localdomain'?
Adam
richardvo...@gmail.com on 13/10/08 12:42, wrote:
If you're set up as a domain controller, rather than plain workgroup
(and you are), then you need to forward dns requests for that domain
to the samba domain controller. I think the needed dnsmasq
configuration option is "server". You also need to make sure dnsmasq
is not filtering out Microsoft Networking requires, there's a
filterwin2k option or something like that which needs to be disabled.
Hope this helps.
On Mon, Oct 13, 2008 at 10:21 AM, Adam Hardy
<adam....@cyberspaceroad.com> wrote:
Just been wading through the docs and the mailing lists at samba.org trying
to find out how I should configure my samba file server but I still haven't
been able to work out the relationship of the samba server to the rest of my
network.
I'm running a SOHO with linux, OS X and windows clients which need to
connect to the samba server to be able to run backups. I think it's causing
conflict with the main gateway / DHCP server (which runs dnsmasq).
Samba has these 4 settings which are causing me complete confusion:
workgroup = SAMBA_WORK_GROUP
domain master = yes
local master = yes
preferred master = yes
By all accounts this appears to be the way to allow the clients to browse
the samba server, but I get problems with connections dropping,
authentications failing and sometimes the server not even showing up.
Am I right that the workgroup name should be totally different from the
domain name I set for the DHCP clients in dnsmasq? (localdomain)
