Good evening, I am trying to setup Samba as file server using this tutorial: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server The version I am using is 4.6.7 from Van Belle's repo, on Debian Stretch 9.1. I have a server subnet (192.168.13.x) and a client subnet (192.168.11.x), currently, for testing purposes, the server is on the same subnet as the clients. Will I have problems if after the tests I move to the server subnet? Clients are Windows 10 x64 build 1703 and it seems Master Browser is broken on this version as "net view" gives me error 2184. For my share structure I am thinking in dividing them in departments (groups in this case): - Commercial (/srv/data/commercial) - Finances (/srv/data/finances) - Production (/srv/data/production) - Marketing (/srv/data/marketing) and so on. I can show all departments if needed, I need better ideas anyway, as I can't figure out a way to give read/write access to a single folder per department, if they need to exchange files for some reason. The only thing I've changed in smb.conf from the tutorial was adding "name resolve order" and putting dns as first. Am I going in the right path here? Regards, Flavio Silveira
On Tue, 29 Aug 2017 17:20:06 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote:> Good evening, > > I am trying to setup Samba as file server using this tutorial: > https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_ServerWhy ? your last post was about setting up an AD DC, see here for how to setup a Unix domain member: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member> > The version I am using is 4.6.7 from Van Belle's repo, on Debian > Stretch 9.1. > > I have a server subnet (192.168.13.x) and a client subnet > (192.168.11.x), currently, for testing purposes, the server is on the > same subnet as the clients. Will I have problems if after the tests I > move to the server subnet?No, not if you set up a Unix domain member, in which case you will only need the smb.conf and you can then just reuse this on all your unix machines.> > Clients are Windows 10 x64 build 1703 and it seems Master Browser > is broken on this version as "net view" gives me error 2184. > > For my share structure I am thinking in dividing them in > departments (groups in this case): > > - Commercial (/srv/data/commercial) > > - Finances (/srv/data/finances) > > - Production (/srv/data/production) > > - Marketing (/srv/data/marketing) > > and so on. > > I can show all departments if needed, I need better ideas anyway, > as I can't figure out a way to give read/write access to a single > folder per department, if they need to exchange files for some reason. > > The only thing I've changed in smb.conf from the tutorial was > adding "name resolve order" and putting dns as first.AD relies on dns so there is no need for that line in smb.conf> > Am I going in the right path here?No, probably not, you should set up a Unix domain member instead, by trying to set up a standalone server, you are basically trying to set a workgroup member. If you do go down the 'workgroup' line, you will have to create the groups in AD and on the standalone server, along with ALL the users. Rowland
Hi Rowland, On 29/08/2017 17:55, Rowland Penny via samba wrote:> On Tue, 29 Aug 2017 17:20:06 -0300 > Flávio Silveira via samba <samba at lists.samba.org> wrote: > >> Good evening, >> >> I am trying to setup Samba as file server using this tutorial: >> https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server > Why ? your last post was about setting up an AD DC, see here for how > to setup a Unix domain member: > > https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_MemberI think you are confusing me with someone else, my last post was regarding running AD DC and File Server with the same Samba, no Unix at all. Andrew answered it wasn't recommended, and as I am new, I have decided to focus on the file server only, as it is what I need for now, AD would be a plus.>> The version I am using is 4.6.7 from Van Belle's repo, on Debian >> Stretch 9.1. >> >> I have a server subnet (192.168.13.x) and a client subnet >> (192.168.11.x), currently, for testing purposes, the server is on the >> same subnet as the clients. Will I have problems if after the tests I >> move to the server subnet? > No, not if you set up a Unix domain member, in which case you will only > need the smb.conf and you can then just reuse this on all your unix > machines.I don't have any Unix machine, the only machine I have runs Debian Stretch 9.1.>> Clients are Windows 10 x64 build 1703 and it seems Master Browser >> is broken on this version as "net view" gives me error 2184. >> >> For my share structure I am thinking in dividing them in >> departments (groups in this case): >> >> - Commercial (/srv/data/commercial) >> >> - Finances (/srv/data/finances) >> >> - Production (/srv/data/production) >> >> - Marketing (/srv/data/marketing) >> >> and so on. >> >> I can show all departments if needed, I need better ideas anyway, >> as I can't figure out a way to give read/write access to a single >> folder per department, if they need to exchange files for some reason. >> >> The only thing I've changed in smb.conf from the tutorial was >> adding "name resolve order" and putting dns as first. > AD relies on dns so there is no need for that line in smb.confI don't have an AD, my network is a simple WORKGROUP, and I gave up the idea of setting up both AD and File Server for now as I would need 2 machines, I only have one.> >> Am I going in the right path here? > No, probably not, you should set up a Unix domain member instead, by > trying to set up a standalone server, you are basically trying to set a > workgroup member. > > If you do go down the 'workgroup' line, you will have to create the > groups in AD and on the standalone server, along with ALL the users.So if I don't have an AD, I will just need to create the groups on the standalone server, along with the users, correct? I am guessing the wiki tutorial I am following (Setting up Samba as a Standalone server) is to create a File Server, right? Sorry for all this confusion.> Rowland > >Regards, Flavio Silveira
Hai, If you have a small network, yes, a DC only is not recommended, but if configured correcly it works fine. I see you have only one linux server, so i can assum only windows clients. Then, i say yes, setup an AD DC as fileserver. What i dont understand, yes, everybody even MS tells AD DC as fileserver is not recommended. So why was there a MS SBS servers. ADDC, FILE SERVER, SQL, EXCHANGE. Now you dont want SQL and Exchange on the same server and especialy not on the ADDC but i did deploy lots of them. and if needed sql on separated server. ( most offices i did, did not use MS Sql.) What im trying to say here. If you have a small network, say max 50 users/computer, and not to many groups and nested groups. Running ADDC als fileserver works fine. I install AD DC as of 5-10 computers. The why; it standarizes the setup more, so less problems or problems on all pc's. And in my case much less problems. So yes, setup AD DC, especialy if you have only windows clients. Make life more easy. The hard part, is the learning part if it, ;-) and not running it. Just start simple. But thats just my opinion. Greetz, Louis