samba - Jun 1999 - Urgent: multiple NIC

Hi,

I have a NT Workstation with SP4 and 3 network interfaces. I use ATM
over IP, so two of my interfaces are CLIP.
CLIP is ip over atm, so the only problem for samba would be no
broadcasts in atm interfaces.

I also have a Linux Box (RedHat 2.2.1 with samba 2.0.2) with 3
interfaces for the same networks as my PC.

It looks something like this:

              -Linux Box-          -NT Box-
(atm)         192.168.28.96        192.168.28.128
(atm)         192.168.26.96        192.168.26.128
(ethernet)    194.117.24.96        194.117.24.128

If I map a network drive in my NT for the 192.168.26.96 Linux interface
(using the ip not a netbios name or any other name) I get traffic in the
other interfaces.

Using tcpdump on the interface associated with 192.168.26.96 (atm1) on
the Linux Box I only get traffic flowing from

    194.117.24.128 --> 192.168.26.96
    ^^^^^^^^^^^^^^
If I try a file transfer the data comes from

    192.168.26.96 --> 194.117.24.128
                      ^^^^^^^^^^^^^^
on the interface for ethernet (eth0).

If unplug the ethernet cable the transfer is interrupted. Sometimes I
pick up the transfer on the other atm interface.

I've tryed to use lmhosts to name my NT Box and the Linux Box (added
192.168.28.128 myBox    #PRE
192.168.26.96  linuxBox26 #PRE
192.168.28.96  linuxBox28 #PRE
)
but that didn't help. Also put
    domain master = yes
    wins support = yes
    wins proxy = yes
on the smbd.conf in my Linux, with the same negative results.

Imho, the problem is that there's no association between the netbios
name (and ip) of the server machine and the interface used by the client
machine. The samba client connects to the correct ip, but listen in any
interface.

If there is a way to associate the ip/name with the correct network,
i.e., making the connetion on only one network, please let me know.

Thanks in advance for any pointer that will help me.

Carlos

I have a nagging problem with Samba 2.0.4 running on an Enterprise
250/Solaris 7 server. Users' print jobs queue up and print correctly and
then, without warning, the jobs just stop. The samba logs indicate no
problem, the jobs queue, print and are removed. But no output is
generated. So far my solution has been to stop, then start, the nmb/smb
services. But this is after the users start screaming. Anybody have a
similar experience or a fix?

Bob Rohde