[Samba] Configuring a samba server with two NICs

Hi all,

I am trying hard to configure samba, but I can not achieve my goals.
Other than standard man pages, I have seen also many posts/documents
samba with multiple nics, but I couldn' find any relevant to me.

So, please, let me explain my settings and what I am looking to set up.

First of all, my desktop runs ubuntu 8.04 with samba 3.0.28a
On the pc I have 2 nics, eth0 and eth1.
eth1 has address 10.80.2.121
eth0 has address 192.168.23.1

The network on eth1 is a company network, with many windows/unix pcs
on it and a wins server at the address 192.167.219.2.

The network on eth0 is a small private network, in the sense that I attach
to it only my laptop with a crossed cable and I use the desktop to share
network and services with the laptop. The laptop is an eeepc900 with its
Xandros default distribution and samba 3.0.24-6, with the default smb.conf
(I include at the end of the message the result of
cat smb.conf | egrep -v "^(#|;| *$)"
on the eeepc)

I want to share a directory (/media/matematica/libri) and I want that it
is possible to have (free but readonly) access to it only from a bunch of
trusted pcs: the one attached at eth0 (192.168.23.)
and two on the eth1 (10.80.2.196 10.80.2.72), plus myself (10.80.2.121)
Finally, at least on the eth1 network, I want to be part of the workgroup
"DOCENTI".

Summing this up, I wrote the following smb.conf on my desktop:

[global]
wins server = 192.167.219.2
domain master = no
local master = no
workgroup = DOCENTI
server string = Stumbo
hosts deny = ALL
hosts allow = 192.168.23. 10.80.2.121 10.80.2.196 10.80.2.72 127.0.0.1
security = share
[libri]
guest ok = yes
path = /media/matematica/libri
read only = yes

It works partially, in the sense that all is ok on eth1: I am part of the
workgroup DOCENTI, the trusted pcs can access the shared dir, whereas all
others can't (I would also like to be invisible to the others, but I don't
think this is possible...)

On the other hand, from the laptop side I can't see my desktop: what
should I do in order to see the shared dir also from the laptop?

Thanks a lot for your help

Fabio

--------------------------------------
cat smb.conf | egrep -v "^(#|;| *$)"

[global]
include = /etc/opt/xandros/xandrosncs/run/samba_wins
workgroup = WORKGROUP
server string = %h server (Asus Eee PC)
dns proxy = no
name resolve order = lmhosts host wins bcast
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = share
encrypt passwords = true
passdb backend = tdbsam
ldap delete dn = yes
obey pam restrictions = yes
invalid users = root
map to guest = Bad User
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n
*password\supdated\ssuccessfully* .
client use spnego = no
load printers = no
printing = cups
printcap name = cups
socket options = TCP_NODELAY
dos filetimes = yes
display charset = UTF8
unix charset = UTF8
unix extensions = no


-------------------------------

the included file in smb.conf contains
wins server = 192.167.219.2

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

> -----Original Message-----
> From: samba-bounces+dmcleod=foranyauto.com@lists.samba.org
> [mailto:samba-bounces+dmcleod=foranyauto.com@lists.samba.org]
> On Behalf Of Fabio
> Sent: Friday, June 13, 2008 3:22 AM
> To: samba@lists.samba.org
> Subject: [Samba] Configuring a samba server with two NICs




FWIW, there was just a discussion on the Dell Server list trying to use a
crossover between two recent Dell servers.
It DIDN'T work.
A normal network cable did.
Seems that some modern cards a suppose to auto-configure, but in this case
it didn't work with a crossover.

http://article.gmane.org/gmane.linux...oweredge/32995


Can you at least PING it?
Dennis

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

>
> FWIW, there was just a discussion on the Dell Server list trying to use a
> crossover between two recent Dell servers.
> It DIDN'T work.
> A normal network cable did.
> Seems that some modern cards a suppose to auto-configure, but in this case
> it didn't work with a crossover.
>
All gigabit devices auto crossover so no crossover is necessary if
both sides are gigabit. I am not sure this is the problem though. It
looks like ipv4 forwarding needs to be turned on on the machine that
has 2 nics. However I may be wrong as I was a little confused with the
discussion of the two networks and their purpose.

John
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

