Network Working Group
`
`Request for Comments: 1002
`
`March, 1987
`
`PROTOCOL STANDARD FOR A NetBIOS SERV Cfi
`
`
`
`
`
`
`
`ON A TCP/UDP TRANSPORT:
`
`
`
`DETA LfiD SPECIFICATIONS
`
`
`
`
`ABSTRACT
`
`
`
`
`
`This RFC defines a proposed standard protocol to support Net% OS
`services in a TCP/IP environment. Both local network and internet
`operation are supported. Various node types are defined to accommodate
`local and internet topologies and to allow operation with or without the
`use of IP broadcast.
`
`
`This RFC gives the detailed specifications of the NetBIOS—over—TCP
`packets, protocols, and defined constants and variables.
`A more general
`overview is found in a companion RFC, "Protocol Standard For a NetBIOS
`Service on a TCP/UDP Transport: Concepts and Methods".
`
`
`NetBIOS Working Group
`
`[Page 1]
`
`Page 1 of 85
`
`LG Electronics Exhibit 1032
`
`

`

`RFC 1002
`
`March 1987
`
`4
`
`4
`
`5
`
`5
`
`5 7 7
`
`8
`
`10
`11
`
`13
`14
`15
`16
`16
`17
`18
`
`19
`20
`20
`
`21
`22
`23
`24
`25
`26
`27
`29
`29
`
`30
`31
`31
`31
`32
`32
`32
`32
`
`33
`34
`
`34
`34
`
`35
`35
`35
`
`1.
`
`2.
`
`3.
`
`4.
`
`
`
`
`TA4L£ Oh CONTENTS
`
`
`
`
`
`
`STATUS OF TH S MfiMO
`
`
`ACKNOWLEDGEMENTS
`
`
`
`
`INTRO)UCT ON
`
`
`
`
`PACKET DfiSCR PTIONS
`4.1 NAME FORMAT
`4.2 NAME SERVICE PACKETS
`4.2.1 GENERAL FORMAT OF NAME SERVICE PACKETS
`4.2.1.1 HEADER
`
`4.2.1.2 QUESTION SECTION
`4.2.1.3 RESOURCE RECORD
`
`4.2.2 NAME REGISTRATION REQUEST
`4.2.3 NAME OVERWRITE REQUEST & DEMAND
`4.2.4 NAME REFRESH REQUEST
`4.2.5 POSITIVE NAME REGISTRATION RESPONSE
`4.2.6 NEGATIVE NAME REGISTRATION RESPONSE
`4.2.7 END—NODE CHALLENGE REGISTRATION RESPONSE
`4.2.8 NAME CONFLICT DEMAND
`
`4.2.9 NAME RELEASE REQUEST & DEMAND
`4.2.10 POSITIVE NAME RELEASE RESPONSE
`4.2.11 NEGATIVE NAME RELEASE RESPONSE
`
`4.2.12 NAME QUERY REQUEST
`4.2.13 POSITIVE NAME QUERY RESPONSE
`4.2.14 NEGATIVE NAME QUERY RESPONSE
`4.2.15 REDIRECT NAME QUERY RESPONSE
`4.2.16 WAIT FOR ACKNOWLEDGEMENT (WACK) RESPONSE
`4.2.17 NODE STATUS REQUEST
`4.2.18 NODE STATUS RESPONSE
`SESSION SERVICE PACKETS
`4.3.1 GENERAL FORMAT OF SESSION PACKETS
`
`4.3.2 SESSION REQUEST PACKET
`4.3.3 POSITIVE SESSION RESPONSE PACKET
`4.3.4 NEGATIVE SESSION RESPONSE PACKET
`4.3.5 SESSION RETARGET RESPONSE PACKET
`4.3.6 SESSION MESSAGE PACKET
`4.3.7 SESSION KEEP ALIVE PACKET
`DATAGRAM SERVICE PACKETS
`4.4.1 NetBIOS DATAGRAM HEADER
`
`4.3
`
`4.4
`
`4.4.2 DIRECT_UNIQUE, DIRECT_GROUP,
`4.4.3 DATAGRAM ERROR PACKET
`
`& BROADCAST DATAGRAM
`
`4.4.4 DATAGRAM QUERY REQUEST
`4.4.5 DATAGRAM POSITIVE AND NEGATIVE QUERY RESPONSE
`
`5.
`
`PROTOCOL DESCRIPTIONS
`5.1 NAME SERVICE PROTOCOLS
`5.1.1 B—NODE ACTIVITY
`
`NetBIOS Working Group
`
`[Page 2]
`
`Page 2 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`
`PROCESSING
`
`PROCESSING
`PROCESSING
`
`PROCESSING
`PROCESSING
`
`35
`37
`37
`38
`39
`42
`42
`45
`45
`46
`47
`49
`50
`50
`54
`55
`56
`58
`60
`60
`61
`66
`67
`67
`67
`71
`72
`72
`72
`73
`73
`73
`73
`74
`74
`76
`78
`80
`
`83
`
`85
`
`L‘LJ
`
` }
`
`
`
`WWP<
`
`L‘L.
`
`ZWWW
`
`6.
`
`DEFINED CONSTANTS AND VARIABLES
`
`REFERENCES
`
`
`NetBIOS Working Group
`
`[Page 3]
`
`Page 3 of 85
`
`
`} NAME
`B-NODE
`
`
`
`
`B-NODE
`))_GROUP NAM
`
`B-NODE
`::ND_NAME
`
`
`AM: RETEASfi
`B NODE
`
`
`
`:NCOMING PACKETB-NODE
`
`
`l—F. Z O )E ACT
`TY
`
`P-NODE
`J.) NAME
`.
`
`
`P-NODE
`1.
`H—GROUP NAM
`:ND NAME
`P-NODE
`1.
`
`
`
`P-NODE
`1.
`DET.+'.T+'._NAME
`INCOMING PACKET
`P—NODE
`.1.
`TIMER INITIATED
`P—NODE
`.1.
`M- NODE ACTIVITY
`.3
`M—NODE
`ADD NAME
`.1.
`M—NODE
`ADD GROUP NAME
`.1.
`M—NODE
`FIND NAME
`.1.
`M—NODE
`DELETE NAME
`.1.
`M—NODE
`INCOMING PACKET
`.1.
`M—NODE
`TIMER INITIATED
`.1.
`NBNS ACTIVITY
`.4
`4.1 NBNS INCOMING PACKET PROCESSING
`.1.
`4. 2
`NBNS TIMER_INITIATED PROCESSING
`.1.
`SION SERVICE PROTOCOLS
`SES
`SESSION ESTABLISHMENT PROTOCOLS
`.1
`.2
`1.
`1 USER REQUEST PROCESSING
`2 RECEIVED PACKET PROCESSING
`.2
`1.
`SESSION DATA TRANSFER PROTOCOLS
`.2
`.2
`2.1
`USER REQUEST PROCESSING
`.2
`2. 2 RECEIVED PACKET PROCESSING
`.2
`2. 3
`PROCESSING INITIATED BY TIMER
`SESSION TERMINATION PROTOCOLS
`.3
`.2
`3.1 USER REQUEST PROCESSING
`5.2.3.2 RECEPTION INDICATION PROCESSING
`5.3 NetBIOS DATAGRAM SERVICE PROTOCOLS
`B NODE TRANSMISSION OF NetBIOS DATAGRAMS
`5 3 1
`P AND M NODE TRANSMISSION OF NetBIOS DATAGRAMS
`5.3.2
`RECEPTION OF NetBIOS DATAGRAMS BY ALL NODES
`5.3.3
`PROTOCOLS FOR_THE NBDD
`5 3 4
`
`1.
`1.
`1.
`1.
`1.
`
`2 1
`
`HHHHH
`UIEmNH
`NN:[\J:[\):[\J[\J501;me
`tA.)tA.)tA.)tA.)tA.)tA.)
`UNLJ'III-bzulklld
`
`UWUWI—‘UWUWUWUWUWUfil—‘UWUWUWUWUWUWP—‘mmmmm
`
`{II(II
`
`(II
`
`5. 2
`
`

`

`RFC 1002
`
`March 1987
`
`PROTOCOL STANDARD FOR A NetBIOS SERV Cfi
`
`
`
`
`
`
`
`ON A TCP/UDP TRANSPORT:
`
`
`
`
`DETA LfiD SPECIFICATIONS
`
`
`
`
`
`
`
`STATUS OF TH S MfiMO
`
`l.
`
`
`
`
`
`
`This RFC specifies a proposed standard for the DAiPA nternet
`
`community.
`Since this topic is new to the Internet community,
`
`discussions and suggestions are specifically requested.
`
`Please send written comments to:
`
`Karl Auerbach
`
`Epilogue Technology Corporation
`P.O. Box 5432
`
`Redwood City, CA
`
`94063
`
`Please send online comments to:
`
`Avnish Aggarwal
`Internet: mtxinulexcelan!avnish@ucbvax.berkeley.edu
`Usenet:
`ucbvaxlmtxinulexcelan!avnish
`
`Distribution of this memorandum is unlimited.
`
`
`
`2.
`
`ACKNOWLEDGEMENTS
`
`This RFC has been developed under the auspices of the Internet
`Activities Board.
`
`The following individuals have contributed to the development of
`this RFC:
`
`Avnish Aggarwal
`Geoffrey Arnold
`Keith Ball
`
`Richard Cherry
`Greg Ennis
`David Kaufman
`
`Dan Lynch
`Steve Thomas
`
`Arvind Agrawal
`Karl Auerbach
`Amatzia Ben—Artzi
`
`Lorenzo Aguilar
`K. Ramesh Babu
`Vint Cerf
`
`David Crocker
`Steve Holmgren
`Lee LaBarre
`
`Gaylord Miyata
`Ishan Wu
`
`Steve Deering
`Jay Israel
`James Lau
`
`David Stevens
`
`The system proposed by this RFC does not reflect any existing
`Netbios—over—TCP implementation. However,
`the design
`incorporates considerable knowledge obtained from prior
`implementations. Special thanks goes to the following
`organizations which have provided this invaluable information:
`
`CMC/Syros
`
`Excelan
`
`Sytek
`
`Ungermann—Bass
`
`NetBIOS Working Group
`
`[Page 4]
`
`Page 4 of 85
`
`

`

`RFC 1002
`
`
`
`
`
`INTRO)UCT ON
`
`3.
`
`March 1987
`
`
`This RFC contains the detailed packet formats and protocol
`
`specifications for NetBIOS—over—TCP. This RFC is a companion to
`
`
`
`RFC 1001, "Protocol Standard For a NetBIOS Service on a TCP/UDP
`Transport: Concepts and Methods" [1].
`
`
`
`
`PACKET DfiSCR PTIONS
`
`4.
`
`I1
`
`
`
`Bit and byte ordering are defined by the most recent version o;
`"Assigned Numbers"
`[2].
`
`4.1.
`
`NAME FORMAT
`
`
`
`The NetBIOS name representation in al' NetB"OS packets (for NAME,
`SESSION, and DATAGRAM services)
`is defined in the Domain Name
`Service RFC 883[3] as "compressed" name messages. This format is
`called "second—level encoding" in the section entitled
`"Representation of NetBIOS Names" in the Concepts and Methods
`document.
`
`
`
`
`the first two paragraphs from page 31,
`For ease of description,
`the section titled "Domain name representation and compression",
`of RFC 883 are replicated here:
`
`Domain names messages are expressed in terms of a sequence
`of labels. Each label is represented as a one octet length
`field followed by that number of octets. Since every domain
`name ends with the null label of the root, a compressed
`domain name is terminated by a length byte of zero.
`The
`high order two bits of the length field must be zero, and
`the remaining six bits of the length field limit the label
`to 63 octets or less.
`
`the total length of label
`To simplify implementations,
`octets and label length octets that make up a domain name is
`restricted to 255 octets or less.
`
`The following is the uncompressed representation of the NetBIOS name
`"FRED ", which is the 4 ASCII characters, F, R, E, D,
`followed by 12
`
`space characters (0x20). This name has the SCOPE_ID:
`
`"NETBIOS.COM"
`
`EGFCEFEECACACACACACACACACACACACA.NETBIOS.COM
`
`This uncompressed representation of names is called "first—level
`encoding" in the section entitled "Representation of NetBIOS Names"
`in the Concepts and Methods document.
`
`The following is a pictographic representation of the compressed
`representation of the previous uncompressed Domain Name
`representation.
`
`NetBIOS Working Group
`
`[Page 5]
`
`Page 5 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`1
`1
`1
`2 2 2 9 9 2 9 2 9 2 3 3
`1
`1 1 1 1
`1
`1
`0 1 2 3 4 5 6 7
`8 9 0
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`+ +
`+
`+ +
`+
`+ +
`+
`+
`+ + +
`+
`
`|
`0x20
`|
`E (0x45)
`|
`G (0x47)
`|
`F {0x46}
`
`+ +
`+
`+
`+
`+ +
`+
`+
`+ +
`+
`
`|
`+ J
`
`|
`+ +
`
`C [0x43)
`+
`
`E (0x45)
`+
`
`|
`+
`
`|
`+
`
`E (0x45)
`+
`
`C (0X43)
`+
`
`|
`+
`
`|
`+
`
`F (0x46)
`+
`
`J
`
`A (0x5 )
`+
`
`+
`
`|
`+ 1
`
`|
`+ +
`
`E (0x45)
`+
`
`C {0X43}
`+
`
`+
`
`|
`+
`
`|
`+
`
`|
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`|
`C (0X43)
`|
`A {0x41}
`|
`C (0x43)
`|
`A (0X41)
`|
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`A (0x41)
`|
`C (0x43)
`|
`A {0x41}
`|
`C {0x43}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`A (0x41)
`|
`C (0x43)
`|
`A {0x41}
`|
`C {0x43}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`A (0x41)
`|
`C (0x43)
`|
`A {0x41}
`|
`C {0x43}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`A (0x41)
`|
`C (0x43)
`|
`A {0x41}
`|
`C {0x43}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`A (0X41)
`|
`0x07
`|
`N {0X4E}
`|
`E {0x45}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`T (0x54)
`|
`B (0x42)
`|
`I {0x49}
`|
`O {0X4F}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`S (0x53)
`|
`0x03
`|
`C {0x43}
`|
`O {0X4F}
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`M (0X4D)
`|
`0x00
`
`+ + + + + + + + + + + + + + + + +
`
`A
`(page 31)].
`[7
`Each section of a domain name is called a label
`label can be a maximum of 63 bytes.
`The first byte of a label in
`compressed representation is the number of bytes in the label.
`For
`the above example,
`the first 0X20 is the number of bytes in the
`left—most label, EGFCEFEECACACACACACACACACACACACA, of the domain
`name.
`The bytes following the label length count are the characters
`of the label.
`The following labels are in sequence after the first
`label, which is the encoded NetBIOS name, until a zero {0x00} length
`count.
`The zero length count represents the root label, which is
`always null.
`
`A label length count is actually a 6—bit field in the label length
`field.
`The most significant 2 bits of the field, bits 7 and 6, are
`flags allowing an escape from the above compressed representation.
`If bits 7 and 6 are both set {11),
`the following 14 bits are an
`offset pointer into the full message to the actual label string from
`another domain name that belongs in this name. This label pointer
`allows for a further compression of a domain name in a packet.
`
`NetBIOS implementations can only use label string pointers in Name
`Service packets.
`They cannot be used in Session or Datagram Service
`packets.
`
`NetBIOS Working Group
`
`[Page 6]
`
`Page 6 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`(01 and 10} of a label
`The Other two possible values for bits I and 6
`
`
`
`length field are reserved "or "uture use by RFC 883[2 (page 32)].
`
`
`
`Note -haL the first octet o: a compressed name must contain one of
`the following bit patterns.
`{An "X" indicates a bit whose value may
`be either 0 or 1.}:
`
`
`
`
`
`length must be 32 (decimal)
`00100000 — Netbios name,
`llxxxxxx — Label string pointer
`10xxxxxx — Reserved
`lexxxxx — Reserved
`
`4.2.
`
`NAME SERVICE PACKETS
`
`4.2.1.
`
`
`GENERAL FORMAT OF NAME SERVICE PACKETS
`
`
`The NetBIOS Name Service packets follow the packet structure defined
`in the Domain Name Service (DNS) RFC 883 [7 (pg 26—31)].
`The
`
`structures are compatible with the existing DNS packet formats,
`however, additional types and codes have been added to work with
`NetBIOS.
`
`If Name Service packets are sent over a TCP connection they are
`
`preceded by a 16 bit unsigned integer representing the length of the
`Name Service packet.
`
`2 2
`1 2
`1
`1
`2 3 3
`2 2 2 2
`2
`1
`1 1 1
`1 1 1
`CO['0
`2 3
`9 0
`7
`3
`0 1 2 3 4 5 6 7 8 9
`9 0 1
`4 5 6 7
`1
`8
`4 5 6
`0 1 2
`
`+++++++++++++++++++++++++++++++++
`
`|
`
`HEADER
`
`
`+++++++++++++++++++++++++++++++
`
`QUESTION ENTRIES
`
`+++++++++++++++++++++++++++++++
`
` +—x—+—x—+—x—+—x—+— + + + + + + + +
`
`
`+++++++++++++++++++++++
`
`ANSWER RESOURCE RECORDS
`
`AUTHORITY RESOURCE RECORDS
`
`
`+++++++++++++++++++++++++++++++
`
`ADDITIONAL RESOURCE RECORDS
`
`+++++++++++++++++++++++++++++++
`
`I
`
`+—x—+—x—+—x—+—x—+—
`
`NetBIOS Working Group
`
`[Page 7]
`
`Page 7 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`
`HTADER
`.?.1.‘.
`
`0 1 2 3 4
`+ +
`+
`
`5 6 7
`
`+
`
`1
`8 9 O
`
`1 1
`1
`1 1 1 1
`1
`1 2 3 4 5 6 7 8
`+
`+ +
`+
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`9 0 1 2 3 4
`5 6 T 8
`9 0 1
`+
`+ +
`+
`
`+
`
`I
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I
`NAME_TRN_:D
`I OPCODE
`I RCODE I
`NM_FLAGS
`+ J
`+
`+
`+
`+
`J
`+
`+
`+
`+
`
`I
`+ +
`
`
`QDCOUNT
`+
`
`+
`
`+
`
`I
`+
`
`+
`
`+
`
`ANCOUNT
`+ +
`
`+
`
`I
`ARCOUNT
`I
`NSCOUNT
`I
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`Field
`
`Description
`
`NAME_TRN_ID
`
`Transaction ID for Name Service Transaction.
`Requestor places a unique value for each active
`transaction. Responder puts NAME_TRN_ID value
`from request packet in response packet.
`
`OPCODE
`
`Packet type code, see table below.
`
`NM_FLAGS
`
`Flags for operation, see table below.
`
`RCODE
`
`QDCOUNT
`
`Result codes of request. Table of RCODE values
`for each response packet below.
`
`Unsigned 16 bit integer specifying the number of
`entries in the question section of a Name
`
`Service packet. Always zero {0) for responses.
`Must be non—zero for all NetBIOS Name requests.
`
`ANCOUNT
`
`Unsigned 16 bit integer specifying the number of
`resource records in the answer section of a Name
`
`Service packet.
`
`NSCOUNT
`
`Unsigned 16 bit integer specifying the number of
`resource records in the authority section of a
`Name Service packet.
`
`ARCOUNT
`
`Unsigned 16 bit integer specifying the number of
`resource records in the additional records
`
`section of a Name Service packet.
`
`The OPCODE field is defined as:
`
`4
`3
`2
`l
`0
`+———+———+———+———+———+
`
`|
`OPCODE
`I R I
`+———+———+———+———+———+
`
`NetBIOS Working Group
`
`[Page 8]
`
`Page 8 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`Symbol
`
`Bit(s}
`
`Description
`
`
`OPCODE
`
`1—4
`
`Operation specifier:
`0 = query
`= registration
`release
`WACK
`refresh
`
`OOH-JONU'I
`
`R
`
`O
`
`
`RESPONSE flag:
`if bit == 0 then request packet
`if bit == 1 then response packet.
`
`The NM_FLAGS field is defined as:
`
`6
`5
`4
`3
`2
`1
`0
`
`+
`+
`+
`+
`+
`+
`
`+
`
`+
`
`I B I
`0
`I
`0
`IRA ITC IRD IRA I
`
`+
`+
`+
`+
`+
`+
`+
`+
`
`Symbol
`
`Bit{s)
`
`Description
`
`B
`
`RA
`
`6
`
`Broadcast Flag.
`= 1: packet was broadcast or multicast
`= 0: unicast
`
`3
`
`Recursion Available Flag.
`
`Only valid in responses from a NetBIOS Name
`Server —— must be zero in all other
`
`responses .
`
`then the NBNS supports recursive
`If one (1)
`query, registration, and release.
`
`then the end—node must iterate
`If zero (0)
`for query and challenge for registration.
`
`RD
`
`2
`
`Recursion Desired Flag.
`
`May only be set on a request to a NetBIOS
`Name Server.
`
`The NBNS will copy its state into the
`response packet.
`
`the NBNS will iterate on the
`If one (1)
`query, registration, or release.
`
`TC
`
`1
`
`Truncation Flag.
`
`NetBIOS Working Group
`
`[Page 9]
`
`Page 9 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`Set if this message was truncated because the
`datagram carrying it would be greater than
`5?6 bytes in length. Use TCP to get the
`
`
`information from the NetBIOS Name Server.
`
` Authoritative Answer flag.
`
`Must be zero (0)
`(0).
`
`
`
`if R flag of OPCODE is zero
`
`then if AA is one (1)
`If R flag is one {1)
`then the node responding is an authority for
`the domain name.
`
`End nodes responding to queries always set
`this bit in responses.
`
`4.2.1.2.
`
`QUESTION SECTION
`
`l l l l l l l l l l 2 2 2 2 2 2 2 2 2 2 3 3
`
`0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l
`+++++++++++++++++++++++++++++++
`
`QUESTION_NAME
`
`+—+—xx—+
`
`+ | / / |+ |+ F
`
`
`+++++++++++++++++++++++++++++++
`
`QUESTION_TYPE QUESTION CLASS I
`
`
`++++++++++++++++++++++++1++++++
`
`ield
`
`Description
`
`QUESTION_NAME
`
`The compressed name representation of the
`NetBIOS name for the request.
`
`QUESTION_TYPE
`
`The values for this field
`The type of request.
`are specified for each request.
`
`QUESTION_CLASS
`
`The values for this
`The class of the request.
`field are specified for each request.
`
`QUESTION_TYPE is defined as:
`
`Symbol
`
`NB
`NBSTAT
`
`Value
`
`0X0020
`0X0021
`
`Description:
`
`
`NetBIOS general Name Service Resource Record
`
`
`
`NetBIOS NODE STATUS Resource Record {See NO)£
`STATUS REQUEST)
`
`QUESTION_CLASS is defined as:
`
`NetBIOS Working Group
`
`[Page 10]
`
`Page 10 of 85
`
`

`

`RFC 1002
`
`March
`
`1987
`
`Symbol
`
`Value Description:
`
`IN
`
`OxOOOl
`
`
`Internet class
`
`4.2.1.3.
`
`
`
`RESOURCE RECORD
`
`l 1 1 2 2 2 2 2 2 2 2 2 2 3 3
`1
`l 1 1
`1
`1
`1
`0 l 2 3 4 5 6 7
`8 9 O
`1 2 3 4 5 6 ? 8
`9 0 l 2 3 4
`5 6 7 8
`9 O 1
`
`+ + I
`I
`+
`I
`I
`+
`I
`1
`I
`+
`I
`I
`I
`+
`I + I
`+
`I
`I
`I
`+ + I
`I
`+
`I
`I
`I
`
`|
`
`+
`
`|
`
`/
`/
`/
`/
`|
`|
`
`+ + + + +
`+ + + + +
`+ + + + +
`+ + + + + + + + + + + +
`
`RR_NAME
`
`
`I
`I
`RR_TYPE
`I
`RR_CLASS
`+ + + + +
`+ + + + +
`+ + + + +
`+ + + + + + + + + + + +
`
`I
`I
`TTL
`
`+ + + + +
`+ + + + +
`+ + + + +
`+ + + + + + + + + + + +
`
`I
`I
`I
`RDLENGTH
`
`|
`+ + + + +
`+ + + + +
`+ + +
`/
`/
`/
`/
`RDATA
`|
`|
`
`+ + + + +
`+ + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`Field
`
`Description
`
`RR_NAME
`
`The compressed name representation of the
`NetBIOS name corresponding to this resource
`record.
`
`RR_TYPE
`
`Resource record type code
`
`RR_CLASS
`
`Resource record class code
`
`TTL
`
`RDLENGTH
`
`The Time To Live of a the resource record‘s
`name.
`
`Unsigned 16 bit integer that specifies the
`number of bytes in the RDATA field.
`
`RDATA
`
`RR_CLASS and RR;TYPE dependent field. Contains
`the resource information for the NetBIOS name.
`
`RESOURCE RECORD RR_TYPE field definitions:
`
`Symbol
`
`Value Description:
`
`0X0001
`
`0X0002
`
`IP address Resource Record {See REDIRECT NAME
`QUERY RESPONSE}
`Name Server Resource Record (See REDIRECT
`
`A N
`
`S
`
`NetBIOS Working Group
`
`[Page 11]
`
`Page 11 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`NULL
`
`OXOOOA
`
`OXOOZO
`
`NBSTAT
`
`OX0021
`
` RfiSOURCfi RECOR) R
`
` Net
`
`
`NAME QUERY RESPONSE)
`
`NULL
`Resource Record (See WAIT FOR
`ACKNOWLEDGEMENT RESPONSE)
`NetBIOS genera: _ Name Service Resource Record
`
`(See NB_FLAGS and NB_ADDRESS, below)
`
`
`
`
`
`BIOS NO)£ STATUS Resource Record (See NO)£
`STATUS RESPONSE)
`
`
`
`
`
`
`
`{_CLASS field definitions:
`
`Symbol
`
`IN
`
`Value
`
`Description:
`
`OXOOOl
`
`Internet class
`
`
`
`
`
`NB_FLAGS field of the RESOURCE RECORD RUATA field for RR_TYPE O:
`"NB":
`
`1
`l
`1
`l
`1
`1
`0
`1
`3
`4
`5
`6
`7
`8
`9
`O
`1
`2
`3
`4
`5
`
`+
`+
`+
`+
`+
`+
`+
`+
`+
`+
`+
`+
`
`+
`
`+
`
`I
`+
`
`
`
`I G I
`+
`+
`
`ONT
`+
`
`I
`+
`
`+
`
`+
`
`+
`
`+
`
`
`
`RESERVED
`+
`
`
`
`+
`
`+
`
`:
`
`+
`
`Symbol
`
`Bit{s)
`
`Description:
`
`RESERVED
`ONT
`
`3—15
`1,2
`
`Reserved for future use. Must be zero (0).
`Owner Node Type:
`00 = B node
`01 = P node
`10 = M node
`11 = Reserved for future use
`
`For registration requests this is the
`claimant‘s type.
`For responses this is the actual owner's
`type.
`
`G
`
`0
`
`Group Name Flag.
`If one
`(1)
`then the RR;NAME iS a GROUP
`NetBIOS name.
`
`then the RR_NAME is a UNIQUE
`If zero (0)
`NetBIOS name.
`
`The NB_ADDRESS field of the RESOURCE RECORD RDATA field for
`RR_TYPE of "NB" is the IP address of the name's owner.
`
`NetBIOS Working Group
`
`[Page 12]
`
`Page 12 of 85
`
`

`

`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`0X0001
`+
`
`+
`
`+
`
` +—+—+—+—+—mx—+—+—mx—+—+—+—+ + + + + + +—+—+—+—+—mx—+—+—mx—+—+—+—+
`
`RFC 1002
`
`March 1987
`
`4.2.2.
`
`
`
`
`
`
`
`NAMfi REG STRAT ON RfiQUEST
`
`8 9
`5 6 7
`0 l 2 3 4
`
`+
`+
`+
`+
`++
`+
`+
`++
`+
`
`
`NAME TRN ID
`+
`
`+
`
`+
`
`I0
`+
`
`I
`
`0X5
`
`+
`
`0 O lIOIO 0 Bl
`+.
`+
`
`OX0
`
`I
`+
`
`+
`
`+
`
`OXOOOO
`++
`
`+
`
`
`
`OX0001
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++
`
`QUESTION_NAME
`
`
`+++++++++++++++++++++++++++++++
`
`IN (0X0001)
`I
`NB (0X0020)
`
`++++++++++++++++++++++++++
`
`RR_NAME
`
`
`+++++++++++++++++++++++++++++++
`
`IN {OXOOOl}
`I
`NB (0X0020)
`
`+++++++++++++++++++++++++++++++
`TTL
`
`+++++++++++++++++++++++++++++++
`
`NB FLAGS
`I
`0X0006
`+++++++++++++++++++++¥1++++++++
`
`NB_ADDRESS
`+++++++++++++++++++++++++++++++
`
`the
`Since the RR_NAME is the same name as the QUESTION_NAME,
`RR NAME representation must use pointers to the QUESTION NAME
`name's labels to guarantee the length of the datagram is_less
`than the maximum 576 bytes.
`See section above on name formats
`and also page 31 and 32 of RFC 883, Domain Names — Implementation
`and Specification, for a complete description of compressed name
`label pointers.
`
`
`NetBIOS Working Group
`
`[Page 13]
`
`Page 13 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.3.
`
`
`
`
`
`
`
`NAME OVERWRITE REQUfiST &
`}*MfiND
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`+
`
`I
`+
`I
`+
`
`I
`+1
`I
`++
`
`+
`
`+
`
`
`
`
`
`
`
`NAME TRN :D
`_+_
`0X0001
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`+
`
`I0
`+
`I
`+
`
`
`
`I
`
`+
`
`0X5
`
`
`
`
`
`+
`
`+
`
`
`
`
`
`0 O OIOIO 0 Bl
`+1
`+
`OXOOOO
`++
`
`
`
`
`
`
`
`OX0
`
`
`
`+
`
`I
`I
`OXOOOO
`I
`0X0001
`
`+++++++++++++++++++++++++++ +++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++ +++++
`
`QUESTION—NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN (UXUOOl)
`
`+++++++++++++++++++++++++++ +++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++ +++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUl}
`
`+++++++++++++++++++++++++++ +++++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++ +++++
`
`I
`I
`UXUOOS
`I
`NB FLAGS
`
`+++++++++++++++++++++++_++++ +++++
`|
`NBADDRESS
`I
`
`+++++++++++++++_++++++++++++ +++++
`
`
`NetBIOS Working Group
`
`[Page 14]
`
`Page 14 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.4.
`
`
`NAME REFRESH REQUEST
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`+
`
`I
`+
`I
`+
`
`I
`+1
`I
`++
`
`+
`
`+
`
`
`
`
`
`
`
`NAME TRN :D
`_+_
`0X0001
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`+
`
`I0
`+
`I
`+
`
`
`
`I
`
`+
`
`0X9
`
`
`
`
`
`+
`
`+
`
`
`
`
`
`0 O OIOIO 0 Bl
`+1
`+
`OXOOOO
`++
`
`
`
`
`
`
`
`OX0
`
`
`
`+
`
`I
`I
`OXOOOO
`I
`0X0001
`
`+++++++++++++++++++++++++++ +++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++ +++++
`
`QUESTION—NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN (UXUOOl)
`
`+++++++++++++++++++++++++++ +++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++ +++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUl}
`
`+++++++++++++++++++++++++++ +++++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++ +++++
`
`I
`I
`UXUOOS
`I
`NB FLAGS
`
`+++++++++++++++++++++++_++++ +++++
`|
`NBADDRESS
`I
`
`+++++++++++++++_++++++++++++ +++++
`
`
`NetBIOS Working Group
`
`[Page 15]
`
`Page 15 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.5.
`
`
`
`
`
`
`
`
`POSIT"VE NAMfi REG STRAT ON RfiSPONSE
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1 2 3 4 5 6 7 8
`9 0 I 2 3 4
`5 6 7 8
`9 O 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`I
`+
`I
`+
`
`I
`+:
`I
`++
`
`NAME TRN ID
`_+_
`OXOOOU
`+
`
`+
`
`+
`
`+
`
`+
`
`I1
`+
`I
`+
`
`0X5
`
`:
`
`+
`
`+
`
`+
`
`I O 1I1IO 0 0|
`+1
`+
`0X0001
`++
`
`+
`
`OX0
`
`I
`I
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUI}
`
`+++++++++++++++++++++++++++++++++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUOOS
`I
`NB FLAGS
`
`++++++++++++++++++++++¥1+++++++++
`I
`NB ADDRESS
`I
`
`++++++++++++++¥1+++++++++++++++++
`
`4.2.6.
`
`NEGATIVE NAME REGISTRATION RESPONSE
`
`1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
`9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
`0 1 2 3 4 5 6 7 8
`
`++++++++++++++++++++++++++++++++
`
`I1IOI1I1I0 OIOI RCODE
`0X5
`I1I
`NAME TRN ID
`
`++++++I+I++++++++++++++++++++++
`OXOOOO
`I
`0X0001
`
`+++++++++++++++++++++++++++++++
`
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++
`
`RR_NAME
`
`
`+++++++++++++++++++++++++++++++
`
`IN {0X0001}
`I
`NB (OXOOZO)
`
`+++++++++++++++++++++++++++++++
`TTL
`
`+++++++++++++++++++++++++++++++
`
`NB FLAGS
`I
`0X0006
`
`+++++++++++++++++++++¥1++++++++
`
`NB_ADDRESS
`+++++++++++++++++++++++++++++++
`
`+—+—+—+—+—xx—+—+—+—
`
`+ |+ |+ |+ | / / |+ |+ |+ |+ |+
`
`NetBIOS Working Group
`
`[Page 16]
`
`Page 16 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`RCODE field values:
`
`Symbol
`
`EMT_ERR
`
`SRV_ERR
`
`IMP_ERR
`
`RFS_ERR
`
`ACT_ERR
`CFT_ERR
`
` Va lue
`
`0x1
`
`0x2
`
`0X4
`
`0x5
`
`0x6
`0x7
`
`Description:
`
`Format Error. Request was invalidly
`
`formatted.
`
`
`
`Server failure.
`process name.
`
`Problem with NBNS, cannot
`
`Unsupported request error. Allowable only
`
`for challenging NBNS when gets an Update type
`registration request.
`Refused error.
`For policy reasons server
`will not register this name from this host.
`Active error.
`Name is owned by another node.
`Name in conflict error.
`A_UNIQUE name is
`owned by more than one node.
`
`4.2.7.
`
`END-NODE CHALLENGE REGISTRATION RESPONSE
`
`l l l l l l l l l l 2 2 2 2 2 2 2 2 2 2 3 3
`
`0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l
`++++++++++++++++++++++++++++++++
`
`|+ |+ |+ | / / |+ |+ |+ |+ |+
`
`|l| 0X5 |l|0|l|0|0 0|0|NAME_TRN_ ID 0x0
`
`
`
`
`+++ + +++++++++++++++++++++++++++
`
`OXOOOO
`
`I OXOOOl
`+++ + +++++++++++++++++++++++++++
`
`OXOOOO
`
`I OXOOOO
`+++++++++++++++++++++++++++
`
`RR_NAME
`
`NB_ADDRESS +—+—+—+—+—xx—+—+—+—+
`
`
`+++++++++++++++++++++++++++
`
`NB (0X0020) IN {OXOOOl} I
`
`
`+++++++++++++++++++++++++++
`TTL
`+++++++++++++++++++++++++++
`
`0X0006
`
`| NB_FLAGS
`+++++++++++++++++++++++++++
`
`+++++++++++++++++++++++++++
`
`
`NetBIOS Working Group
`
`[Page 17]
`
`Page 17 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.8.
`
`.L
`
`NAM: CONFLICT DEMAND
`
`0 1 2 3 4
`++
`+
`
`5 6 7
`
`+
`
`1
`8 9 O
`
`1 1
`1
`1 1 1 1
`1
`1 2 3 4 5 6 7 8
`+
`++
`+
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`+
`++
`+
`
`I1
`+
`I
`+
`
`0X5
`
`J
`
`+
`
`+
`
`+
`
`1 O 1I1IO 0 0|
`+1
`+
`0X0001
`++
`
`+
`
`OX7
`
`+
`
`I
`+
`I
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I
`+1
`I
`++
`
`NAME TRN ID
`_+_
`OXOOOO
`+
`
`+
`
`+
`
`+
`
`+
`
`I
`I
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUI}
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUUOOOUUU
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`0X0006
`IOIONTIUI
`UXOOU
`
`+++++++++++++++++++++++++++++++++
`
`I
`UXUUOOOUUU
`I
`
`+++++++++++++++++++++++++++++++++
`
`This packet is identical to a NEGATIVE NAME REGISTRATION RESPONSE
`
`with RCODE = CFT_ERR.
`
`
`NetBIOS Working Group
`
`[Page 18]
`
`Page 18 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.9.
`
`
`
`
`NAM? RELEAST REQUEST & DEMAND
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`+
`
`I
`+
`I
`+
`
`I
`+1
`I
`++
`
`+
`
`+
`
`
`
`
`
`
`
`NAME TRN ID
`_+_
`OXOOOI
`+
`
`
`
`
`
`
`
`
`
`+
`
`+
`
`
`
`I0
`+
`I
`+
`
`
`
`I
`
`+
`
`0X6
`
`
`
`
`
`+
`
`+
`
`
`
`
`
`
`
`
`
`
`
`0 O OIOIO 0 Bl
`+1
`+
`OXOOOO
`++
`
`
`
`
`
`
`
`OX0
`
`
`
`+
`
`I
`I
`OXOOOO
`I
`OXOOOI
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`QUESTION—NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN (UXUOOI)
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUI}
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUUOOOUUU
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUOOS
`I
`NB FLAGS
`
`+++++++++++++++++++++++_++++++++++
`|
`NBADDRESS
`I
`
`+++++++++++++++_++++++++++++++++++
`
`the
`the QUESTION_NAME,
`Since the RR_NAME is the same name as
`string pointers to the
`RR_NAME representation must use label
`length of the datagram is
`QUESTION_NAME labels to guarantee the
`This is the same condition as
`less than the maximum 576 bytes.
`with the NAME REGISTRATION REQUEST.
`
`
`NetBIOS Working Group
`
`[Page 19]
`
`Page 19 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.10.
`
`
`
`
`POSIT"VE NAME RELEASE RESPONSE
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 O 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`I
`+
`I
`+
`
`I
`+:
`I
`++
`
`NAME TRN :D
`_+_
`OXOOOU
`+
`
`+
`
`+
`
`+
`
`+
`
`I1
`+
`I
`+
`
`0X6
`
`:
`
`+
`
`+
`
`+
`
`1 O OIOIO 0 0|
`+1
`+
`0X0001
`++
`
`+
`
`OX0
`
`I
`I
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUl}
`
`+++++++++++++++++++++++++++++++++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUOOS
`I
`NB FLAGS
`
`++++++++++++++++++++++¥1+++++++++
`I
`NB ADDRESS
`I
`
`++++++++++++++¥1+++++++++++++++++
`
`4.2.11.
`
`NEGATIVE NAME RELEASE RESPONSE
`
`1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
`9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
`0 1 2 3 4 5 6 7 8
`
`++++++++++++++++++++++++++++++++
`
`I1IOIOIOI0 OIOI RCODE
`0X6
`I1I
`NAME TRN ID
`
`++++++I+I++++++++++++++++++++++
`OXOOOO
`I
`0X0001
`
`+++++++++++++++++++++++++++++++
`
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++
`
`RR_NAME
`
`
`+++++++++++++++++++++++++++++++
`
`IN {0X0001}
`I
`NB (OXOOZO)
`
`+++++++++++++++++++++++++++++++
`TTL
`
`+++++++++++++++++++++++++++++++
`
`NB FLAGS
`I
`0X0006
`
`+++++++++++++++++++++¥1++++++++
`
`NB_ADDRESS
`+++++++++++++++++++++++++++++++
`
`+—+—+—+—+—xx—+—+—+—
`
`+ |+ |+ |+ | / / |+ |+ |+ |+ |+
`
`NetBIOS Working Group
`
`[Page 20]
`
`Page 20 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`
`RCODE field values:
`
`Symbol
`
`Value Description:
`
`
`
`EMT_ERR
`
`0X1
`
`Format Error. Request was invalidly
`
`formatted.
`
`SRV_ERR
`
`OX2
`
`
`Server failure.
`process name.
`
`Problem with NBNS, cannot
`
`RFS_ERR
`
`0x5
`
`For policy reasons server
`Refused error.
`will not release this name from this host.
`
`ACT_ERR
`
`Name is owned by another node.
`0x6 Active error.
`Only that node may release it.
`A NetBIOS
`Name Server can optionally allow a node to
`release a name it does not own. This would
`facilitate detection of inactive names for
`
`nodes that went down silently.
`
`4.2.12.
`
`NAME QUERY REQUEST
`
`l l l l l l l l l l 2 2 2 2 2 2 2 2 2 2 3 3
`0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l 2 3 4 5 6 7 8 9 0 l
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`
`|
`|
`NAME_TRN_ID
`|0|
`0X0
`|0|0|l|0|0 OIBI
`0x0
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`0X0001
`|
`OXOOOO
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`|
`OXOOOO
`|
`OXOOOO
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`|
`
`|
`
`/
`/
`/
`/
`|
`|
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`QUESTION_NAME
`
`|
`|
`NB (0x0020)
`|
`IN (0X0001)
`
`+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
`
`
`NetBIOS Working Group
`
`[Page 21]
`
`Page 21 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.13.
`
`
`POSITIVE NAME QUERY RESPONS
`
` L‘LJ
`
`0 1 2 3 4
`++
`+
`
`5 6 7
`
`+
`
`1
`8 9 O
`
`1 1
`1
`1 1 1 1
`1
`1 2 3 4 5 6 7 8
`+
`++
`+
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`9 0 1 2 3 4
`5 6 7 8
`9 O 1
`+
`++
`+
`
`
`I
`NAME TRN :D
`I1
`0X0
`1 T 1|?IO 0 0|
`OX0
`
`+:
`+
`_+_
`+
`+
`:
`+
`+1
`+
`I
`OXOOOU
`I
`0X0001
`++
`+
`+
`++
`
`+
`
`+
`
`+
`
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`+
`
`I
`+
`I
`+
`
`+
`
`I
`I
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NB (OXUUZU)
`I
`IN {UXOOUl}
`
`+++++++++++++++++++++++++++++++++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`RDLENGTH
`
`+++++++++++++++++
`I
`
`I
`|
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`ADDR_ENTRY ARRAY
`
`The ADDR ENTRY ARRAY a sequence of zero or more ADDR ENTRY
`records._ Each ADDR_ENTRY record represents an owner—of a name.
`For group names there may be multiple entries. However,
`the list
`may be incomplete due to packet size limitations. Bit 22, "T",
`will be set to indicate truncated data.
`
`Each ADDR_ENTRY has the following format:
`
`+++++++++++++++++++++++++++++++++
`
`
`|
`NB_FLAGS
`|
`|
`NB_ADDRESS
`+++++++++++++++++++++++++++++++++
`
`I
`NB ADDRESS (continued)
`|
`
`+++I+++++++++++++
`
`
`NetBIOS Working Group
`
`[Page 22]
`
`Page 22 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.14.
`
`
`
`
`
`
`NfiGAT VE NPME QUERY RESPONSE
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8
`O
`1 2 3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`+
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I
`+ I
`I
`++
`
`
`NAME TRN :D
`_ + _
`OXOOOU
`+
`
`+
`
`+
`
`+
`
`+
`
`I1
`+
`I
`+
`
`0X0
`
`I
`
`+
`
`+
`
`+
`
`
`0 1|?IO 0 0| RCODE I
`+ 1
`+
`+
`OXOOOO
`I
`++
`+
`
`+
`
`I
`I
`OXOOOO
`I
`OXOOOO
`
`+++++++++++++++++++++++++++++++++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++++++
`
`RR_NAME
`
`I
`I
`NULL (UXUUUA)
`I
`IN {UXOOUl}
`
`+++++++++++++++++++++++++++++++++
`
`I
`I
`UXUUOOOUUU
`
`+++++++++++++++++++++++++++++++++
`
`I
`UXUOOO
`|
`
`+++++++++++++++++
`
`RCODE field values:
`
`Symbol
`
`Value
`
`Description
`
`FMT_ERR
`
`SRV_ERR
`
`NAM_ERR
`
`IMP_ERR
`
`RFS_ERR
`
`0x1
`
`0x2
`
`0x3
`
`0x4
`
`0x5
`
`Format Error. Request was invalidly
`formatted.
`
`Server failure.
`process name.
`
`Problem with NBNS, cannot
`
`Name Error.
`exist.
`
`The name requested does not
`
`Unsupported request error. Allowable only
`for challenging NBNS when gets an Update type
`registration request.
`Refused error.
`For policy reasons server
`will not register this name from this host.
`
`
`NetBIOS Working Group
`
`[Page 23]
`
`Page 23 of 85
`
`

`

`RFC 1002
`
`March 1987
`
`4.2.15.
`
`
`
`REDIRECT NAME QUERY RESPONSE
`
`1 2 2 2 2 2 2 2 2 2 2 3 3
`1 1
`1
`1 1 1
`1
`1
`0 1 2 3 4
`5 6 7
`8 9 O
`1
`3 4 5 6 7 8
`9 0 1 2 3 4
`5 6 7 8
`9 0 1
`
`++
`+
`+
`+
`++
`+
`+
`++
`+
`
`
`I
`NAME TRN :D
`I1
`0X0
`0 O lIOIO 0 0|
`OX0
`+:
`+
`_+_
`+
`+
`:
`+
`+1
`+
`
`I
`OXOOOU
`I
`OXOOOO
`++
`+
`+
`++
`
`
`
`
`
`
`
`
`
`
`
`+
`
`+
`
`I
`+
`I
`+
`
`
`
`
`
`
`
`
`
`+
`
`
`
`
`
`
`
`
`
`
`
`+
`
`
`
`
`
`+
`
`
`
`
`
`
`
`+
`
`I
`I
`0X0001
`I
`0X0001
`
`+++++++++++++++++++++++++++++ +++
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++ +++
`
`RR_NAME
`
`I
`I
`NS (0X0002)
`I
`IN {OXOOOI}
`
`+++++++++++++++++++++++++++++ +++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++++ +++
`
`I
`I
`RDLENGTH
`
`+++++++++++++++++
`
`I
`
`I
`+
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++ +++
`
`NSD_NAME
`
`I
`
`I
`
`/
`/
`/
`/
`I
`I
`
`+++++++++++++++++++++++++++++ +++
`
`RR_NAME
`
`I
`I
`A {0X0001)
`I
`IN {OXOOOI}
`
`+++++++++++++++++++++++++++++ +++
`
`|
`I
`TTL
`
`+++++++++++++++++++++++++++++ +++
`
`I
`I
`0X0004
`I
`NSD IP ADDR
`
`++++++++++++++