Meta tags:

Headings (most frequently used words):

netbios, name, service, internet, hostname, contents, history, and, terminology, services, vs, node, types, suffixes, protocol, stack, see, also, references, further, reading, external, links, datagram, distribution, session,

Text of the page (most frequently used words):
the (165), #netbios (122), and (59), name (49), for (40), windows (39), service (35), protocol (30), network (26), tcp (26), that (25), over (25), from (24), netbeui (23), session (23), was (21), with (21), edit (19), names (19), this (18), are (18), microsoft (18), api (18), computer (17), not (16), datagram (16), services (15), used (14), nbf (13), nbt (13), also (13), ibm (13), its (13), node (13), hostname (13), original (12), smb (12), networking (12), system (12), layer (12), but (12), internet (12), retrieved (11), domain (11), which (11), can (11), send (11), only (10), type (10), protocols (9), archived (9), file (9), networks (9), server (9), token (9), ring (9), link (9), ipx (9), other (9), wikipedia (8), use (8), articles (8), characters (8), lan (8), any (8), udp (8), such (8), applications (8), packet (8), implementation (8), may (7), 2023 (7), article (7), 802 (7), support (7), addresses (7), wins (7), see (7), record (7), broadcast (7), when (7), page (6), all (6), technical (6), suffixes (6), learn (6), message (6), supported (6), spx (6), called (6), host (6), dns (6), has (6), communicate (6), net (6), using (5), open (5), isbn (5), remote (5), march (5), how (5), 2000 (5), transport (5), frames (5), history (5), group (5), suffix (5), types (5), there (5), part (5), provides (5), resolution (5), one (5), version (5), provide (5), toggle (4), contents (4), search (4), under (4), june (4), multiple (4), september (4), 2010 (4), citations (4), control (4), basic (4), end (4), reference (4), links (4), technology (4), computers (4), hardware (4), carries (4), ieee (4), main (4), browser (4), character (4), generally (4), must (4), address (4), these (4), were (4), since (4), full (4), order (4), each (4), more (4), acknowledgment (4), will (4), mode (4), port (4), communication (4), standard (4), emulator (4), allow (4), layers (4), sytek (4), requests (4), responses (4), remove (4), help (4), here (4), hide (4), move (4), sidebar (4), add (3), table (3), view (3), text (3), available (3), registered (3), non (3), last (3), issues (3), too (3), august (3), 2012 (3), short (3), different (3), december (3), what (3), osi (3), nbx (3), operating (3), because (3), does (3), between (3), ipv6 (3), interface (3), com (3), 2007 (3), april (3), references (3), requires (3), workgroups (3), ethernet (3), data (3), input (3), output (3), application (3), related (3), printer (3), sharing (3), workstation (3), master (3), 16th (3), commonly (3), then (3), based (3), connection (3), hostnames (3), running (3), machine (3), usually (3), provided (3), small (3), had (3), stop (3), however (3), via (3), often (3), either (3), close (3), request (3), receive (3), wait (3), arrive (3), primitives (3), offered (3), runs (3), distribution (3), atop (3), enhanced (3), 1985 (3), own (3), netware (3), novell (3), created (3), level (3), oems (3), please (3), details (3), improve (3), tools (3), languages (2), contact (2), about (2), privacy (2), policy (2), terms (2), apply (2), inc (2), license (2), july (2), categories (2), unsourced (2), statements (2), lacking (2), description (2), wikidata (2), 2009 (2), base (2), list (2), lmhosts (2), systems (2), model (2), cifs (2), published (2), publication (2), external (2), 2004 (2), john (2), wiley (2), sons (2), concepts (2), haugdahl (2), scott (2), 1990 (2), architecture (2), inside (2), further (2), reading (2), 2017 (2), naming (2), february (2), 2006 (2), vista (2), install (2), www (2), edition (2), book (2), pdf (2), side (2), first (2), physical (2), following (2), stack (2), primary (2), controller (2), client (2), access (2), number (2), some (2), configured (2), way (2), operates (2), properties (2), advanced (2), connect (2), resolved (2), into (2), including (2), three (2), above (2), confused (2), being (2), case (2), whether (2), originally (2), today (2), most (2), method (2), they (2), installed (2), same (2), run (2), have (2), answered (2), ack (2), nak (2), response (2), prompt (2), sessions (2), closed (2), initiating (2), started (2), implement (2), establish (2), sends (2), listen (2), two (2), allows (2), messages (2), packets (2), error (2), detection (2), recovery (2), operation (2), connectionless (2), registers (2), length (2), 137 (2), citation (2), needed (2), top (2), necessary (2), itself (2), industry (2), through (2), able (2), switch (2), means (2), where (2), implemented (2), implementations (2), after (2), 1987 (2), released (2), included (2), officially (2), rfc (2), logical (2), complete (2), product (2), ready (2), form (2), oem (2), make (2), parts (2), interrupt (2), another (2), produced (2), new (2), user (2), local (2), area (2), terminology (2), transported (2), transports (2), general (2), talk (2), redirects (2), appearance (2), upload (2), changes (2), read (2), subsection (2), log (2), create (2), account (2), donate (2), menu (2), topic, mobile, cookie, statement, statistics, developers, code, conduct, legal, safety, contacts, disclaimers, additional, site, you, agree, trademark, profit, organization, wikimedia, foundation, creative, commons, attribution, sharealike, rendered, parsoid, edited, 2026, utc, hidden, dmy, dates, 2020, maintenance, addressing, https, org, index, php, title, oldid, 1364324576, czech, republic, national, authority, databases, richard, sharpe, october, 2002, january, just, library, visual, coder, bliss, jon, reedholm, knowledge, describing, interconnection, team, samba, implementing, apis, tamara, dean, 206, guide, meyers, michael, managing, troubleshooting, mcgraw, hill, 978, 225665, silberschatz, abraham, galvin, peter, baer, gagne, greg, 7th, 471, 69466, corp, 99914, conventions, active, directory, domains, sites, ous, 2019, defined, rfc1002, mapping, administrative, applies, ipv4, wpo, management, november, encapsulation, 2016, kb301041, kb306059, 2024, early, museum, getaway, oreilly, assessing, security, assessment, 2nd, 3rd, corporation, 939405, sosinsky, barrie, 9780470543429, 528, bible, block, manual, 2022, datacenter, azure, quic, incorrectly, labeled, netdde, presentation, hearts, clipbook, viewer, chat, shows, brief, enables, elections, controllers, workgroup, messenger, unique, alternately, endchar, indicates, limited, 255, values, displayed, opening, typing, registry, display, unknown, ipconfig, command, line, 0x08, hybrid, 0x04, mixed, 0x02, peer, 0x01, networked, relates, resolves, assumes, nodes, assured, thus, property, per, interaction, environment, four, plus, both, set, dialog, box, specific, viewed, changed, tab, panel, etc, typically, possible, operate, many, listed, norm, web, browsers, ftp, telnet, assuming, addition, need, necessarily, sometimes, stored, hierarchical, hosts, sequence, alphanumeric, explicitly, permitted, comply, restrictions, cannot, consist, entirely, digits, hyphen, appear, advised, against, presence, distinguish, ascii, limits, reserves, describes, specified, determined, individual, supplied, done, broadcasts, below, although, truncated, completely, conjunction, during, established, transmitted, positive, negative, retransmission, sending, reply, prompts, final, accept, reject, like, doesn, require, hang, attempts, call, opens, lets, span, 139, responsible, 138, find, looks, delete, unregisters, start, distribute, datagrams, register, octets, vary, particular, frequently, octet, designates, resource, tell, offers, rarely, note, upper, integral, now, adaptation, adds, field, byte, stream, notion, boundaries, ssn, oriented, dgm, registration, distinct, specification, become, despite, supporting, maximum, pcs, limitation, overcome, wide, transition, example, having, formerly, segment, compartmentalized, resolve, facto, unroutable, devices, bridgeable, segments, connected, lack, routable, well, suited, medium, sized, advantage, little, configuration, internetwork, bridges, confusion, originated, strictly, should, died, considering, time, companies, known, simply, regardless, incorporated, extensions, found, elected, consequently, continues, accurately, former, latter, moniker, hit, market, program, driver, offering, almost, every, decreased, quickly, development, dropped, starting, rom, manually, include, drivers, providing, described, 1001, methods, 1002, detailed, specifications, developed, built, virtually, suite, interoperation, 1986, featuring, company, emulation, encapsulated, within, delivered, actually, nor, distributed, lacked, expected, accessed, variant, split, lower, calls, depended, while, higher, independent, invoking, 0x2a, instead, 0x5c, reliance, unfortunate, effect, versions, weren, x86, went, forward, scheme, aware, era, work, named, extended, expanded, among, things, ability, deal, greater, capacity, simultaneously, specifically, uses, virtual, circuit, 1983, software, alone, relied, proprietary, wire, modern, identifying, 1980s, 1990s, manager, dos, llc, allowing, separate, several, discuss, without, removing, understandable, experts, readers, understand, includes, precise, introducing, lacks, sufficient, corresponding, inline, nios, digital, research, redirect, free, encyclopedia, item, projects, printable, download, print, export, legacy, parser, get, shortened, url, cite, information, permanent, actions, english, українська, türkçe, svenska, русский, português, polski, nederlands, македонски, 한국어, 日本語, italiano, bahasa, indonesia, magyar, français, فارسی, euskara, español, deutsch, dansk, čeština, català, brezhoneg, azərbaycanca, personal, special, pages, recent, community, portal, contribute, random, current, events, navigation, jump, content,

