Session, datagram, and range of NetBIOS protocol

We have analyzed the basic concepts of the NetBIOS protocol and the differences with NetBEUI. Let us know a lot about the content. So next. Let's introduce more specific content of the NetBIOS protocol. Including NetBIOS Sessions, data packets, and systems.

NetBIOS session

NetBIOS Session Service provides a connection-oriented, reliable, and completely dual information service for user programs. NetBIOS requires a client program and a server program. The establishment of NetBIOS Sessions requires the cooperation between the two parties. A program must issue the listen command before other programs can issue the call command. For the listen command, refer to the name in its NetBIOS name table or in windows Server) and the name used as the remote program at the other end of the session. If the listener is not listening, the call command will not succeed. If the call succeeds, each program receives the session id as the confirmation for session creation.

Send and receive commands to transmit data. At the end of the session, each program will execute the pending command. There is no actual traffic control for the session service, because it is assumed that the LAN is fast enough to transmit the required data.
　
NetBIOS Datagram

A datagram can be sent to a specific location, all members in the group, or broadcast to the entire LAN. Compared with other data services, NetBIOS datagram is connectionless and unreliable. The send_datasync Command requires the caller to set the target name. If the target name is a group name, each member in the group receives data. The caller of the receive_datvecommand must determine the local place name of the data it receives. In addition to actual data, receive_datasync also returns the sender name. If NetBIOS receives data but does not run the receive_datvecommand while waiting, the data will be discarded.

The Send_Broadcast_Datagram Command sends information to each NetBIOS protocol system on the local network. When the NetBIOS node receives the broadcast data, each process that publishes the Receive_Broadcast_Datagram command receives the data. If these commands are not running when the broadcast data is received, the data will be discarded.

NetBIOS enables the application to establish a session with another device, so that the network forwarder and processing protocol can process requests received and sent to another machine. NetBIOS does not actually operate on data. NetBIOS defines the network interfaces used to reach the protocols of these services, rather than the Protocols themselves. Historically, NetBIOS was bundled with the NetBEUI protocol network extension user interface. The combination of interfaces and protocols sometimes causes confusion, but they are different.

Network protocols provide at least one way to locate and connect to specific services on the network. This is usually done by converting the node and service name into network address name resolution. Before establishing a connection with TCP/IP, the NetBIOS service name must be resolved to an IP address. Most NetBIOS TCP/IP implementations use broadcast or LMHOSTS files to resolve the name and address. In Microsoft, you are most likely to use a NetBIOS name server named WINS.
　
NetBEUI description

NetBEUI is an enhanced version of the network operating system that uses the NetBIOS protocol. It standardizes unstandardized transmission frames in NetBIOS and adds additional features. Transport-layer drivers are often used by Microsoft LAN Controllers of Microsoft slanmanager. NetBEUI executes the OSILLC2 protocol. NetBEUI is an interface designed by the original PC network protocol and IBM for the LanManger LAN operator) server. This agreement will be adopted by Microsoft later as a standard for their network products. It specifies the method by which the high-level software sends and receives information through the NetBIOS frame protocol. This protocol runs on the standard 802.2 data link protocol layer.
　
NetBIOS range

The NetBIOS range ID provides additional naming services for NetBIOS built on the TCP/IP module called NBT. The main purpose of NetBIOS range ID is to isolate NetBIOS communication on a single network from those nodes with the same NetBIOS range ID. The NetBIOS range ID is a string appended to the NetBIOS name. The NetBIOS protocol range IDs on the two hosts must match. Otherwise, the two hosts cannot communicate with each other. NetBIOS range ID allows computers to use the same computer name and different range IDs. The range ID is part of the NetBIOS name and is unique.