Misplaced Pages

#645354

40-519: NetBIOS was developed by Sytek Inc as an API for software communication over this IBM PC Network LAN technology; with Sytek networking protocols being used for communication over the wire. IBM's later Token Ring network emulated the NetBIOS application programming interface , and it lived on in many later systems. The original broadband version in 1984 communicated over 75 Ω cable television compatible co-axial cable with each card connecting via

80-641: A local area network . As strictly an API , NetBIOS is not a networking protocol . Operating systems of the 1980s (DOS and Novell Netware primarily) ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. NetBIOS is also used for identifying system names in TCP/IP (Windows). NetBIOS

120-433: A DNS server. (It is also possible to operate many TCP/IP-based applications, including the three listed above, using only IP addresses, but this is not the norm.) Under Windows, the node type of a networked computer relates to the way it resolves NetBIOS names to IP addresses . This assumes that there are any IP addresses for the NetBIOS nodes, which is assured only when NetBIOS operates over NBT; thus, node types are not

160-597: A NetBIOS Service on a TCP/UDP Transport: Detailed Specifications"). The NBT protocol was developed in order to "allow an implementation [of NetBIOS applications] to be built on virtually any type of system where the TCP/IP protocol suite is available," and to "allow NetBIOS interoperation in the Internet." After the PS/2 computer hit the market in 1987, IBM released the PC LAN Support Program, which included

200-654: A car, then car restorers and collectors consider those to be the OEM parts. Other-brand parts would be considered aftermarket, such as Champion spark plugs, DieHard batteries, Kinsler fuel injectors, and BMP engine blocks and heads. Many auto parts manufacturers sell parts through multiple channels, for example to car makers for installation during new-vehicle construction, to car makers for resale as automaker-branded replacement parts, and through general merchandising supply chains. Any given brand of part can be OEM on some vehicle models and aftermarket on others. Microsoft

240-480: A company that produces parts and equipment that may be marketed by another manufacturer. However, the term is ambiguous, with several other common meanings. It sometimes means the maker of a system that includes other companies' subsystems, an end-product producer, an automotive part that is manufactured by the same company that produced the original part used in the automobile's assembly, or a value-added reseller . When referring to auto parts, OEM typically refers to

280-498: A different requirement regarding installation media from Direct OEMs. While a clean retail media of Windows can be installed and activated on these devices with OEM keys (most commonly using the SLP key that's embedded in to the system firmware already), actual OEM recovery media that was created by the PC manufacturer (not system-builder, nor retail Windows versions) typically only works on

320-676: A driver offering the NetBIOS API. There is some confusion between the names NetBIOS and NetBEUI. NetBEUI originated strictly as the moniker for IBM's enhanced 1985 NetBIOS emulator for Token Ring. The name NetBEUI should have died there, considering that at the time, the NetBIOS implementations by other companies were known simply as NetBIOS regardless of whether they incorporated the API extensions found in Token Ring's emulator. For MS-Net, however, Microsoft elected to name its implementation of

360-481: A length field to each SMB message; this is necessary because TCP only provides a byte-stream service with no notion of message boundaries.) In order to start sessions or distribute datagrams, an application must register its NetBIOS name using the name service. NetBIOS names are 16 octets in length and vary based on the particular implementation. Frequently, the 16th octet, called the NetBIOS Suffix, designates

400-405: A much cheaper " baseband " version, also running at 2 Mbit/s connected computers in daisy-chain style using twisted-pair cables with 6P2C modular telephone connectors (often mistermed "RJ11"). Interface cards had two 6P2C sockets for connecting to left and right neighbor nodes. The unused sockets at the ends of the network segment had to be fitted with a terminator on one end of the chain and

440-527: A positive-acknowledgment (ACK) or negative-acknowledgment (NAK) response. A NAK will prompt retransmission of the data. Sessions are closed by the non-initiating computer by sending a close request. The computer that started the session will reply with a close response which prompts the final session closed packet. When NetBIOS is run in conjunction with Internet protocols (e.g., NBT), each computer may have multiple names: one or more NetBIOS name service names and one or more Internet host names. The NetBIOS name

SECTION 10

#1732790796646

480-544: A property of NetBIOS per se but of interaction between NetBIOS and TCP/IP in the Windows OS environment. There are four node types. The node type in use is displayed by opening a command line and typing ipconfig /all . A Windows computer registry may also be configured in such a way as to display "unknown" for the node type. The NetBIOS Suffix, alternately called the NetBIOS End Character (endchar),

520-477: A sequence of alphanumeric characters. The following characters are explicitly not permitted: \/:*?"<>| . Since Windows 2000, NetBIOS names also had to comply with restrictions on DNS names: they cannot consist entirely of digits, and the hyphen ("-") or full-stop (".") characters may not appear as the first or last character. Since Windows 2000, Microsoft has advised against including any full-stop (".") characters in NetBIOS names, such that applications can use