>> FWIW, there was just a discussion on the Dell Server list trying to use a
>> crossover between two recent Dell servers.
>> It DIDN'T work.
>> A normal network cable did.
>> Seems that some modern cards a suppose to auto-configure, but in this case
>> it didn't work with a crossover.
>>
> All gigabit devices auto crossover so no crossover is necessary if
> both sides are gigabit. I am not sure this is the problem though. It
> looks like ipv4 forwarding needs to be turned on on the machine that
> has 2 nics.

None of the 2 nics is a gigabit... :-((

> However I may be wrong as I was a little confused with the
> discussion of the two networks and their purpose.

Maybe I didn't explain well myself, sorry.

My principal aim is simply to share the same directory over the two
networs: everything else is unessential. They can also be invisible to each
other.
What I got with my config is that my shared dir is accessible on eth1 (where
I just allow 3 IPs), but it is not on eth0 (my laptop).

Thanks

Fabi
Thanks

Fabio

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

> FWIW, there was just a discussion on the Dell Server list trying to use a
> crossover between two recent Dell servers.
> It DIDN'T work.
> A normal network cable did.
> Seems that some modern cards a suppose to auto-configure, but in this case
> it didn't work with a crossover.
>
> http://article.gmane.org/gmane.linux...oweredge/32995
>
>
> Can you at least PING it?
> Dennis

Sorry, I forgot to answer this.

If I configure samba to listen only on eth0 (my laptop connected via a
crossover cable), then I can access the shared dir.

If that matters, I also configured ip masquerading so that from the laptop
I can access the internet via the desktop.

Fabio

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

On Fri, Jun 13, 2008 at 4:59 PM, Fabio <egalua@hotmail.com> wrote:
>> FWIW, there was just a discussion on the Dell Server list trying to use a
>> crossover between two recent Dell servers.
>> It DIDN'T work.
>> A normal network cable did.
>> Seems that some modern cards a suppose to auto-configure, but in this case
>> it didn't work with a crossover.
>>
>> http://article.gmane.org/gmane.linux...oweredge/32995
>>
>>
>> Can you at least PING it?
>> Dennis
>
> Sorry, I forgot to answer this.
>
> If I configure samba to listen only on eth0 (my laptop connected via a
> crossover cable), then I can access the shared dir.
>
> If that matters, I also configured ip masquerading so that from the laptop
> I can access the internet via the desktop.
>

Are you trying to access samba on the laptop using the ipaddress of
the samba server?

John
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

>>> Can you at least PING it?
>>> Dennis
>>
>> Sorry, I forgot to answer this.
>>
>> If I configure samba to listen only on eth0 (my laptop connected via a
>> crossover cable), then I can access the shared dir.
>>
>> If that matters, I also configured ip masquerading so that from the laptop
>> I can access the internet via the desktop.
>>
>
> Are you trying to access samba on the laptop using the ipaddress of
> the samba server?

No: I am trying to access it using a file manager.
When I will be back at office, on monday, I will try also using the
ipaddress.

Fabio

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

> No: I am trying to access it using a file manager.
> When I will be back at office, on monday, I will try also using the
> ipaddress.
>
I meant using file manager. Instead of clicking on network
neighborhood or typing the name try the full unc path of the share
using the ipadress instead of the name. If that does not work turn off
the ipaddress restrictions and see if it works that way.

I know samba works with multiple networks because at work we have a
gigabit network and a 100mbit one as well. And both networks connect
to several of the samba servers and the clients on either side can use
the shares fine.

John
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

Most of my samba servers have had four NICs in them for at least a
decade. Several have six.

--Charlie

On Sat, Jun 14, 2008 at 4:55 AM, John Drescher <drescherjm@gmail.com> wrote:
>> No: I am trying to access it using a file manager.
>> When I will be back at office, on monday, I will try also using the
>> ipaddress.
>>
> I meant using file manager. Instead of clicking on network
> neighborhood or typing the name try the full unc path of the share
> using the ipadress instead of the name. If that does not work turn off
> the ipaddress restrictions and see if it works that way.
>
> I know samba works with multiple networks because at work we have a
> gigabit network and a 100mbit one as well. And both networks connect
> to several of the samba servers and the clients on either side can use
> the shares fine.
>
> John
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba