Understanding Network Protocols

An Introduction Network Protocols

A protocol is a collection of specifications or rules for data packets that enable information to be sent over the network. Network protocols are designed for network communication. In order to understand the different protocols available and their efficiencies, lets first look at the Open Systems Interconnection (OSI) reference model. This is the standard model for network communication developed by International Organization for Standardization (ISO). The design of the OSI model is that of a stack of protocols. The different stacks of protocols operate together to transport data and enable network communication. Each stack has specific functions associated with it to transmit data over the network.

The different layers of the Open Systems Interconnection (OSI) reference model are:

Data is transmitted in packets through the different OSI layers. When the packet travels from the top layers to the bottom layers in the OSI reference model, information is appended to the packet to assist in delivering it to the destination computer. The protocols that provide packaging, and delivery of the data at the various layers, are known as the protocol stack. The protocols stack is a collection of protocols. When data is transmitted over the network segments, the data is being routed. Transmission Control Protocol/Internet Protocol (TCP/IP) and Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) are the typically utilized routing protocols. When the network is not segmented, non-routing transport protocols such as NetBIOS Extended User Interface (NetBEUI) can be utilized. The downside of having non-routable protocols is that network expansion becomes an issue when the network needs to communicate with other networks. There are also some protocols that only function at a specific layer in the OSI reference model. In this case, the layer that the protocols operate at typically defines the function of the layer specific protocol. The following section looks at how protocols operate together to transmit data over the network.

How protocols operate together to transmit data over the network

As mentioned earlier, data is transmitted over the network in manageable portions, called packets. In addition to this, data is transmitted over the network in separate, methodical steps with each step having individual actions, and protocols. The protocol steps in the sending computer are carried out from top to bottom; and from bottom to top in the receiving computer.

The function of protocols at the sending computer is summarized below:

The function of protocols at the receiving computer is summarized below:

For the above mentioned process to be successful, each computer has to use the identical routable protocols. These are protocols that support LAN to LAN communications where data is transmitted from one LAN to another LAN through multiple paths.

You can mix protocols with NICs to suit your networking needs. This is known as the binding process. The binding process can be defined as the manner in which protocols are connected to one another and the NIC. The binding order ascertains the order that the OS execute the protocols for a network connection. This order is used when more than one protocol is bound to the same NIC.

There are a few standard protocol models that are used by hardware and software manufacturers when they develop technology or products. These protocols stacks are noted below. At each layer of the protocol stack, protocols execute various actions/tasks

The communication activities that the network has to perform fall into one of the protocol types listed below. The OSI reference model is actually utilized to define which protocols should operate at each layer of the OSI reference model. Each protocol type is therefore associated with layers within the OSI reference model:

The Institute of Electrical and Electronic Engineers (IEEE) protocols at the physical layer OSI reference model are detailed below:

The Primary Network Protocols

The primary network protocols utilized in networks these days are

Transmission Control Protocol/Internet Protocol (TCP/IP)

TCP/IP is the industry standard suite of protocols that enables enterprise networking and connectivity in a heterogeneous environment. It is the protocol commonly used for interoperability between various types of computers, and can be used to access the Internet and its resources. The protocol is typically utilized as an internetworking protocol and because of its many features; the majority of networks support it.

A few protocols especially designed for the TCP/IP protocol suite are:

The TCP/IP suite is a routable, robust, stable, scalable and efficient protocol that offers a variety of features and advantages over IPX/SPX and NetBEUI.

The TCP/IP suite utilizes the following four layer model, with each layer being associated with different layers of the OSI reference model:

AppleTalk

This is a protocol suite designed for communication among Macintosh computers. AppleTalk was developed by Apple Computer Corporation. From the Windows 2000 Server days, Windows included support for computers running Windows 2000 Server and Apple Macintosh clients to facilitate the sharing of files and printers.

Asynchronous Transfer Mode (ATM)

This is networking technology that transmits data in cells of a fixed length and is therefore best suited for voice, video, and data communications. A cell is a packet that has a fixed length. The ATM protocol provides a guaranteed of Service (QoS) on a LAN, a wide area network (WAN) and a public internetwork. Windows architecture utilizes the following components to support ATM:

Data Link Control (DLC)

This protocol was designed for IBM mainframe communications. It is commonly used to print to Hewlett-Packard printers which are directly connected to networks. A shortfall of this protocol is that it does not directly interface with the Transport Driver Interface layer.

Infrared Data Association (IrDA)

