1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<refentry id="nmblookup">
<refmeta>
<refentrytitle>nmblookup</refentrytitle>
<manvolnum>1</manvolnum>
</refmeta>
<refnamediv>
<refname>nmblookup</refname>
<refpurpose>NetBIOS over TCP/IP client used to lookup NetBIOS
names</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>nmblookup</command>
<arg choice="opt">-M</arg>
<arg choice="opt">-R</arg>
<arg choice="opt">-S</arg>
<arg choice="opt">-r</arg>
<arg choice="opt">-A</arg>
<arg choice="opt">-h</arg>
<arg choice="opt">-B <broadcast address></arg>
<arg choice="opt">-U <unicast address></arg>
<arg choice="opt">-d <debug level></arg>
<arg choice="opt">-s <smb config file></arg>
<arg choice="opt">-i <NetBIOS scope></arg>
<arg choice="opt">-T</arg>
<arg choice="opt">-f</arg>
<arg choice="req">name</arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1>
<title>DESCRIPTION</title>
<para>This tool is part of the <citerefentry><refentrytitle>Samba</refentrytitle>
<manvolnum>7</manvolnum></citerefentry> suite.</para>
<para><command>nmblookup</command> is used to query NetBIOS names
and map them to IP addresses in a network using NetBIOS over TCP/IP
queries. The options allow the name queries to be directed at a
particular IP broadcast area or to a particular machine. All queries
are done over UDP.</para>
</refsect1>
<refsect1>
<title>OPTIONS</title>
<variablelist>
<varlistentry>
<term>-M</term>
<listitem><para>Searches for a master browser by looking
up the NetBIOS name <replaceable>name</replaceable> with a
type of <constant>0x1d</constant>. If <replaceable>
name</replaceable> is "-" then it does a lookup on the special name
<constant>__MSBROWSE__</constant>.</para></listitem>
</varlistentry>
<varlistentry>
<term>-R</term>
<listitem><para>Set the recursion desired bit in the packet
to do a recursive lookup. This is used when sending a name
query to a machine running a WINS server and the user wishes
to query the names in the WINS server. If this bit is unset
the normal (broadcast responding) NetBIOS processing code
on a machine is used instead. See RFC1001, RFC1002 for details.
</para></listitem>
</varlistentry>
<varlistentry>
<term>-S</term>
<listitem><para>Once the name query has returned an IP
address then do a node status query as well. A node status
query returns the NetBIOS names registered by a host.
</para></listitem>
</varlistentry>
<varlistentry>
<term>-r</term>
<listitem><para>Try and bind to UDP port 137 to send and receive UDP
datagrams. The reason for this option is a bug in Windows 95
where it ignores the source port of the requesting packet
and only replies to UDP port 137. Unfortunately, on most UNIX
systems root privilege is needed to bind to this port, and
in addition, if the <citerefentry><refentrytitle>nmbd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> daemon is running on this machine it also binds to this port.
</para></listitem>
</varlistentry>
<varlistentry>
<term>-A</term>
<listitem><para>Interpret <replaceable>name</replaceable> as
an IP Address and do a node status query on this address.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-h</term>
<listitem><para>Print a help (usage) message.</para></listitem>
</varlistentry>
<varlistentry>
<term>-B <broadcast address></term>
<listitem><para>Send the query to the given broadcast address. Without
this option the default behavior of nmblookup is to send the
query to the broadcast address of the network interfaces as
either auto-detected or defined in the <ulink
url="smb.conf.5.html#INTERFACES"><parameter>interfaces</parameter>
</ulink> parameter of the <citerefentry><refentrytitle>smb.conf</refentrytitle>
<manvolnum>5</manvolnum></citerefentry> file.
</para></listitem>
</varlistentry>
<varlistentry>
<term>-U <unicast address></term>
<listitem><para>Do a unicast query to the specified address or
host <replaceable>unicast address</replaceable>. This option
(along with the <parameter>-R</parameter> option) is needed to
query a WINS server.</para></listitem>
</varlistentry>
<varlistentry>
<term>-d <debuglevel></term>
<listitem><para>debuglevel is an integer from 0 to 10.</para>
<para>The default value if this parameter is not specified
is zero.</para>
<para>The higher this value, the more detail will be logged
about the activities of <command>nmblookup</command>. At level
0, only critical errors and serious warnings will be logged.</para>
<para>Levels above 1 will generate considerable amounts of
log data, and should only be used when investigating a problem.
Levels above 3 are designed for use only by developers and
generate HUGE amounts of data, most of which is extremely cryptic.</para>
<para>Note that specifying this parameter here will override
the <ulink url="smb.conf.5.html#LOGLEVEL"><parameter>
log level</parameter></ulink> parameter in the <filename>
smb.conf(5)</filename> file.</para></listitem>
</varlistentry>
<varlistentry>
<term>-s <smb.conf></term>
<listitem><para>This parameter specifies the pathname to
the Samba configuration file, <ulink url="smb.conf.5.html">
smb.conf(5)</ulink>. This file controls all aspects of
the Samba setup on the machine.</para></listitem>
</varlistentry>
<varlistentry>
<term>-i <scope></term>
<listitem><para>This specifies a NetBIOS scope that
<command>nmblookup</command> will use to communicate with when
generating NetBIOS names. For details on the use of NetBIOS
scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes are
<emphasis>very</emphasis> rarely used, only set this parameter
if you are the system administrator in charge of all the
NetBIOS systems you communicate with.</para></listitem>
</varlistentry>
<varlistentry>
<term>-T</term>
<listitem><para>This causes any IP addresses found in the
lookup to be looked up via a reverse DNS lookup into a
DNS name, and printed out before each</para>
<para><emphasis>IP address .... NetBIOS name</emphasis></para>
<para> pair that is the normal output.</para></listitem>
</varlistentry>
<varlistentry>
<term>-f</term>
<listitem><para>
Show which flags apply to the name that has been looked up. Possible
answers are zero or more of: Response, Authoritative,
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
</para></listitem>
</varlistentry>
<varlistentry>
<term>name</term>
<listitem><para>This is the NetBIOS name being queried. Depending
upon the previous options this may be a NetBIOS name or IP address.
If a NetBIOS name then the different name types may be specified
by appending '#<type>' to the name. This name may also be
'*', which will return all registered names within a broadcast
area.</para></listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>EXAMPLES</title>
<para><command>nmblookup</command> can be used to query
a WINS server (in the same way <command>nslookup</command> is
used to query DNS servers). To query a WINS server, <command>nmblookup</command>
must be called like this:</para>
<para><command>nmblookup -U server -R 'name'</command></para>
<para>For example, running :</para>
<para><command>nmblookup -U samba.org -R 'IRIX#1B'</command></para>
<para>would query the WINS server samba.org for the domain
master browser (1B name type) for the IRIX workgroup.</para>
</refsect1>
<refsect1>
<title>VERSION</title>
<para>This man page is correct for version 3.0 of
the Samba suite.</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><citerefentry><refentrytitle>nmbd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>samba</refentrytitle>
<manvolnum>7</manvolnum></citerefentry>, and <citerefentry><refentrytitle>smb.conf</refentrytitle>
<manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</para>
<para>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at <ulink url="ftp://ftp.icce.rug.nl/pub/unix/">
ftp://ftp.icce.rug.nl/pub/unix/</ulink>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</para>
</refsect1>
</refentry>
|