smbclient using all interfaces

Tim Winders twinders at
Tue Feb 16 14:40:08 GMT 1999

On Tue, 16 Feb 1999, Christopher R. Hertel wrote:

> Try dropping only 139.  The -L option (if I remember correctly) connects 
> to port 139 on the remote end.  If it *does* work, then the problem was 
> name resolution packets not getting through.

OK, Chris.  I have re-applied the filter with only port 139 being blocked
and I see this:

twinders> smbclient -L atc-srv
Added interface ip= bcast= nmask=
Added interface ip= bcast= nmask=
Added interface ip= bcast= nmask=
Added interface ip= bcast= nmask=
Got a positive name query response from ( )

and it just hangs.  You can see that it is using the loopback address for
WINS resolution, so the filter doesn't matter.

I can only deduce that there is a kernel/routing something problem.  Using
TCPdump looking at the first interface above.  When I try to ping the
remote station indicated above, I see nothing.  If I look at the ethernet
interface (, which is not listed in the interfaces option in
smb.conf) and I ping the station above, I see the pings across that

When I remove the filter from the router, the above command works and I
see the packets (with tcpdump) going over the ethernet interface, not over
one of the interfaces above...

=== Tim

|  Tim Winders, CNE, MCSE     |  Email:  Tim.Winders at   |
|  Network Administrator      |  Phone:  806-894-9611 x 2369        |
|  South Plains College       |  Fax:    806-897-4711               |
|  Levelland, TX  79336       |                                     |

More information about the samba-technical mailing list