CNT4007C – Computer Network Fundamentals is a 3-credit upper-division course on how computer networks actually work: the layered model, the protocols at each layer, and the reasoning behind their design. The C suffix indicates an integrated laboratory, which is where the material becomes concrete.
This is a protocol and principles course rather than a vendor certification course. Where a CCNA-style class teaches configuration of specific equipment, this one asks why TCP behaves as it does under congestion, how routing algorithms converge, and what problems each layer exists to solve — knowledge that survives changes in equipment and remains useful for a career.
Content covers network architecture — layering, the OSI and TCP/IP models, and encapsulation; the application layer — HTTP, DNS, SMTP, and the client-server and peer-to-peer models; the transport layer — UDP, TCP, reliable data transfer, connection management, flow control, and congestion control; the network layer — IP addressing, subnetting, CIDR, forwarding, and fragmentation; routing — link-state and distance-vector algorithms, OSPF, and BGP at an introductory level; IPv6 and transition mechanisms; the link layer — framing, error detection, multiple access protocols, Ethernet, switching, and ARP; the physical layer — media, encoding, and bandwidth; wireless networking — 802.11, mobility, and the differences wireless imposes; network security fundamentals — threats, TLS, firewalls, and VPNs; network address translation; quality of service and multimedia networking; network management and troubleshooting; and laboratory work — packet capture, analysis, and configuration.
ping, traceroute, dig, netstat, ip. Know what each actually does.Florida demand is steady and geographically distributed — every hospital system, school district, county government, financial firm, and data center runs a network, and the state has a substantial defense and simulation sector in Orlando and Tampa where networking skills combine well with a clearance. Networking is also one of the more durable IT skill sets: the equipment changes, the protocols mostly do not.
The single most valuable practice in this course, and the thing that separates students who understand networking from those who memorized layer diagrams. Protocols are abstract until you watch them happen.
Capture your own traffic and find the things you have been reading about: the TCP three-way handshake, complete with sequence numbers you can follow; a DNS query and response preceding a web request; retransmissions when a packet is lost; the TLS handshake and the point at which content becomes unreadable; ARP resolving an address on your own subnet. Filter, follow a stream, and read the headers field by field.
Two further benefits. Packet analysis is a directly employable skill — it is central to network troubleshooting and to security operations work. And it builds the habit of verifying rather than assuming: when something does not work, the packets tell you what is actually happening, which is frequently not what the documentation implies.
The one mechanical skill in the course that is reliably tested in examinations and in job interviews, and the one students most often leave half-learned. Given an address and a prefix length you should be able to produce the network address, broadcast address, usable host range, and host count quickly and without a calculator.
What makes it click: work in binary until the boundaries are obvious, then learn the shortcuts rather than starting with the shortcuts; memorize the powers of two and the small set of possible octet values (128, 192, 224, 240, 248, 252, 254, 255); and practice variable-length subnet masking, where you divide a block efficiently among subnets of different sizes, because that is the realistic version of the problem.
Do enough repetitions that it is boring. Interviewers use subnetting precisely because it is quick to pose and immediately reveals whether a candidate's networking knowledge is real.
Worth appreciating rather than merely memorizing, because it explains something genuinely remarkable. The internet has no central controller allocating bandwidth. Instead, every TCP sender independently infers congestion from packet loss and slows down, then gradually speeds up again — and from those local decisions a roughly fair global allocation emerges.
The concrete consequences are worth knowing: TCP interprets loss as congestion, which is why TCP performs poorly over wireless links where loss is often corruption rather than congestion; why bufferbloat hurts, since oversized buffers delay the loss signal and inflate latency; and why applications that need timeliness more than reliability — voice, video, gaming — use UDP and handle loss themselves rather than waiting for retransmission. Understanding this explains far more real-world network behavior than any amount of configuration knowledge.
Important context that connects this course to security work. The core protocols were designed for a small, mutually trusting research network, and trust is assumed in places that are now exploited: ARP has no authentication, so a host can claim any address on the local network; DNS responses were originally unauthenticated, enabling cache poisoning; BGP largely trusts route announcements, which is why route hijacks occur and affect large portions of the internet; and IP source addresses can be forged, which is what makes reflection and amplification attacks possible.
The security layers in use today — TLS, DNSSEC, RPKI, 802.1X — are additions built on top of that foundation rather than parts of the original design. Understanding why a mitigation exists, and what it does and does not protect, is far more useful than memorizing a list of attack names, and it is exactly the reasoning security interviews probe.
The professional habit this course should leave you with. When a network problem appears, guessing is slow and unreliable. Work the layers methodically, usually bottom-up: is there physical connectivity (link light, cable, interface up)? Is there a link-layer address resolution (ARP)? Is there an IP address, mask, and gateway, and can you ping the gateway? Is there routing beyond it (traceroute)? Is DNS resolving (dig, and try the IP directly to isolate it)? Is the transport connection establishing (is the port open, is a firewall dropping it)? Only then is it the application.
The value of the method is that each step eliminates a layer, so you converge instead of guessing. Two heuristics worth carrying: "it's always DNS" is a joke because it is so often true — check name resolution early; and what changed? is the fastest question in troubleshooting, since networks that worked yesterday and fail today usually had something altered.
CNT4007C sits in the upper-division networking sequence alongside CNT4703C (voice and data network design), with CNT3104 (introduction to telecommunications) below it and security coursework at CNT2402 (penetration testing), CNT2404C (intrusion detection and auditing), and CIS4360 (computer security). Hands-on administration and certification content sits under CTS numbers — CTS2321C (Linux system administration), CTS2302C (Windows Active Directory), CTS2375C (cloud) — and CET numbers carry networking technology at some institutions.
The distinction is worth understanding when choosing courses: CNT courses tend to be protocol and principles oriented, while CTS and CET courses tend to be configuration and certification oriented. Both are valuable and they are not interchangeable. SCNS equivalency applies to the same number at the same level, never across numbers, so a 2000-level networking course does not satisfy a 4000-level requirement regardless of overlap — a frequent and expensive surprise for A.S.-to-B.S. transfer students.
Generated September 1, 2026 · Updated September 1, 2026