If you've stepped into the world of Information Technology (IT), you've sailed into an ocean full of magical three-letter acronyms: RAM, CPU, SSD, DNS... Among these acronyms, there's one that forms the foundation of the internet and modern computer networks: TCP/IP.
Perhaps you've seen it on a forum while trying to solve a problem, or maybe it appeared in a training material. So, what exactly is TCP/IP, and where will you encounter it throughout your IT career? Let's explore this topic in the simplest way possible.
In its simplest terms, TCP/IP (Transmission Control Protocol / Internet Protocol) is the universal set of rules that computers, phones, smart TVs, and all other network-connected devices use to communicate with each other.
Let's liken it to a postal service:
IP (Internet Protocol): This is like the address you write on an envelope (data packet) you want to send. Every device on a network has a unique IP address. IP's job is to direct this data packet to the correct address, i.e., the right device. It only focuses on the address and doesn't care about the content of the letter or whether it got lost along the way.
TCP (Transmission Control Protocol): This is the reliable delivery service of the postal system. Imagine you're sending not just a letter, but an encyclopedia consisting of dozens of volumes.
TCP divides this encyclopedia (large data) page by page (into small packets).
It writes the page number on each page.
When it reaches the recipient, it checks if all pages (packets) have arrived.
If a page is missing, it says, "Please resend page 8."
Finally, it puts all the pages in the correct order, reassembling the encyclopedia completely.
Don't think this protocol is just theoretical. As you advance in fields like IT support, system administration, or network specialization, you'll frequently encounter the following situations:
This is the most classic IT support scenario. When a user comes with this complaint, TCP/IP settings should be the first thing that comes to mind.
Initial Check: Has the Device Obtained an Address?
When you open cmd in Windows and type the ipconfig command, the information displayed whispers the source of the problem to you.
IPv4 Address: The device's identification number on the network. If you see an address like 169.254.x.x here, it usually means the device couldn't obtain a valid IP address from the network.
Default Gateway: This is the "door" your device uses to access the internet. It's usually the IP address of your modem or router. If this address is missing, your device won't know how to leave the local network.
DNS Servers: These are like a phonebook that translates domain names like www.google.com into IP addresses. If DNS doesn't work, you won't be able to access websites by their names.
Sometimes the internet works generally, but only a specific site or server is inaccessible. At this point, two fundamental commands come to your rescue:
ping google.com: This command sends a small "hello" packet to the target server and checks if it receives a reply. If a reply comes, you know at least the basic network connection exists. If no reply comes, either the target server is down, or a network device in between is blocking communication.
tracert google.com: This command shows you like a map which stops (routers) your "hello" packet passed through until it reached its destination. If the connection breaks at some point, the tracert output provides an excellent clue as to where the problem might be.
When you set up a new printer, computer, or security camera, it needs an IP address to communicate with other devices on the network. Sometimes this happens automatically (thanks to DHCP), and sometimes you need to manually enter an IP address, subnet mask, and gateway. When you enter this information, you are directly configuring the TCP/IP protocol.
Firewalls, which ensure a company's cybersecurity, fundamentally operate over TCP/IP. When a rule is created, it's often stated like this: "Allow requests coming from this IP address and targeting TCP port 80 (web traffic), but block all requests targeting TCP port 3389 (Remote Desktop)." As you can see, IP addresses and TCP ports are fundamental building blocks of network security.
Learning TCP/IP is like laying the foundation of a house. It might seem a bit complex at first, but once you understand these basic concepts, diagnosing network problems, connecting systems, and ensuring security become much easier.
As you progress in your career, you'll delve deeper into these topics, analyze packets with tools like Wireshark, and learn advanced subjects like VLANs and subnetting. But remember, everything starts with understanding this fundamental duo: IP addresses, and TCP reliably transports.
Ali Gunes
Designed and coded by Ali Gunes
© 2024