All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael <mutk@iprimus.com.au>
To: Dan Egli <dan@shortcircuit.dyndns.org>, netfilter@lists.netfilter.org
Subject: Re: Samba blocked?
Date: Wed, 27 Nov 2002 11:14:23 +1000	[thread overview]
Message-ID: <3DE41C6F.2050704@iprimus.com.au> (raw)
In-Reply-To: 000d01c2958f$d3fadbd0$1e00a8c0@yamatto

Dan Egli wrote:

>Ok. I'm a fair bit confused here. I'm trying to setup a IPtables filter set
>that will block certain ports and allow others. It seems to work perfectly
>for anything other than Samba. If I try:
>
>smbclient //myserver/shared1, it fails to connect. But using the IP in place
>of it:
>smbclient //192.168.0.2/shared1 works just fine. I am specifically allowing
>NetBIOS-ns, NetBIOS-ssn, and NetBIOS-dgm. Still no go. What's wrong?
>
>  
>


Probably nothing wrong with the iptables rules. Might be something wrong 
with the name lookups for smbclient though.
Have a look at man pages for smbclient, in particular the name resolve 
order (-R) command switch. Also have a look at man page for smb.conf, 
 as the method for name look ups is defined there (The order too)

The default order is lmhosts, host, wins, bcast for name look ups.  
I beleive that for bcast name lookups to work you need to allow bcast 
traffic too. ie you need to allow 192.168.0.255 port 137.

If you don't want that, a quick fix is to try adding the 'myserver'  
name and IP to /etc/hosts ..

Cheers,
Michael





  parent reply	other threads:[~2002-11-27  1:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 21:05 Samba blocked? Dan Egli
2002-11-27  0:00 ` Robert Wideman
2002-11-27  1:14 ` Michael [this message]
2002-11-27  2:31   ` Dan Egli
2002-11-27  3:12     ` Michael
2002-11-27  2:41   ` Dan Egli
2002-11-27  3:22     ` Michael
2002-11-27  3:53       ` Dan Egli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DE41C6F.2050704@iprimus.com.au \
    --to=mutk@iprimus.com.au \
    --cc=dan@shortcircuit.dyndns.org \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.