[Samba] Traffic going to wrong interface?
aathan-samba-142892 at cloakmail.com
Wed Jan 7 08:09:42 GMT 2004
So, it seems that Windows XP specifies the primary IP address as the source
address of the TCP connection when connecting to \\192.168.2.200 !!??
On linux host netstat -an:
tcp 0 1239 192.168.2.200:139 18.104.22.168:2894
I would have expected this to read
tcp 0 1239 192.168.2.200:139 192.168.2.201:2894
Where 192.168.2.201 is the second ethernet adapter on the windows client.
From: greg at calibredigital.com [mailto:greg at calibredigital.com]
Sent: Tuesday, January 06, 2004 1:17 PM
To: Andrew Athan
Cc: samba at lists.samba.org
Subject: Re: [Samba] Traffic going to wrong interface?
assuming you are using linux:
Have you tried the below GLOBAL setting?
interfaces = 172.16.92.245
This asks samba to listen on that interface only, I don't know if it
will also force samba to use this interface as the source for any
Making the gigabit interface your primary interface may also work.
You might be able to kludge this from within the /etc/modules.conf file
if you are using modules to drive the cards.
alias eth0 tg3
alias eth1 e100
Then there is the route method. you can add static routes to the
client. Host routes are honored over network routes. I'd use this as a
last resort, it seems wrong.
route add -host 172.16.92.245 eth0
I have a few more but I think one of these might work. good luck with
Andrew Athan wrote:
> If I connect via \\gige.ethernet.address\foo , and copying a large file,
> windows reports outbound traffic on the gige port and return traffic on
> 100Meg port.
> Thus, it seems the samba server sees the client->server traffic via gige
> is responding via the slower interface. Not what I want.
UNIX is user friendly, it's just selective about who its friends are.
More information about the samba