257:
session can be established (either because that computer is not listening for sessions being established to that name or because no resources are available to establish a session to that name) or that a session can be established (in which case the response will include a local session number to be used in subsequent packets). The computer that is starting the session will then send a "Session
Initialize" request which will prompt a "Session Confirm" response.
265:, a NetBIOS/NetBEUI packet might have to be transmitted as a sequence of "Data First Middle" packets and a "Data Only Last" packet; packets that do not need to be segmented in that fashion will be sent as a single "Data Only Last" packet. An acknowledgment will be sent for all "Data Only Last" packets that are successfully received; this will also acknowledge all preceding "Data First Middle" packets.
224:
In order to start sessions or distribute datagrams, an application must register its NetBIOS/NetBEUI name using the name service. To do so, an "Add Name Query" or "Add Group Name Query" packet is broadcast on the network. If the NetBIOS/NetBEUI name is already in use, the name service, running on the
256:
Sessions are established by exchanging packets. The computer establishing the session sends a "Name Query" request, specifying that a session should be initialized. The computer with which the session is to be established will respond with a "Name
Recognized" response indicating either that no
260:
Data is transmitted during an established session by data packets. IEEE 802.2 handles flow control and retransmission of data packets. Because NetBIOS/NetBEUI allows packets to be sent that are larger than the largest packet that could be transmitted on a particular
191:, where it has such an advantage over TCP/IP that 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.
232:
of the host with a given NetBIOS/NetBEUI name; this is done by sending a "Name Query" packet, the response to which will have the MAC address of the host sending the response, i.e. the host with that name.
245:". A datagram is sent with a "Datagram" packet if it is being sent to a particular NetBIOS/NetBEUI name, or a "Datagram Broadcast" packet if it is being sent to all NetBIOS/NetBEUI names on the network.
154:
interface. While the protocol consumes few network resources in a very small network, broadcasts begin to adversely impact performance and speed when the number of hosts present in a network grows.
253:
Session mode lets two computers establish a connection for a "conversation," allows larger messages to be handled, and provides error detection and recovery.
488:
228:
In addition, to start a session or to send a datagram to a particular host rather than to broadcast the datagram, NBF protocol has to determine the
345:
320:
119:
370:
421:
396:
493:
147:
467:
446:
295:, but it is included on the Windows XP CD-ROM and can be installed manually. Windows Vista does not include
183:, but being bridgeable it can also be used to communicate with network segments connected to each other via
280:
and Unix implementations – was officially supported by
Microsoft on almost every version of Windows up to
38:
187:. The lack of support for routable networks means that NBF is only well-suited for small to medium-sized
53:
349:
324:
285:
77:
179:
Because NBF protocol is unroutable it can only be used to communicate with devices in the same
95:
that was originally developed in conjunction with the NBF protocol; both the protocol and the
42:
188:
180:
143:
34:
242:
184:
473:
482:
30:
281:
65:
229:
57:
56:
is used by a number of network operating systems released in the 1990s, such as
292:
225:
host that owns the name, broadcasts a "Node
Conflict" message on the network.
165:
107:
91:. This originates from the confusion with NetBIOS Extended User Interface, an
73:
69:
61:
50:
168:
program and was used by
Microsoft for MS-NET in 1985. In 1987, Microsoft and
375:
262:
157:
111:
84:) also implement the NetBIOS/NetBEUI services over other protocol suites.
425:
400:
206:
135:
99:
27:
151:
173:
92:
81:
46:
450:
169:
114:
caused this confusion by labelling its NBF protocol implementation
139:
131:
397:"The NetBEUI Protocol Is Not Available in Windows XP (KB306059)"
277:
172:
utilized it for their network operating systems LAN Manager and
102:
were originally developed to allow NetBIOS programs to run over
161:
103:
284:, but its use has decreased quickly since the development of
87:
The NBF protocol is broadly, but incorrectly, referred to as
142:
type 2 mode to provide the NetBIOS/NetBEUI session service (
134:
type 1 mode to provide the NetBIOS/NetBEUI name service and
118:. NBF is a protocol and the original NetBEUI was a NetBIOS
268:
Sessions are closed by sending a "Session End" request.
212:
Session service for connection-oriented communication
209:
distribution service for connectionless communication
291:Microsoft officially dropped support starting with
199:NetBIOS/NetBEUI provides three distinct services:
422:"How to install NetBEUI on Windows XP (KB301041)"
203:Name service for name registration and resolution
150:messages, which accounts for its reputation as a
468:LAN Technical Reference: 802.2 and NetBIOS APIs
299:(means NBF) support at all, but the Windows XP
216:NBF protocol implements all of these services.
346:"NetBios NetBEUI NBF Networking Encapsulation"
321:"NetBios NetBEUI NBF Networking Introduction"
8:
41:most commonly used as one of the layers of
474:Comparison of Windows NT Network Protocols
312:
470:– includes NBF protocol specifications
16:Microsoft Windows networking protocol
7:
489:Windows communication and services
146:). NBF protocol makes wide use of
14:
371:"NetBEUI support on Windows 2000"
120:application programming interface
76:. Other protocols, such as NBT (
45:networking in the 1990s. NBF or
276:NBF protocol – apart from DOS,
1:
303:support drivers can be used.
237:Datagram distribution service
93:extension to the NetBIOS API
510:
447:"NetBeui on XP and Vista"
80:), and NBX (NetBIOS-over-
160:developed NetBIOS for
66:Windows for Workgroups
403:on 20 February 2010
78:NetBIOS over TCP/IP
241:Datagram mode is "
130:NBF protocol uses
494:Network protocols
428:on 17 August 2010
43:Microsoft Windows
501:
455:
454:
453:on 7 March 2016.
449:. Archived from
443:
437:
436:
434:
433:
424:. Archived from
418:
412:
411:
409:
408:
399:. Archived from
393:
387:
386:
384:
383:
367:
361:
360:
358:
357:
348:. Archived from
342:
336:
335:
333:
332:
323:. Archived from
317:
181:broadcast domain
509:
508:
504:
503:
502:
500:
499:
498:
479:
478:
464:
459:
458:
445:
444:
440:
431:
429:
420:
419:
415:
406:
404:
395:
394:
390:
381:
379:
369:
368:
364:
355:
353:
344:
343:
339:
330:
328:
319:
318:
314:
309:
274:
251:
249:Session service
239:
222:
197:
144:virtual circuit
128:
17:
12:
11:
5:
507:
505:
497:
496:
491:
481:
480:
477:
476:
471:
463:
462:External links
460:
457:
456:
438:
413:
388:
362:
337:
311:
310:
308:
305:
273:
270:
250:
247:
243:connectionless
238:
235:
221:
218:
214:
213:
210:
204:
196:
193:
127:
124:
20:NetBIOS Frames
15:
13:
10:
9:
6:
4:
3:
2:
506:
495:
492:
490:
487:
486:
484:
475:
472:
469:
466:
465:
461:
452:
448:
442:
439:
427:
423:
417:
414:
402:
398:
392:
389:
378:
377:
372:
366:
363:
352:on 2006-09-15
351:
347:
341:
338:
327:on 2007-02-07
326:
322:
316:
313:
306:
304:
302:
298:
294:
289:
287:
283:
279:
271:
269:
266:
264:
258:
254:
248:
246:
244:
236:
234:
231:
226:
219:
217:
211:
208:
205:
202:
201:
200:
194:
192:
190:
186:
182:
177:
175:
171:
167:
163:
159:
155:
153:
149:
145:
141:
138:service, and
137:
133:
125:
123:
121:
117:
113:
109:
105:
101:
98:
94:
90:
85:
83:
79:
75:
71:
67:
63:
59:
55:
52:
48:
44:
40:
36:
32:
29:
25:
21:
451:the original
441:
430:. Retrieved
426:the original
416:
405:. Retrieved
401:the original
391:
380:. Retrieved
374:
365:
354:. Retrieved
350:the original
340:
329:. Retrieved
325:the original
315:
300:
296:
290:
282:Windows 2000
275:
272:Availability
267:
259:
255:
252:
240:
227:
223:
220:Name service
215:
198:
178:
156:
129:
115:
96:
88:
86:
37:-level data
23:
19:
18:
230:MAC address
122:extension.
58:LAN Manager
26:) is a non-
483:Categories
432:2007-03-19
407:2007-03-19
382:2007-03-19
356:2006-11-24
331:2007-07-03
307:References
293:Windows XP
166:PC-Network
108:Token Ring
74:Windows NT
70:Windows 95
62:LAN Server
51:IEEE 802.2
376:Microsoft
263:MAC layer
148:broadcast
112:Microsoft
110:network.
35:transport
207:Datagram
195:Services
189:networks
164:for the
136:datagram
126:Overview
100:emulator
39:protocol
31:network-
28:routable
301:NetBEUI
297:NetBEUI
185:bridges
174:NetWare
116:NetBEUI
106:'s new
97:NetBEUI
89:NetBEUI
82:IPX/SPX
47:NetBIOS
170:Novell
152:chatty
158:Sytek
140:802.2
132:802.2
49:over
278:OS/2
72:and
33:and
286:NBT
162:IBM
104:IBM
54:LLC
24:NBF
485::
373:.
288:.
176:.
68:,
64:,
60:,
435:.
410:.
385:.
359:.
334:.
22:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.