lmhosts lookup question

[GL Fournerat]

You didn't mention this.. so I thought I would bring it
up...

The lmhost file on that Samba PDC needs to be in the same
directory as your smb.conf file.  Is it?

Gary



Michael Blinn wrote:

> Hello everyone! I'm having trouble doing NetBIOS lookups
> from my samba PDC. Here's the scoop: 1 samba PDC
> controlling a domain named CVILLE on subnet
> 192.168.168.0/24 1 samba PDC controlling a domain named
> MAIN on subnet 192.168.169.0/24    1 NTServer,
> 192.168.168.3, (Not a PDC or BDC) that shares files  The
> two domains are connected with a VPN using tcp/ip only,
> and routes are fine. lmhosts file in
> /usr/local/samba/lib/lmhosts on both samba PDCs AND on
> NTServer: 192.168.168.2     mail
> 192.168.168.3     ntserver
> 192.168.168.2     "MAIN           \0x1c"     #PRE
> 192.168.168.2     "MAIN           \0x1b"     #PRE
> 192.168.169.2     cvserver
> 192.168.169.2     "CVILLE         \0x1c"     #PRE
> 192.168.169.2     "CVILLE         \0x1b"     #PRE  I want
> CVILLE and MAIN to remote sync and allow MAIN to be the
> WINS server, so the applicable entries in each smb.conf
> are: MAIN:wins support = yesname resolve order = lmhosts
> bcast CVILLE:wins server = 192.168.168.2name resolve order
> = lmhosts bcast  When I fire everything up: 1:  NT server
> claims that "No logon server is available" and does not
> allow incoming connections to shares2:   When I do
> "nmblookup ntserver" from domain CVILLE it cannot resolve
> (on 192.168.169.255) Questions: 1:   Is there a way to
> check to see why (if?) samba isn't looking in lmhosts for
> resolution first?2:   After I get this working, do I need
> to specifically set the "WINS Server" on my Win9* boxes
> for resolution from client machines?3:   Could my firewall
> (chains WIDE open for initial testing, ipchains -L below)
> be blocking udp traffic between PDCs?4:   Can Bush really
> get it done?  Any help is greatly appreciated, Michael
> Blinn IT Dude People Places, Inc.  Chain input (policy
> ACCEPT):
> target     prot opt     source
> destination           ports
> ACCEPT     all  ---f--  anywhere
> anywhere              n/a
> acctin     all  ------  anywhere
> anywhere              n/a
> acctboth   all  ------  anywhere
> anywhere              n/a
> inp        all  ------  anywhere
> anywhere              n/a
> Chain forward (policy ACCEPT):
> target     prot opt     source
> destination           ports
> MASQ       tcp  ------  localnet/24
> anywhere              any ->   any
> MASQ       tcp  ------  192.168.169.0/24
> anywhere              any ->   any
> ACCEPT     all  ---f--  anywhere
> anywhere              n/a
> fwd        all  ------  anywhere
> anywhere              n/a
> Chain output (policy ACCEPT):
> target     prot opt     source
> destination           ports
> DENY       all  ------  anywhere
> 199.95.207.0/24       n/a
> ACCEPT     all  ---f--  anywhere
> anywhere              n/a
> acctout    all  ------  anywhere
> anywhere              n/a
> acctboth   all  ------  anywhere
> anywhere              n/a
> out        all  ------  anywhere
> anywhere              n/a
> Chain acctin (1 references):
> Chain acctout (1 references):
> Chain acctboth (2 references):
> Chain inp (1 references):
> Chain out (1 references):
> Chain fwd (1 references):
> target     prot opt     source
> destination           ports
> ACCEPT     all  ------  cvserver.peopleplaces.org
> localnet/24           n/a
> ACCEPT     all  ------  localnet/24
> cvserver.peopleplaces.org  n/a
> ACCEPT     all  ------  192.168.169.0/24
> localnet/24           n/a
> ACCEPT     all  ------  localnet/24
> 192.168.169.0/24      n/a
> Chain IpFwAdM! (0 references):
> target     prot opt     source
> destination           ports
> -          all  ------  anywhere
> anywhere              n/a
> -          all  ------  anywhere
> anywhere              n/a