560-459: A single F connector . Separate transmit and receive frequencies were used. Cards could be ordered that used different frequencies so multiple cards could transmit simultaneously, at 2 Mbit/s each. A Sytek head-end device was required to translate from each card's transmit frequency to the destination card's receive frequency. Frequency-division multiplexing allowed the cable to be shared with other voice, video, and data traffic. Later, in 1987

600-481: A technical reference book from IBM, the NetBIOS API specification has become a de facto standard in the industry despite originally supporting a maximum of only 80 PCs in a LAN. This limitation was generally overcome industry-wide through the transition from NBF to NBT, under which, for example, Microsoft was able to switch to Domain Name System (DNS) for resolution of NetBIOS hostnames , having formerly used

640-435: A variety of manufacturers ( Dell , HP , ASUS , Acer , Lenovo , Wistron , Inventec , Supermicro , Compal Electronics , Quanta Computer , Foxconn , Pegatron , Jabil , Flex , etc.). These OEMs commonly use a procedure known as System Locked Pre-installation , which pre-activates Windows on PCs that are to be sold via mass distribution. These OEMs also commonly bundle software that is not installed on stock Windows on

680-469: A wrap plug on the other. A hybrid star topology was possible using a hub. This computing article is a stub . You can help Misplaced Pages by expanding it . NetBIOS NetBIOS ( / ˈ n ɛ t b aɪ ɒ s / ) is an acronym for Network Basic Input/Output System . It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over

720-417: Is 16 ASCII characters, however Microsoft limits the host name to 15 characters and reserves the 16th character as a NetBIOS Suffix. This suffix describes the service or name record type such as host record, master browser record, or domain controller record or other services. The host name (or short host name) is specified when Windows networking is installed/configured, the suffixes registered are determined by

760-471: Is a popular example of a company that issues its Windows operating systems for use by OEM computer manufacturers via the bundling of Microsoft Windows . OEM product keys are priced lower than their retail counterparts, especially as they are purchased in bulk quantities, although they use the same software as retail versions of Windows. They are primarily for PC manufacturer OEMs and system builders, and as such are typically sold in volume licensing deals to

800-410: Is an operating system-level API that allows applications on computers to communicate with one another over a local area network (LAN). The API was created in 1983 by Sytek Inc . for software communication over IBM PC Network LAN technology. On IBM PC Network , as an API alone, NetBIOS relied on proprietary Sytek networking protocols for communication over the wire. In 1985, IBM went forward with

840-416: Is responsible for error detection and recovery. In NBT , the datagram service runs on UDP port 138. The datagram service primitives offered by NetBIOS are: Session mode lets two computers establish a connection, allows messages to span multiple packets, and provides error detection and recovery. In NBT , the session service runs on TCP port 139. The session service primitives offered by NetBIOS are: In

SECTION 20

#1732790796646

880-493: Is the 16th character of a NetBIOS name and indicates service type for the registered name. The number of record types is limited to 255; some commonly used values are: For unique names: For group names: The following table shows a brief history of NetBIOS and its related protocols. SMB was the main protocol that used NetBIOS. SMB enables Windows File and Printer Sharing. Original equipment manufacturer An original equipment manufacturer ( OEM ) generally refers to

920-473: Is tied to the PC motherboard which it is initially installed on, and there is typically no transferring the key between PCs afterward. This is in contrast to retail keys, which may be transferred, provided they are only activated on one PC at a time. A significant hardware change will trigger a reactivation notice, just as with retail. Direct OEMs are officially held liable for things such as installation/recovery media, and as such were commonly provided until

960-543: The Token Ring network scheme and produced an emulator of Sytek's NetBIOS API to allow NetBIOS-aware applications from the PC-Network era to work over IBM's new Token Ring hardware. This IBM emulator, named NetBIOS Extended User Interface (NetBEUI), expanded the base NetBIOS API created by Sytek with, among other things, the ability to deal with the greater node capacity of Token Ring. A new networking protocol, NBF ,

