[Samba] Do I need two instances of Samba on the same machine (3rd request) ?

Dani Camps danicamps81 at yahoo.com
Thu Mar 10 12:22:59 GMT 2005


I already have all the clients in both subnets
configured to use WINS and configured to be a p-node.
These are my lines in the DHCP server:
-----------------------------------------------------
option netbios-name-servers 192.168.0.1;
option netbios-node-type 2;
-----------------------------------------------------

I rewrite my configuration to check whether I have
some error:
                     INTERNET
                        |
                     __eth1__
      |---------eth0|_______|eth2---------|
192.168.0.0/24         Gateway         192.168.1.0/24

       <------------------------------------>
                     WORKGROUP

eth0:192.168.0.1 and gateway of the 192.168.0.0/24
eth2:192.168.1.1 and gateway of the 192.168.1.0/24
eth1:public IP, doing NAT of the internal subnets

The Gateway is a Fedora Core 3 box where I have Samba
installed. I have Samba configured to be a WINS server
in that machine.

What I have now and it doesn't work is the following:
In the gateway machine I have one instance of Samba
running with this configuration:
-----------------------------------------------------
hosts allow=127. 192.168.0. 192.168.1.
...
socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
...
interfaces=192.168.0.1/24 192.168.1.1/24 127.0.0.1/8
bind interfaces only=yes
...
#To be the DMB
domain master = yes
local master = yes
os level = 255
preferred master = yes
...
#To be the WINS server
name resolve order = wins lmhosts bcast
wins support = yes
dns proxy = no
------------------------------------------

I know I need to make what I want work:
1-One LMB in each subnet
2-One DMB
3-One WINS server and all the clients using WINS

This is why I thought in having two Samba servers in
the gateway machine one binded to each interface
(eth0,eth2), and one of them being the DMB and WINS.
Because it seems that with only one Samba instance in
that machine it doesn't work.

What happens now is the following, the SMB networking
within the 192.168.0.0 network works perfect, but they
only see themselves. And the machines in the
192.168.1.0 can not even open the network neigbourhood
because there is an error (error 53 doing net view).
But IP routing works between the two subnets, I have
checked the ping between machines in the two subnets,
and I have no Firewall rule filetring traffic between
the two subnets. So i don't have any idea about what
could be failing.

Thanks !




--- Adam Tauno Williams <awilliam at whitemice.org>
wrote:
> > > Run one Samba instance as the WINS server and
> > > disable browsing on the
> > > clients (easy if the Samba server is also the
> DHCP
> > > server).
> > The machine that is in the two subnets is a Samba
> > server (one instance) a WINS server and a DHCP
> server,
> > but is not working actually only the clients in
> one
> > subnet see each other, the clients in the other
> subnet
> > don't see anything. And I have checked that the
> > instance of Samba is listening on both subnets.
> > What do u mean with disable the browsing in the
> > clients ? I want the clients to be able to browse
> the
> > workgroup
> 
> Browsing and the ability-to-browse (network
> neighborhood) are two
> different things.  Change the NetBIOS node type of
> the workstations so
> they only use WINS and make sure they have the WINS
> server value in
> their network configuration (either statically or
> acquired by DHCP).  If
> you don't know what the NetBIOS Node Type is then
> you need to read up on
> it, or you'll never get this to work.
> 
> If this box is supposed to be the router between the
> two subnets make
> sure basic IP functionality is up and running first;
> a box on one subnet
> can ping a box on the other subnet.
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


More information about the samba mailing list