Networking Basics and Protocols

Help Desk Ticket #1042: The 'Internal Only' Issue

Help Desk Ticket #1042

User: Sarah Jenkins, Marketing

Issue: Sarah can print to the office printer just fine, but she cannot access any external websites or check her email.

This common scenario is our starting point for understanding how Local Area Networks (LANs) and Wide Area Networks (WANs) interact.

Welcome to your first day on the help desk. We have a ticket from Sarah Jenkins. She reports that her local printer works, but the internet is unreachable. This immediately tells us that her local connection is functional, but the path to the outside world is blocked.

Help Desk Ticket #1042

Ticket Details

User: Sarah Jenkins
Issue: "I can print to the office printer, but I can't open any websites or check email."

This scenario is a classic example of a connectivity gap between local and external resources.

Welcome to the help desk. We have a new ticket from Sarah Jenkins. She's frustrated because she can print her reports locally, but she's completely cut off from the internet. To solve this, we need to understand how networks are structured and how data finds its way out of the building.

Network Types: LAN vs. WAN

Networks are categorized by their geographic reach.

First, let's look at the scope. Sarah's computer and printer are part of a Local Area Network, or LAN. Because they are in the same building, they communicate directly. However, the websites she wants to visit are on the Wide Area Network, or WAN—specifically, the Internet. Her problem likely lies at the router, which acts as the bridge between her LAN and the WAN.

Understanding Network Types

Networks are categorized by their geographic size:

To solve our user's problem, we need to distinguish between these network types. A **LAN**, or Local Area Network, connects devices in a small area, like the user's computer and that hallway printer. A **WLAN** is simply a **LAN** that uses wireless signals. Finally, a **WAN**, or Wide Area Network, covers huge distances. The Internet is the world's largest **WAN**.

Network Types: LAN vs. WAN

Geographic Reach

To solve Sarah's problem, we categorize networks by their scope:

A Local Area Network, or LAN, connects devices in a small area, like Sarah's office. If she were using Wi-Fi, we'd call it a WLAN. However, to reach the internet, her data must travel to a Wide Area Network, or WAN. In troubleshooting, we always look at the boundary where the LAN meets the WAN.

IP Addressing: IPv4 vs. IPv6

The Digital Address

Every device needs a unique IP (Internet Protocol) address to communicate.

Every device needs an identity. IPv4 uses four sets of decimal numbers. But with only 4.3 billion addresses, we've essentially run out. That's why we have IPv6, which uses hexadecimal characters to provide trillions upon trillions of unique addresses.

IP Addressing: IPv4 and IPv6

Every device needs a unique IP (Internet Protocol) address to communicate.

To talk to other devices, Sarah's computer needs an IP, or Internet Protocol address. Most networks still use IPv4, which looks like four numbers separated by dots. But because we ran out of IPv4 addresses, we now use IPv6. These are much longer, using hexadecimal characters to ensure every device on Earth can have its own unique ID.

The Internet's Phonebook: DNS

DNS (Domain Name System) – Port 53: Translates human-friendly names (google.com) into IP addresses.

If DNS fails, Sarah can't reach websites by name, even if her connection is physically active.

When Sarah types 'google.com', her computer doesn't actually know where that is. It asks a DNS, or Domain Name System server, on Port 53. The DNS acts like a phonebook, giving the computer the specific IP address needed to connect. Without DNS, the internet feels 'broken' because we can't remember thousands of numeric addresses.

Common Protocols and Ports

The Rules of the Road

A Protocol is a set of rules. A Port is a virtual doorway (0-65535).

Think of a protocol as a language and a port as a specific door at an address. DNS on Port 53 is the internet's phonebook. DHCP on Ports 67 and 68 gives devices their IP addresses automatically. For the web, we use HTTP on Port 80, or the secure HTTPS on Port 443.

Common Protocols and Ports

Protocols are the 'rules' for communication. Each uses a specific Port (a logical gateway) to route traffic.

ProtocolPort
DNS53
DHCP67/68
HTTP/HTTPS80/443
SSH22
RDP3389

Think of ports as doors to a building. Each protocol has its own door. **DNS** on Port 53 translates names like google.com into IP addresses. **DHCP** on Ports 67 and 68 automatically hands out **IP addresses** to devices. For the web, we use **HTTP** on Port 80 and the secure **HTTPS** on Port 443. Finally, for remote access, remember **SSH** on Port 22 and **RDP** on Port 3389.

