Common Protocol Suites
From Proprofs
You are here: Home > Schools > Comptia > Network+ Certification > Wiki Home >Study Guide
Contents |
[edit section] Understanding Common Protocol Suites
Network+ will test you on your ability to differentiate between the more common protocol suites, or groups of protocols that are interconnected and work together to provide network services on many different layers of the OSI model. Most of the protocols operate between the Network and Application layers. The most common (and most tested on the exam) protocol suite is the TCP/IP suite, which encompasses such widely pervasive protocols as TCP, IP, HTTP, FTP, POP3, and many others. However, there exist other protocol suites as well, and CompTIA expects you to be able to identify the proprietor, usage, and unique features of each of the protocol suites.
[edit section] NetBEUI (NetBIOS Extended User Interface)
NetBEUI is a Microsoft protocol suite designed to work within a small-sized, Windows-based LAN. In fact, the NetBEUI protocol is not even routable, or able to transmit through routers. This is because the system of addressing that NetBEUI employs does not utilize “unique” identifiers or addresses; instead, NetBEUI uses 15 character “names” that are not necessarily unique. Think of NetBEUI as the system of communication you may use within your office – office mailboxes may address people on a first-name-last-name basis and in communicating with people, you often will say, “Send this to John”. Yet, outside of your office your request is meaningless, because there are millions of Johns throughout the world. So, that inter-office communication system is not “routable”.
[edit section] AppleTalk
The AppleTalk protocol suite is used for communication within Apple (Macintosh) networks. Unlike NetBEUI, AppleTalk is routable and can be employed in large LAN networks and even some WAN networks. However, this implementation is relatively uncommon as most computers on most networks will not be Apple computers and therefore will not natively communicate with AppleTalk. However, AppleTalk remains a viable option in large Macintosh networks.
[edit section] IPX/SPX
Novell is no longer such an active purveyor of this protocol suite (at least not as much as they used to be), but IPX/SPX is still employed on Novell (NetWare) networks. You should know that IPX (Internet Packet Exchange) is the Novell equivalent of the IP protocol of the TCP/IP suite as it is connectionless and cannot guarantee data delivery, while SPX (Sequenced Packet Exchange) is the equivalent of TCP and is connection-oriented. IPX is considered the fastest routable protocol available today, but the proprietary nature of the IPX/SPX suite, as well as the lack of developer consensus on the protocol suite and network hardware available for the suite has historically kept it from gaining widespread acceptance.
[edit section] DLC
DLC (Data Link Control) is a specialized protocol used for communication between a PC and non-PC devices, such as an older IBM PC, mainframe computer, or network-enabled printer. DLC is not designed for use between “normal” PC computers.
[edit section] TCP/IP
TCP/IP (Transmission Control Protocol / Internet Protocol) is by far the most common protocol suite today. There are several reasons for this, including the amount of development and architecture dedicated to the suite, the non-proprietary nature of the suite, its large number of application layer protocols, its use in the Internet, and its status as a relatively light-weight protocol suite. Key aspects of the TCP/IP protocol suite include:
- IP Addressing Scheme
- Suite Protocols at the Network, Transport, Session, and Application layers
- TCP Ports
- ARP Protocol (Layer-2 to Layer-3 translation)
- DHCP (Ability to automatically assign IP addresses)
Each of these items requires a broader study and will be covered individually in other articles, but remember that the above constitute the integral components of the TCP/IP stack.
[edit section] Quick Review
1. You have recently switched the communication protocol in your network to IPX/SPX at the recommendation of an analyst. Your network is directly connected to the Internet through a broadband connection. When you try to connect to the Internet, what will happen?
a. The connection will not be any noticeably different than before
b. Some users will be unable to connect because of TCP/IP to IPX/SPX bridge issues
c. You will not be able to access the Internet
d. You will not be able to use the MAC sub-layer services
2. An IBM PC is unable to connect to Macintosh computers, but can connect to other Windows machines as well as the Internet. Which of the following protocols should be installed to ensure that the PC can communicate with Macs?
a. TCP/IP
b. IPX
c. NetBeui
d. AppleTalk
3. Which two protocols can be used in conjunction to allow for communication between NT-based and Netware-based networks?
a. IP and TCP
b. IPX and SPX
c. IPX and IP
d. TCP and NetBeui
e. SPX and HTTP
f. IPX and NetBeui
[edit section] Answers
1. Because the Internet is a TCP/IP-based inter-network, it only follows that an IPX/SPX network directly connected to the Internet would not be able to communicate with the Internet because the protocols do not match. It would be akin to a Chinese manufacturer instructing French manufacturers in Chinese. So, the answer is C; you would not, in that case, be able to access the Internet (understand the Chinese manufacturer)
2. AppleTalk ensures communication with Macintosh computers, so the answer is D.
3. This one is tricky. Don’t be thrown off by NetBeui – it can only be used for communication with other Windows (Microsoft) computers. So you can eliminate the choices with NetBeui (D and F). Next, you should recognize that HTTP is not a protocol that could be used at any rate for communication between these networks and eliminate choice E. Choice B should immediately stand out as invalid because you understand that IPX and SPX are part of the same (Novell) protocol suite and therefore could not help in communication between NT and Novell networks. In a similar way, choice A can be eliminated because TCP and IP are both part of the TCP/IP stack. So, the only choice remaining is actually C. IP can be understood by both Windows-based and Novell-based machines, so an IPX to IP gateway would allow for communication between these networks.
Top 5 Contributors to this article
|
|||||||||
|