Browse Prior Art Database

Increasing Resources for NetBios Applications without Application Programming Interface Changes

IP.com Disclosure Number: IPCOM000115985D
Original Publication Date: 1995-Jul-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 4 page(s) / 135K

Publishing Venue

IBM

Related People

Anand, VK: AUTHOR

Abstract

NetBIOS protocol has been designed for Local Area Networks. When the NetBIOS protocol is being used in Wide Area Network (WAN) environment, users hit the resource limitations that are inherent in the NetBIOS architecture. Even staying within the LAN spectrum, the users hit these limitations quickly. The following are the some of the reasons why the users hit this limitations in LAN itself: o Advancement in Hardware technology enables the users to add more systems to LAN etc., o Limitations are surfaced as the users are using the protocol more extensively. For e.g., running more applications on the same system.

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

Increasing Resources for NetBios Applications without Application
Programming Interface Changes

      NetBIOS protocol has been designed for Local Area Networks.
When the NetBIOS protocol is being used in Wide Area Network (WAN)
environment, users hit the resource limitations that are inherent in
the NetBIOS architecture.  Even staying within the LAN spectrum, the
users hit these limitations quickly.  The following are the some of
the reasons why the users hit this limitations in LAN itself:
  o  Advancement in Hardware technology enables the users to add more
      systems to LAN etc.,
  o  Limitations are surfaced as the users are using the protocol
more
      extensively.  For e.g., running more applications on the same
      system.

      Hence the software is also needed to be evolved to support the
hardware.  One way of achieving this is improving or extending the
existing software subsystems whenever it is possible.

      The resource limitations can be removed by increasing the
NetBIOS resources.  This disclosure will concentrate on only
improving
the major three NetBIOS resources - NAMES, COMMANDS and SESSIONS.

      Increasing the above mentioned three NetBIOS resources involves
the following issues:
  o  The protocol drivers need to be modified to allocate more of
each
      of these NetBIOS names, sessions and commands.
  o  The Network Control Blocks (NCB) defined for NetBIOS Application
      Programming Interface (API) have assigned one byte field to
      represent the maximum number for each of these (names, commands
      and sessions) resources.  There is a need to change the max
      resource number field to a word to represent more than 255.
      Changing the control block will affect the existing NetBIOS
      applications.
  o  In our NetBIOS protocol the maximum sessions and links available
      are 255.  But more sessions can be mapped to one link.  Hence,
if
      a NetBIOS application uses more than one session on one link
then
      the link table entries are wasted thereby our protocol will not
      let the users to use all the available links.  Consequently
more
      than one session should be associated with one link.
  o  Since these resource information such as session number, name
      number etc. are also used in the NetBIOS protocol frames, there
      is a need to redefine most of the NetBIOS frames.  Changing the
      frames will create incompatibility with the existing protocol
      stacks.

      This disclosure discusses how to implement the resource
extension with minimum impact to the existing applications and also
proposes solutions to the above mentioned issues.

      Increasing the NetBIOS resources without changing the NCB -
NETBIOS applications get their resources allocated during the
NCB.RESET command.  In our NetBIOS API driver, there is a c...