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

Transmission Control Protocol/Internet Protocol Networking over Netbios

IP.com Disclosure Number: IPCOM000106843D
Original Publication Date: 1993-Dec-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 114K

Publishing Venue

IBM

Related People

Cheng, C: AUTHOR [+5]

Abstract

Many popular client/server types of applications based on the Transmission Control Protocol/Internet Protocol (TCP/IP) network in the UNIX* environment are being ported to traditional PC environments (DOS, Windows**, OS/2***). These applications most commonly access TCP/IP services via a transport programming interface called socket. TCP/IP is a networking protocol that can be used for LAN and WAN environment. Because of its generality, it is not as efficient a protocol as other widely used LAN based protocols. Netbios is one of the popular LAN protocols used widely in PC systems and in different types of LANs. Many PC client and server types of applications use the Netbios API to access Netbios services on LAN.

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

Transmission Control Protocol/Internet Protocol Networking over Netbios

      Many popular client/server types of applications based on the
Transmission Control Protocol/Internet Protocol (TCP/IP) network in
the UNIX* environment are being ported to traditional PC environments
(DOS, Windows**, OS/2***).  These applications most commonly access
TCP/IP services via a transport programming interface called socket.
TCP/IP is a networking protocol that can be used for LAN and WAN
environment.  Because of its generality, it is not as efficient a
protocol as other widely used LAN based protocols.  Netbios is one of
the popular LAN protocols used widely in PC systems and in different
types of LANs.  Many PC client and server types of applications use
the Netbios API to access Netbios services on LAN.  To use both types
of applications, the client workstation is required to install both
TCP/IP and Netbios protocols which results in extra memory,
configuration and management overheads of the two different networks
and inefficient use of limited computing resource at the workstation.

      The solution is to support both TCP/IP and Netbios applications
using SINGLE protocol on a LAN.  Since Netbios is the more efficient
LAN protocol, existing Netbios applications will continue to use the
Netbios API to access Netbios.  The TCP/IP socket interface can be
emulated using the Netbios API, therefore allowing a TCP/IP socket
application to communicate  with each other using the Netbios
protocol.  The term "TCP/IP networking over Netbios" refers to the
ability to emulate a TCP/IP network over the Netbios/LAN.

      To accomplish this task, the emulation layer will provide
services transparently to translate TCP/IP Network address to Netbios
name, and map the TCP/IP transport level services provided by socket
to Netbios.  Not all TCP/IP transport semantics can be emulated.
However, the majority can be supported and this allows most TCP/IP
socket applications run without changes.  This emulation can be
implemented directly using the current socket abstraction layer in
TCP/IP plus a Netbios specific emulation layer.  Much of the socket
semantics can be provided directly using the socket layer.  The
technique to implement the emulation layer is described below.

      The TCP/IP Network address (4 bytes Net Id and Host Id, 2 byte
Port Id (program ID)) is translated into a Netbios transport name (16
character).

      This is accomplished by using the 4 byte IP address as part of
the character string for the Netbios name prefixed with a unique
identifier.  Both the client and server system will use the same
address translation scheme and therefore will be able to
connect/locate one another using the same translated Netbios address.
The 2 bye of Port ID is carried as header information on the connect
request sent from the originating system to the destination system
and used at the destination to locate the destination program.

o...