Hi-
Ok, this is puzzling me. I have two machines on different networks
running Samba 1.9.18p10. On one machine, which is running Redhat 5.1, I
can do "nmblookup -A <IP ADDRESS>" and get the IP address of a
host on
the LAN. This network also has an NT server domain controller, but I
doubt that matters in this case, since I'm querying the machine
directly.
The second machine is running Slackware 3.2. The same command, on that
machine, does not work except when querying the Samba server itself.
All other machines give a "No status response" error. Here is some
debugging output from that. The machine being queried is running Win95.
Also, any insight into the lp_servicenumber messages would be
appreciated.
monm:/admin/samba/var> nmblookup -d 9 -A 207.63.36.220
Initialising global parameters
params.c:pm_process() - Processing configuration file
"/admin/samba/lib/smb.conf
"
Processing section "[global]"
doing parameter workgroup = MHS
doing parameter server string = Monm
doing parameter load printers = yes
doing parameter log file = /admin/samba/var/log.%m
doing parameter max log size = 50
doing parameter security = user
doing parameter socket options = TCP_NODELAY
doing parameter interfaces = 207.63.36.200/24 10.0.0.1/21
doing parameter remote announce = 207.63.36.255 10.0.7.255
doing parameter dns proxy = no
pm_process() returned Yes
lp_servicenumber: couldn't find homes
lp_servicenumber: couldn't find printers
lp_servicenumber: couldn't find printers
adding IPC service
Added interface ip=207.63.36.200 bcast=207.63.36.255 nmask=255.255.255.0
Added interface ip=10.0.0.1 bcast=10.0.7.255 nmask=255.255.248.0
bind succeeded on port 0
Socket opened.
Sending queries to 207.63.36.255
Looking up status of 207.63.36.220
nmb packet from 207.63.36.220(137) header: id=6484 opcode=Query(0)
response=No
header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=*<00> q_type=33 q_class=1
1998/10/22 17:08:11 sending a packet of len 50 to (207.63.36.220) on
port 137
nmb packet from 207.63.36.220(137) header: id=6484 opcode=Query(0)
response=No
header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=*<00> q_type=33 q_class=1
1998/10/22 17:08:16 sending a packet of len 50 to (207.63.36.220) on
port 137
No status response (this is not unusual)
Please CC replies by email as I'm not on the list. Thanks!
--
-Brian Ryner
bryner@uiuc.edu
Brian Ryner wrote:> > Hi- > > Ok, this is puzzling me. I have two machines on different networks > running Samba 1.9.18p10. On one machine, which is running Redhat 5.1, I > can do "nmblookup -A <IP ADDRESS>" and get the IP address of a host on > the LAN. This network also has an NT server domain controller, but I > doubt that matters in this case, since I'm querying the machine > directly. > > The second machine is running Slackware 3.2. The same command, on that > machine, does not work except when querying the Samba server itself. > All other machines give a "No status response" error. Here is some > debugging output from that. The machine being queried is running Win95. > Also, any insight into the lp_servicenumber messages would be > appreciated. >If your machine is running nmbd you will get the "No status response" from Win95 machines and will get responses from Win98 and WinNT. This is because Win95 will not respond to anything but port 137. Since nmbd is already bound to that port you will not receive the response. You can kill nmbd temporarily if you want to use nmblookup with Win95 machines. -- =====================================================================Herb Lewis Silicon Graphics Technical Marketing 2011 N Shoreline Blvd Network Systems Division Mountain View, CA 94043 herb@sgi.com Tel: 650-933-2177 http://www.sgi.com Fax: 650-932-2177 ======================================================================