[Samba] nmblookup -B localhost __SAMBA__ failing on samba-2.2.3a

GHCebulka at uss.com GHCebulka at uss.com
Wed Mar 27 12:16:04 GMT 2002


Joseph,
     I have the following entries in the /etc/services file. I start nnbd
and smbd via a startup script in init.d. Swat is started from inetd.conf
though.
/etc/servcies entries
netbios-ssn         139/tcp   # Samba ServicePorts
netbios-ns          137/udp   # Samba Service Port
swat           901/tcp   # SWAT - Admin tool for samba

/etc/inetd.conf entry
# samba-2.2.3a
swat stream tcp nowait root /usr/local/samba/sbin/swat swat

    I am assuming that this is what you mean. Nmbd, smbd and swat seem to
work fine. Howerver, nmbd will not answer on the localhost address. Which
is odd. Does samba even need to be able to talk to itself over the the
localhost address?
     George

Message: 5
Date: Wed, 27 Mar 2002 07:39:27 -0800
From: Joseph Loo <jloo at acm.org>
To: samba list <samba at lists.samba.org>
Subject: Re: [Samba] nmblookup -B localhost __SAMBA__ failing on
samba-2.2.3a

Have you added the entries in the inet and services entries?

GHCebulka at uss.com wrote:

>Server:   Samba-2.2.3a
>OS:  Solaris 2.7
>
>nmbd is failing to start from swat. After looking through the source code
I
>found that swat uses  "nmblookup -B 127.0.0.1 __SAMBA__" command to
>determing whether nmbd is running or not.
>#nmblookup -B localhost __SAMBA__
>querying __SAMBA__ on 127.0.0.1
>name_query failed to find name __SAMBA__
>
>However, nmbd is running and I can see/use shares on my MS machines. When
I
>run nmblookup -B azure __SAMBA__, it works fine.
>#nmblookup -B azure __SAMBA__
>querying __SAMBA__ on 170.191.20.27
>170.191.20.27 __SAMBA__<00>
>
>What am I doing wrong here????
>I've included the output from ifconfig -a and my smb.conf file.
>Any help would be great,
>     Thanks in advance,
>     George Cebulka
>
>ifconfig -a
>lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232        inet
>127.0.0.1 netmask ff000000
>hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
>inet 170.191.20.27 netmask ffffff80 broadcast 170.191.20.127        ether
>8:0:20:a3:68:6d
>hme0:1: flags=843<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500        inet
>170.191.20.33 netmask ffffff80 broadcast 170.191.20.127
>qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
>inet 170.191.21.11 netmask ffffff80 broadcast 170.191.21.127        ether
>8:0:20:c8:8b:18 root at azure /usr/local/samba/bin
>
># Samba config file created using SWAT
># from pltsups-d548127 (170.191.24.84)
># Date: 2002/03/26 16:09:40
>
># Global parameters
>[global]
>           workgroup = HDQ
>           netbios aliases = azure.psc.uss.com
>           security = DOMAIN
>           encrypt passwords = Yes
>           min passwd length = 6
>           password server = *
>           username map = /usr/local/samba/lib/username.map
>           log level = 5
>           max log size = 1000
>           name resolve order = wins bcast host
>           os level = 0
>           preferred master = False
>           domain master = False
>           wins server = 170.191.250.78
>           admin users = @samba
>           create mask = 0775
>           directory mask = 0775
>           hosts allow = 170.191.,10.16.,localhost
>
>[clearcase]
>           comment = ClearCase test install
>           path = /products/ccase/cc_storage
>           valid users = cc_albd, at cc_ecd, at cc_ecq, at cc_azd, at cc_azq, at clearcas
>           read only = No
>
>[samba]
>           path = /usr/local/samba
>           valid users = @samba
>           read only = No
>
>
>

--
Joseph Loo
jloo at acm.org







More information about the samba mailing list