Samba file sharing

SearchMaster

Diamond Member
Jun 6, 2002
7,791
114
106
I am setting up a ClarkConnect linux box primarily to serve as a content filter/proxy server for my young sons' computers. However, I would also like to use it as a file server to replace an existing file server on my network.

My original network is 192.168.0.x and most of the computers are on it, and it is the network exposed to the DSL modem, and eth1 for my linux box. The new network is 192.168.2.x, which is eth0 for my linux box. I set up Samba today and got everything working on the 192.168.2.x side, but I can't get the 192.168.0.x network to see the file shares.

In my smb.conf file, there is a line "interfaces = lo eth0". If I put "interfaces = lo eth0 eth1" there instead and restart Samba, it removes the eth1 and goes back to the original configuration.

Any ideas? I'm not terribly proficient at Linux but I've done a bit here and there before.
 

xSauronx

Lifer
Jul 14, 2000
19,582
4
81
Samba config file

search the page for "subnet" and get reading. this seems to be most relevant:
Networking Options with Samba

If you're running Samba on a multihomed system (on multiple subnets), you will need to configure Samba to use all the network interfaces. Another use for the options presented in this section is to implement better security by allowing or disallowing connections on the specified interfaces.

Let's assume that our Samba server can access both the subnets 192.168.220.* and 134.213.233.*. Here are our additions to the configuration file to add the networking configuration options:

[global]
# Networking configuration options
hosts allow = 192.168.220. 134.213.233.
hosts deny = 192.168.220.102
interfaces = 192.168.220.100/255.255.255.0
134.213.233.110/255.255.255.0
bind interfaces only = yes

without looking at it *too* closely, i would expect this to cover what youre interested in
 

SearchMaster

Diamond Member
Jun 6, 2002
7,791
114
106
Thanks but no dice.

When I try to replace "interfaces = lo eth0" with "interfaces = 192.168.2.1/255.255.255.0 192.168.0.34/255.255.255.0" and restart Samba, it overwrites that line with the previous value.
 

SearchMaster

Diamond Member
Jun 6, 2002
7,791
114
106
I found the solution to the overwriting problem - it was "automagic"ally rewriting it for me so I turned automagic off.

Now I need to figure out how to open the smb ports in the firewall - I *think* that's the only thing keeping me out now.
 

SearchMaster

Diamond Member
Jun 6, 2002
7,791
114
106
Solved - removing the automagic script along with opening samba-related ports in the firewall solved the problem.