I have a samba server with 2 ethernet ports, one of which is a gigabit port. When connecting from a windows client that has a crossover to the gigabit port, and a crossover to the 100Meg port: 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 the 100Meg port. Thus, it seems the samba server sees the client->server traffic via gige but is responding via the slower interface. Not what I want. Any clues? Thanks, A.
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 outbound connections. 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 it. peace. 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 the > 100Meg port. > > Thus, it seems the samba server sees the client->server traffic via gige but > is responding via the slower interface. Not what I want.-- UNIX is user friendly, it's just selective about who its friends are.