PBQ: Troubleshooting the Gateway

The user still can't reach the internet. Use the terminal to diagnose the issue. Try typing ipconfig or ping 8.8.8.8.

Let's solve the ticket. Since the user can print locally but can't browse, we need to check their configuration. Type 'ipconfig' into the terminal to see if they have a valid gateway address. The **IP address** looks good, but look at the **DNS** server. It's blank. This is why they can't browse by name! Try pinging a public IP like 8.8.8.8 to see if the **WAN** connection is actually alive. The ping worked! This confirms the **WAN** is fine, but the **DNS** service is failing. You've successfully diagnosed the issue.

Protocol Matching Challenge

Match the Protocol to its default Port Number. This is a critical skill for the CompTIA A+ exam.

Let's test your memory. Drag the protocol names on the left to their correct port numbers on the right. Excellent! You've correctly identified that port. Well done. You've mastered the essential ports for this module.

Automating Setup: DHCP

DHCP (Dynamic Host Configuration Protocol) – Ports 67, 68: Automatically assigns IP addresses and configuration to devices.

If Sarah's computer can't find a DHCP server, it might assign itself an APIPA address (169.254.x.x).

When a device joins a network, it needs an IP address. Instead of typing it manually, we use DHCP, or Dynamic Host Configuration Protocol. The DHCP server hands out addresses on Ports 67 and 68. If this fails, Windows assigns an APIPA address starting with 169.254. If you see that number, you know the DHCP server is unreachable.

Core Protocols and Ports

Memorize these common protocols and their default ports for the A+ exam:

Beyond DNS and DHCP, you must know these core protocols. Notice that secure protocols like SSH on Port 22 and HTTPS on Port 443 are preferred over unencrypted ones like HTTP. For remote support, you'll often use RDP on Port 3389 to take control of a user's screen.

Troubleshooting Sarah's PC

Investigation Time

Use the simulated command prompt to check Sarah's network configuration. Type ipconfig to see her current settings.

Let's look at Sarah's computer. Type 'ipconfig' in the terminal to see her IP configuration. Look at the IP address. It's 192.168.1.15. That's a valid local address. Her Default Gateway is 192.168.1.1. Now, try to 'ping 8.8.8.8' to see if she can reach the internet by IP. The name resolution failed. This confirms it: her DNS settings on Port 53 are the problem. The ping worked! This means she HAS internet access, but she can't resolve names. Try to 'ping google.com' now.

Troubleshooting Sarah's Ticket

Let's use the ipconfig and ping commands to find the break in Sarah's connection.

1. Check the Default Gateway (the router).
2. Verify DNS resolution.

Let's sit at Sarah's desk and open the command prompt. Type 'ipconfig' to see her settings. Her IP is 192.168.1.50 and her gateway is 192.168.1.1. If we can ping the gateway but not 'google.com', we know the LAN is fine, but the WAN or DNS is the issue. Great idea. Pinging 8.8.8.8 works, which means she HAS internet access. But pinging 'google.com' fails. This confirms the DNS server on Port 53 is the culprit!

Exam Objectives Summary

Lesson Recap

You've completed the Networking Basics lesson. Remember: if local resources work but external ones don't, check the **WAN** gateway and **DNS** settings. Keep these ports and IP formats memorized, as they are high-frequency topics on the CompTIA A+ exam. See you in the next lesson!

Lesson Summary & Exam Objectives

Key Takeaways

Great work today. We've solved Sarah's ticket by identifying a DNS issue and explored the core protocols you'll see on the A+ exam. Remember to associate port numbers with their protocols and always check the Default Gateway when internet access fails.

Performance-Based Question: Identify the Outage

A user reports they cannot access the company's secure file server. Look at their network configuration and identify the most likely cause.

Here is a new scenario. A user's computer shows an IP address of 169.254.11.4. Based on what you've learned, what is the primary problem? Click on the component that has failed. Correct! An address starting with 169.254 is an APIPA address, meaning the computer could not reach the DHCP server to get a valid configuration. Not quite. That component seems fine. Look closely at that 169.254 IP address. What service provides IP addresses automatically?

Lesson Summary & Exam Prep

Exam Objectives Covered:

Excellent work. We've solved Sarah's ticket and covered the core networking objectives for the A+ exam. Remember: if a user can print but not browse, isolate the LAN from the WAN and check those DNS and DHCP settings. You're now ready to move on to configuring SOHO networks!