Text of the page (random words):
bute help learn to edit community portal recent changes upload file special pages search search appearance donate create account log in personal tools donate create account log in contents move to sidebar hide top 1 history and terminology 2 services toggle services subsection 2 1 name service 2 2 datagram distribution service 2 3 session service 3 netbios name vs internet hostname toggle netbios name vs internet hostname subsection 3 1 netbios name 3 2 internet hostname 4 node types 5 netbios suffixes 6 protocol stack 7 see also 8 references 9 further reading 10 external links toggle the table of contents netbios 24 languages azərbaycanca brezhoneg català čeština dansk deutsch español euskara فارسی français magyar bahasa indonesia italiano 日本語 한국어 македонски nederlands polski português русский svenska türkçe українська 中文 edit links article talk english read edit view history tools tools move to sidebar hide actions read edit view history general what links here related changes upload file permanent link page information cite this page get shortened url switch to legacy parser print export download as pdf printable version in other projects wikidata item appearance move to sidebar hide from wikipedia the free encyclopedia networking api and protocol netbeui and netbios enhanced user interface redirect here for details see netbeui netbios frames redirects here for details see netbeui network basic input output system redirects here for the network i o system see nios digital research this article has multiple issues please help improve it or discuss these issues on the talk page learn how and when to remove these messages this article includes a list of general references but lacks sufficient corresponding inline citations please help improve this article by introducing more precise citations august 2012 learn how and when to remove this message this article may be too technical for most readers to understand please help improve it to make it understandable to non experts without removing the technical details september 2010 learn how and when to remove this message learn how and when to remove this message netbios ˈ n ɛ t b aɪ ɒ s or network basic input output system is an api that provides services related to the session layer of the osi model allowing applications on separate computers to communicate over a local area network netbios is not a networking protocol netbios api requests and responses can be transported over several protocols the netbios frames protocol which transports netbios api requests and responses over ieee 802 2 llc was commonly used as one of the layers of dos and microsoft windows networking in the 1980s and 1990s it was supported by a number of network operating systems such as lan manager lan server windows for workgroups windows 95 and windows nt the netbios over ipx spx nbx protocol transports netbios api requests and responses over novell netware s ipx spx protocols in modern networks netbios requests and responses are usually transported over tcp ip via the netbios over tcp ip nbt protocol netbios over tcp ip is also used for identifying system names in tcp ip networks on windows history and terminology edit netbios 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 1 2 1 1 on ibm pc network as an api alone netbios relied on proprietary sytek networking protocols for communication over the wire 3 2 1 1 in 1985 ibm went forward with 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 2 1 1 this ibm emulator named netbios extended user interface netbeui 2 2 2 expanded the base netbios api created by sytek with among other things the ability to deal with the greater node capacity of token ring 2 2 17 a new networking protocol netbios frames nbf was simultaneously produced by ibm to allow the netbeui api to provide its services over token ring specifically at the ieee 802 2 logical link control layer it uses 802 2 type 1 mode to provide the netbios netbeui name service and datagram service and 802 2 type 2 mode to provide the netbios netbeui session service virtual circuit 2 3 8 3 10 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 the ieee 802 2 logical link control layer by the nbf protocol 4 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 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 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 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 5 in 1986 novell released advanced novell netware 2 0 featuring the company s own emulation of 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 providing netbios services atop 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 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 a driver offering the netbios api the nbf protocol was officially supported by microsoft on almost every version of windows up to windows 2000 6 but its use has decreased quickly since the development of nbt microsoft officially dropped support starting with windows xp 7 but it is included on the windows xp cd rom and can be installed manually 8 windows vista does not include netbeui means nbf support at all but the windows xp netbeui support drivers can be used 9 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 the nbf protocol netbeui naming its implementation of the transport protocol after ibm s enhanced version of the api citation needed 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 because the nbf protocol is unroutable it can only be used to communicate with devices in the same broadcast domain but being bridgeable it can also be used to communicate with network segments connected to each other via bridges the lack of support for routable networks means that nbf is only well suited for small to medium sized networks where it has an advantage over tcp ip in that it requires little configuration the netbios netbeui services must be implemented atop other protocols such as ipx and tcp ip see above in order to be of use in an internetwork 10 since its original publication in 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 the lan segment compartmentalized nbf protocol itself to resolve such names in windows client server networks 1 services edit netbios provides three distinct services name service netbios ns for name registration and resolution datagram distribution service netbios dgm for connectionless communication session service netbios ssn for connection oriented communication 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 a length field to each smb message this is necessary because tcp only provides a byte stream service with no notion of message boundaries name service edit 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 the type of resource and can be used to tell other applications what type of services the system offers citation needed 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 add name registers a netbios name add group name registers a netbios group name delete name unregisters a netbios name or group name find name looks up a netbios name on the network internet protocol version 6 ipv6 is not supported by the netbios name resolution protocol 11 datagram distribution service edit datagram mode is connectionless the application 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 send datagram send a datagram to a remote netbios name send broadcast datagram send a datagram to all netbios names on the network receive datagram wait for a packet to arrive from a send datagram operation receive broadcast datagram wait for a packet to arrive from a send broadcast datagram operation session service edit 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 call opens a session to a remote netbios name listen listen for attempts to open a session to a netbios name hang up close a session send sends a packet to the computer on the other end of a session send no ack like send but doesn t require an acknowledgment receive wait for a packet to arrive from a send on the other end of a session in 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 a positive acknowledgment ack or a 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 netbios name vs internet hostname edit 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 hostnames netbios name edit a netbios name is 16 ascii characters however microsoft limits the hostname to 15 characters and reserves the 16th character as a netbios suffix 12 this suffix describes the service or name record type such as host record master browser record or domain controller record or other services the hostname or short hostname for a host is specified when windows networking is installed or configured on the host the suffixes registered are determined by 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 hostname see below although truncated to 15 characters but it may also be completely different netbios names are 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 the presence of a full stop to distinguish domain names from netbios names 12 the windows lmhosts file provides a netbios name resolution method that can be used for small networks that do not use a wins server internet hostname edit a windows machine s netbios name is not to be confused with the computer s internet hostname assuming that the computer is also an internet host in addition to being a netbios node which need not necessarily be the case generally a computer running internet protocols whether it is a windows machine or not usually has a hostname 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 hostname of a windows computer is based on the netbios name plus the primary dns suffix which are both set in the system properties dialog box there may also be connection specific suffixes which can be viewed or changed on the dns tab in control pan...