This is set of high speed, bidirectional wireless infrared protocols which enable different devices such as printers, portable and desktop computers, cameras and personal digital assistants (PDAs) to communicate between one another. NDIS connectionless drivers have to be used with the IrDA protocol stack.

Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX)

IPX defines addressing for the NetWare network with SPX providing security and reliability to the IPX protocol. IPX is a connectionless, datagram based, network-layer protocol. IPX is basically alike to the IP. IPX defines the following types of addressing:

SPX on the other hand provides connection oriented, reliable servers at the Transport layer of the OSI reference model.

The following protocols, other than IPX/SPX, are commonly used by Netware:

The Microsoft implementation of the IPX/SPX protocol is NWLink. NWLink is utilized when clients running a Windows OS need to access resources hosted by NetWare servers.

NetBIOS Enhanced User Interface (NetBEUI)

NetBEUI is a fast efficient transport layer protocol provided with network products. The protocol has a small stack size, small memory overhead and it compatible with all networks which are Microsoft based. NetBEUI is actually limited to Microsoft based networks. The major disadvantage of NetBEUI is that it does not include routing support. You therefore have to use bridges as opposed to routers when connecting computers running Windows and NetBEUI.

How to select between the different network protocols

The routable protocols most commonly utilized are Transmission Control Protocol/Internet Protocol (TCP/IP) and Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX). Routable protocols are typically utilized when a network needs to interact with a different network. You could opt to utilize a non-routable protocol such as NetBIOS Extended User Interface (NetBEUI) if you have a small non-segmented network. There are protocols that guarantee the delivery of data, while others merely broadcast data. When dealing with those larger networks, a protocol suite that guarantees delivery, reliability, and data integrity should be implemented. Data security is another key factor that should be considered when deciding on the protocol stack to implement. If your environment includes sensitive mission critical data, you would possibly need to choose a protocol stack that contains protocols which can authenticate, encrypt, and decrypt data. The items that you should include when selecting between the different network protocols are briefly summarized below:

Microsoft Windows Server 2003 utilizes a layered network architecture that enables different protocols to communicate using the identical structure and methods. The protocols supported on Windows Server 2003 are TCP/IP version 6, TCP/IP version 4, IPX/SPX and AppleTalk. The utilization of multiple network adapters is also supported with Windows Server 2003. Each network adapter can also use a combination of protocols or networking components. This is known as binding protocols to the adapter.

It is recommended to implement a DHCP server if your TCP/IP network has over 25 hosts. The DHCP server would enable you to configure host name resolution settings. DHCP would automatically provide the proper address for the hosts set up to use the DHCP protocol.

How to manually configure the TCP/IP protocol

  1. Click Start, Control Panel, and then Network Connections.
  2. Proceed to double-click the particular local area connection you want to work with, to open the Local Area Connection Status dialog box.
  3. Click the Properties button.
  4. When The Local Area Connection Properties dialog box appears, click Internet Protocol (TCP/IP), and click Properties
  5. This opens the Internet Protocol (TCP/IP) Properties dialog box.
  6. Select the Use the following IP address option and enter the appropriate IP address, subnet mask and default gateway information.
  7. Select the Use the following DNS server addresses option and enter the IP address of the DNS server.
  8. Click the Advanced button
  9. When the Advanced TCP/IP Settings dialog box appears, configure the necessary advanced TCP/IP properties.
  10. Click OK

How to change the protocol binding order

Use the steps below to change the protocol binding order:

  1. Click Start, Control Panel, and then Network Connections
  2. Use the menu bar to select Advanced, and then Advanced Settings
  3. Use the Adapters and Bindings tab to move the primary connection to the top of the available list.
  4. Choose a connection to display the bindings for a particular adapter.
  5. Choose the Internet Protocol (TCP/IP) beneath Client for Microsoft Networks and move it to the top of the list.
  6. Use the Provider Order tab to move Microsoft Windows Network to the top of the Network Providers list.
  7. Click OK


Top 5 Free Networking Tools

Bookmark Understanding Network Protocols

Latest Blog Posts


English English GermanGerman SpanishSpanish FrenchFrench ItalianItalian PortuguesePortuguese RussianRussian DutchDutch
GreekGreek HindiHindi JapaneseJapanese KoreanKorean ChineseChinese Chinese (Simplified)Chinese (Simplified) ArabicArabic

Copyright 2009 Tech-FAQ. All rights reserved. Privacy Policy.