Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Network Identifiers for the NETBIOS LAN Communication Protocol

IP.com Disclosure Number: IPCOM000110577D
Original Publication Date: 1992-Dec-01
Included in the Prior Art Database: 2005-Mar-25
Document File: 2 page(s) / 92K

Publishing Venue

IBM

Related People

Cheng, C: AUTHOR [+4]

Abstract

This article extends the NETBIOS addressing specification by allowing a Network Identifier (NETID) to be part of a NETBIOS addressing definition. This permits multiple NETBIOS networks to exist on a single LAN, Bridged LANs and LANs which are interconnected by gateways to communication protocols, such as SNA, TCP/IP, OSI, etc. Currently, all NETBIOS LANS are considered part of a single address space without the benefit of a NETID address qualification.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Network Identifiers for the NETBIOS LAN Communication Protocol

       This article extends the NETBIOS addressing specification
by allowing a Network Identifier (NETID) to be part of a NETBIOS
addressing definition.  This permits multiple NETBIOS networks to
exist on a single LAN, Bridged LANs and LANs which are interconnected
by gateways to communication protocols, such as SNA, TCP/IP, OSI,
etc.  Currently, all NETBIOS LANS are considered part of a single
address space without the benefit of a NETID address qualification.

      In current NETBIOS communication networks existing in IBM's LAN
environment, there is no way for users of the NETBIOS application
programming interface (API) to specify endpoint network identifiers
of communicating partners.  All communication is implicitly limited
to a single address space.  There are several steps required in order
to address the NETBIOS NETID deficiency.

      Architect a NETBIOS NETID form that may be used in conjunction
with its current 16-byte name.  The 16-byte name is an unarchitected
form where byte position has no semantic.  In the NETBIOS NETID
environment, the 16 bytes would function as it does today.  That is,
it must be unique within a particular NETID (which is currently
implied as a single NETID).  For consistency with IBM networking
naming/addressing, this NETBIOS network ID would be an
eight-character value consisting of digits 0 through 9 and alphabetic
characters A through Z associated with a specific character set (SNA
like).

      Future users of the NETBIOS API indicate which Network
Identifier (NETID) should be used on each API request.

      In a configuration that consists of a LAN or Bridged LAN
environment, the current NETBIOS protocol does not contain space for
the NETID portion of the extended NETBIOS addressing technique.
Rather, today's API specifies a 4-bit adapter number identifying the
particular LAN adapter card associated with individual NETBIOS API
requests.  The request is then transmitted only through the LAN to
which the adapter card...