1000-562: The IEEE 802.2 Logical Link Control layer by the NBF protocol. However, the MS-Net was only delivered to OEMs , and it was actually not a complete product, nor was it ready to communicate on the network in the form it was distributed. It lacked any implementation of OSI Layers 1 to 4 ( Physical , Data link , Network and Transport Layers) and an OEM was expected to provide these implementations (in

1040-635: The LAN segment-compartmentalized NBF protocol itself to resolve such names in Windows client-server networks . NetBIOS provides three distinct services: (Note: SMB , an upper layer, is a service that runs on top of the Session Service and the Datagram service, and is not to be confused as a necessary and integral part of NetBIOS itself. It can now run atop TCP with a small adaptation layer that adds

1080-459: The NBF protocol "NetBEUI" – naming its implementation of the transport protocol after IBM's enhanced version of the API. Consequently Microsoft file and printer sharing over Ethernet often continues to be called NetBEUI, with the name NetBIOS commonly used only in reference to file and printer sharing over TCP/IP . More accurately, the former is NetBIOS Frames (NBF), and the latter is NetBIOS over TCP/IP (NBT). Since its original publication in

1120-556: The NetBIOS API. Its services were encapsulated within NetWare's IPX/SPX protocol using the NetBIOS over IPX/SPX (NBX) protocol. In 1987, a method of encapsulating NetBIOS in TCP and UDP packets, NetBIOS over TCP/IP (NBT), was published. It was described in RFC 1001 ("Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods") and RFC 1002 ("Protocol Standard for

1160-584: The System Properties dialog box. There may also be connection-specific suffixes which can be viewed or changed on the DNS tab in Control Panel → Network → TCP/IP → Advanced Properties. Host names are used by applications such as telnet , ftp , web browsers , etc. To connect to a computer running the TCP/IP protocol using its name, the host name must be resolved into an IP address , typically by

1200-512: The case). Generally a computer running Internet protocols (whether it is a Windows machine or not) usually has a host name (also sometimes called a machine name). Originally these names were stored in and provided by a hosts file but today most such names are part of the hierarchical Domain Name System (DNS). Generally the host name of a Windows computer is based on the NetBIOS name plus the Primary DNS Suffix, which are both set in

1240-495: The form of a NetBIOS part) to make its version of MS-Net a complete and ready to use product. MS-Net accessed the network through the Microsoft's own variant of NetBIOS, which was split into two parts - the lower level part that OEMs had to provide implemented the NetBIOS calls that depended on layers 1-4, while the higher level part, provided by Microsoft, was hardware- and protocol-independent. This NetBIOS implementation supported

IBM PC Network - Misplaced Pages Continue

1280-404: The full NetBIOS API, but was called by invoking x86 interrupt 0x2A, instead of IBM's standard interrupt 0x5C. The reliance on OEMs to implement parts of NetBIOS had the unfortunate side effect that different OEM versions of MS-Net and NetBIOS generally weren't able to communicate with one another. In 1986, Novell released Advanced Novell NetWare 2.0 featuring the company's own emulation of

1320-406: The images of Windows that will be deployed with their PCs (appropriate hardware drivers , anti-malware and maintenance software, various apps, etc.). Individuals may also purchase OEM "system-builder" licenses for personal use (to include virtual hardware ), or for sale/resale on PCs which they build. Per Microsoft's EULA regarding PC manufacturers and system-builder OEM licenses, the product key

1360-509: The individual services supplied by the host. In order to connect to a computer running TCP/IP via its NetBIOS name, the name must be resolved to a network address . Today this is usually an IP address (the NetBIOS name to IP address resolution is often done by either broadcasts or a WINS Server – NetBIOS Name Server). A computer's NetBIOS name is often the same as that computer's host name (see below), although truncated to 15 characters, but it may also be completely different. NetBIOS names are

1400-412: The late-2000s. These were phased out in favor of recovery partitions located on the primary storage drive of the PC (and available for order from the manufacturer upon request) for the user to repair or restore their systems to the factory state. This not only cut down on costs, but was also a consequence of the gradual obsolescence and phasing out of optical media from 2010 onward. System builders also have

1440-490: The manufacturer of the original equipment, that is, the parts which are then subsequently assembled and installed during the construction of a new vehicle. In contrast, aftermarket parts are those made by companies other than the OEM, which might be installed as replacements or enhancements after the car comes out of the factory. For example, if Ford used Autolite spark plugs , Exide batteries, Bosch fuel injectors , and Ford's own engine blocks and heads when building

1480-411: The original protocol used to implement NetBIOS services on PC-Network, to establish a session, the initiating computer sends an Open request which is answered by an Open acknowledgment. The computer that started the session will then send a Session Request packet which will prompt either a Session Accept or Session Reject packet. During an established session, each transmitted packet is answered by either

1520-430: The presence of a full-stop to distinguish domain names from NetBIOS names. The Windows LMHOSTS file provides a NetBIOS name resolution method that can be used for small networks that do not use a WINS server. A Windows machine's NetBIOS name is not to be confused with the computer's Internet host name (assuming that the computer is also an Internet host in addition to being a NetBIOS node, which need not necessarily be

1560-412: The type of resource, and can be used to tell other applications what type of services the system offers. In NBT , the name service operates on UDP port 137 (TCP port 137 can also be used, but rarely is). The name service primitives offered by NetBIOS are: Internet Protocol Version 6 (IPv6) are not supported by the NetBIOS name resolution protocol. Datagram mode is connectionless ; the application

1600-463: Was simultaneously produced by IBM to allow its NetBEUI API (their enhanced NetBIOS API) to provide its services over Token Ring – specifically, at the IEEE 802.2 Logical Link Control layer. In 1985, Microsoft created its own implementation of the NetBIOS API for its MS-Net networking technology. As in the case of IBM's Token Ring, the services of Microsoft's NetBIOS implementation were provided over

#645354