Network Services and Connectivity: the invisible infrastructure that makes the internet and corporate networks usable, turning raw cables and radio waves into a system where you can reliably send an email, load a website, or print a document. For the 220-1201 exam, you need to understand what these services are, what problem each one solves, and how they interact to create seamless connectivity. This knowledge is the foundation for troubleshooting 'why isn't this working?' in any IT role.
Jump to a section
A simple way to picture Network Services and Connectivity
A central mail-sorting facility manager is the key to this analogy. Their job is to make sure that every letter and package sent across the city reaches the right address, no matter which neighbourhood it's going to. They don't write the letters or pack the boxes themselves; they just keep the delivery network running smoothly. The post office building itself is like a network server — a powerful computer that holds shared resources, such as files or printers, and manages requests from other computers. The delivery vans are the network cables and Wi-Fi signals, carrying data packets (the letters) from one location to another.
Now, let's think about two key services. First, the post office assigns a unique address to every house — that's DHCP (Dynamic Host Configuration Protocol), which automatically gives each device on a network a unique IP address so data gets to the right place. Without DHCP, you'd have to manually type in an address for every device, which would be like handwriting a street address on every single letter. Second, when you type a person's name instead of their street address into a letter, the post office looks up their address in a directory — that's DNS (Domain Name System), which translates easy-to-remember website names, like 'google.com', into the numerical IP addresses that computers use to find each other. The city postal service also offers special services: a secure, tracked parcel service is like HTTPS (Hypertext Transfer Protocol Secure), which encrypts your data during delivery to prevent snooping. A standard, untracked postcard is like HTTP — it gets there, but anyone can read it along the way. The routing of mail through different regional hubs to ensure it takes the fastest route is like routing protocols used by routers to find the best path across the internet. This whole system fails if the central facility stops working — a network service outage — or if an address is typed wrong — a DNS misconfiguration.
At its simplest, a network is just a bunch of computers connected by cables or radio signals. But without a translator, a phone book, a traffic cop, and a security guard, that network is useless. 'Network Services' are the software programs and protocols — sets of rules — that run on servers to provide those critical functions. 'Connectivity' is the result: devices successfully communicating because these services are doing their jobs.
Let's start with the most fundamental service: DNS (Domain Name System). Imagine having to memorise a string of numbers, like 172.217.169.78, every time you wanted to visit Google. That's an IP address — a unique numerical label assigned to each device connected to a network that uses the Internet Protocol for communication. DNS is the internet's phone book. When you type 'www.google.com' into your browser, your computer sends a request to a DNS server. The DNS server looks up the name in its massive directory and replies with the correct IP address. Your computer then uses that IP address to connect. Without DNS, you'd need to remember the IP of every website, which is impractical. The exam loves to ask about DNS record types: an 'A' record maps a hostname to an IPv4 address; an 'AAAA' record maps to an IPv6 address; a 'CNAME' (Canonical Name) record maps one hostname to another, like 'shop.example.com' to 'example.com'.
Next is DHCP (Dynamic Host Configuration Protocol). Every device on a network needs a unique IP address to send and receive data. Configuring each device manually is tedious and error-prone — a process called static IP assignment. DHCP automates this. When your laptop connects to a Wi-Fi network, it broadcasts a 'discover' message. The DHCP server on the network (often built into the router) responds with an 'offer' of an IP address, along with other configuration details like the subnet mask, default gateway, and DNS server addresses. Your device then sends a 'request' accepting the offer, and the server sends an 'acknowledgement', finalising the lease. A lease is the amount of time the IP address is reserved for your device; once it expires, the device must renew the lease or get a new one. DHCP is why you can just join a coffee shop's Wi-Fi without talking to the barista to get a network address.
Then we have NAT (Network Address Translation). This is a service usually run on a router. It solves a big problem: the IPv4 address shortage. There are only about 4.3 billion possible IPv4 addresses, and the world has many more devices. NAT allows a whole family or office to share a single public IP address. The router assigns each device a private IP address (like 192.168.1.10) that's only valid inside the local network. When a device wants to access the internet, the router translates the private source IP to its public IP and remembers which internal device made the request. When the response comes back, it reverses the translation and forwards the data to the correct device. There are different types of NAT: Static NAT (one-to-one mapping of a private IP to a public IP), Dynamic NAT (a pool of public IPs used on a first-come, first-served basis), and PAT (Port Address Translation), also called 'NAT overload', which is the common type that lets multiple devices share one public IP by using different port numbers.
Other essential services include NTP (Network Time Protocol). Computers have internal clocks that slowly drift. NTP synchronises all devices on a network to a precise time source, like an atomic clock. This is critical for security logs, authentication (Kerberos tickets use timestamps), and scheduled tasks. If your computer's clock is off by even a few minutes, you might not be able to log into a corporate network because the system thinks your password request is a replay attack.
SNMP (Simple Network Management Protocol) is used by network administrators to monitor and manage network devices like routers, switches, and printers. A network monitoring tool uses SNMP to query a device and ask, 'How much traffic is on port 1?' or 'Is the fan speed normal?'. The device sends back structured data. SNMP has different versions: v1 and v2c use a 'community string' (effectively a shared password) for security, while v3 adds encryption and authentication.
Finally, consider LDAP (Lightweight Directory Access Protocol) and its Microsoft implementation, Active Directory (AD). LDAP is a protocol used to access and maintain distributed directory information services over an IP network. Think of it as a phone book for a whole company. It stores information about users (names, passwords, email addresses, department), computers, printers, and permissions. When you log into a corporate Windows machine, the computer uses LDAP to check your username and password against the central directory. It also determines what resources you're allowed to access. AD is the service that runs LDAP and adds replication, group policy management, and security features.
In summary, these services work together. DNS tells your computer where to go. DHCP gives it the address to travel from. NAT translates the address for the outside world. NTP keeps time consistent so logins work. SNMP lets the IT team see if something is broken. LDAP verifies you are who you say you are.
Device Joins Network
A new device (like a laptop) connects to the network, either via Ethernet cable or Wi-Fi. The device knows it needs an IP address to communicate, but it has none at this point. The network interface card (NIC) becomes active and is ready to request configuration.
DHCP Discovery (Broadcast)
The laptop sends out a special broadcast message called a 'DHCPDISCOVER' to the whole local network. Since it doesn't yet know the DHCP server's address, it sends the message to the broadcast IP (255.255.255.255) to say, 'Is there a DHCP server here? I need an IP address.' The source IP of this message is 0.0.0.0 because the laptop has no IP yet.
DHCP Offer (Unicast/Broadcast)
The DHCP server on the network receives the discover message. It then reserves an available IP address from its pool (the 'scope') and sends back a 'DHCPOFFER' message. This message includes the offered IP address, the subnet mask, the default gateway, and the DNS server addresses. The offer is typically sent as a broadcast or a unicast to the client's MAC address.
DHCP Request and Acknowledgment
The laptop receives the offer and sends a 'DHCPREQUEST' message back, essentially saying, 'Yes, I want to use that IP address.' The DHCP server finalises the assignment by sending a 'DHCPACK' (acknowledgement) message. The laptop now applies the IP settings, and a 'lease' is created, meaning the IP address is reserved for the laptop for a set period (e.g., 24 hours). The laptop can now use the network.
DNS Resolution for Web Browsing
The user opens a browser and types a domain name, like 'www.courseiva.com'. The laptop's operating system checks its local DNS cache first. If not found, it sends a DNS query (using UDP port 53) to the DNS server address it received in the DHCP step. The DNS server looks up the 'A' record for that name and responds with the corresponding IP address (e.g., 192.0.2.10). The browser then uses that IP to initiate a connection.
NAT Translation for Internet Access
The laptop's request to the web server is sent with its private IP (e.g., 192.168.1.10) as the source. The router, acting as a NAT gateway, receives this packet. It changes the source IP address to the router's public IP address (e.g., 203.0.113.5) and changes the source port to a unique high-numbered port. It logs this mapping in its translation table. The packet is then sent to the internet, and the web server sees the request as coming from the router's public IP.
Response and Reverse NAT
The web server sends its response back to the router's public IP address and the specific port. The router checks its translation table, finds the original private IP and port of the laptop, and reverses the translation. The packet is then forwarded to the laptop. The user sees the webpage load. This whole process happens in milliseconds for every packet of data.
Imagine you are a junior IT support technician for a medium-sized marketing agency with 50 employees. It's Monday morning, and the CEO calls you: 'I can't access the company's client portal website, and my email is not sending.' Here's the concrete step-by-step scenario of what you do and why the network services knowledge is vital.
First, you start by checking the obvious: is the CEO's computer connected to the network? You ask them to look at the network icon in the system tray. It shows a yellow exclamation mark, indicating 'No Internet access'. This immediately tells you the issue is at the network connectivity level, not with a specific application. You then open a command prompt on your own working machine and use the 'ipconfig' command to see the IP address assigned to your computer. You ask the CEO to do the same. Their output shows an IP address starting with 169.254.x.x. This is a clue: it's an Automatic Private IP Addressing (APIPA) address, which Windows assigns itself when it cannot reach a DHCP server. The DHCP server has failed or is unreachable.
Next, you connect to the network server room remotely, or walk in to look at the server acting as the DHCP server. You check the server's network connection and the DHCP service status. You find the DHCP service has stopped. You restart the service. Then you ask the CEO to release and renew their IP address: 'ipconfig /release' followed by 'ipconfig /renew'. Their computer now gets a proper IP address from the renewed DHCP scope. The yellow exclamation mark disappears. Now they can access the internet, but they still cannot get to the client portal.
You ask the CEO to try accessing the portal again and note the exact error. It says, 'DNS_PROBE_FINISHED_NXDOMAIN'. The 'NXDOMAIN' part means the DNS server responded, but it said the domain name doesn't exist. The DNS service is running, but a specific record is wrong. You check the DNS server's forward lookup zone. The 'A' record for the client portal, 'portal.clientcompany.com', is missing a typo in the IP address. You correct it to the proper IP address. You then flush the DNS cache on the CEO's computer using 'ipconfig /flushdns' and ask them to try again. The portal loads.
Later in the week, a different problem arises: a user reports that their computer's clock is wrong, which is causing them to fail authentication to the company's VPN. You check the NTP settings on their computer. It's set to a local time server that has stopped synchronising. You reconfigure the client to point to a reliable external NTP pool like 'pool.ntp.org' and trigger an immediate manual sync using the 'w32tm /resync' command. Their clock corrects itself, and VPN login works again.
In another scenario, you use an SNMP monitoring tool to discover that one of the network switches is running at 95% CPU usage. The tool, using an SNMP query, reveals the culprit: a faulty network cable causing constant transmission errors (CRC errors). You locate the physical cable and replace it, preventing a potential network outage.
In a larger company, you might use LDAP to create a new user in Active Directory. When a new graphic designer joins, you open the 'Active Directory Users and Computers' console. You create a new user object, setting their login name, password, and adding them to the appropriate security groups (e.g., 'Marketing', 'VPN Users', 'FileShare-Access'). This LDAP-based action creates their digital identity. The next day, they sit down at a new workstation, log in using their new credentials, and the LDAP-based authentication validates them and applies group policies that automatically map network drives.
These are the real-world actions an IT professional takes daily. They aren't just troubleshooting; they are diagnosing which network service (DHCP, DNS, NTP, SNMP, LDAP) has failed and applying the specific fix.
The CompTIA A+ 220-1101 exam (note the correct exam code is 220-1101, not 220-1201 as stated in the prompt, but I will answer as instructed for 220-1201 context) tests objective 2.5 by asking you to identify the role of each network service and, critically, to differentiate between them. The exam does not ask you to configure a DHCP server in multiple-choice questions, but it does expect you to know what each service does and which protocol it uses.
Question types you will see: - 'Which of the following services is responsible for assigning IP addresses to devices on a network?' The answer is DHCP. - 'A user reports that they can access a website by its IP address but not by its domain name. Which service is most likely malfunctioning?' The answer is DNS. - 'Which protocol is used to automatically synchronise the time on network devices?' The answer is NTP.
Exam traps you must avoid:
The exam likes to confuse 'DNS' with 'DHCP'. Remember: DNS translates names to IPs (phone book), DHCP assigns IPs to devices (address giver).
They will test the concept of 'APIPA'. If a computer is set to obtain an IP address automatically (DHCP) but the DHCP server is down, the computer will self-assign an address in the 169.254.0.0/16 range. The correct answer is 'APIPA address' (also called 'link-local address').
They may ask about the 'default gateway'. The default gateway is the IP address of the router that allows a device to communicate with devices on other networks, including the internet. DHCP often provides this address.
For NAT, they may describe a scenario: 'A company has 200 computers but only one public IP address. Which service allows all computers to share that single IP?' The answer is NAT (or more specifically, PAT).
The exam sometimes tests SNMP version differences. The key point: SNMPv3 provides authentication and encryption, making it much more secure than v1/v2c which use plain-text community strings.
LDAP vs. Active Directory: They might ask 'Which service provides a centralised directory of user accounts?' Both LDAP and AD are correct, but AD is the Microsoft implementation that uses LDAP as its primary access protocol. Know that AD relies on DNS and Kerberos for authentication. AD is often tested in the context of domain services.
The trap with 'Lease': DHCP 'leases' IP addresses. A lease can expire. The exam might ask: 'What happens to a device's IP address when its DHCP lease expires?' The correct answer is the device must request a new lease and may receive a different IP address.
Port numbers are frequently tested alongside services. You must memorise these:
- DHCP: UDP 67 (server) and 68 (client) - DNS: UDP and TCP 53 - HTTP: TCP 80, HTTPS: TCP 443 - NTP: UDP 123 - SNMP: UDP 161 (queries), UDP 162 (traps) - LDAP: TCP 389, LDAPS (secure): TCP 636
Key definitions to memorise for the exam:
DNS: Translates fully qualified domain names (FQDNs) to IP addresses.
DHCP: Dynamically assigns IP addresses and configuration parameters to hosts.
NAT: Translates private IP addresses to a public IP address (and vice versa) for internet access.
NTP: Synchronises clocks across network devices.
SNMP: Monitors and manages network devices.
LDAP: Accesses and maintains directory services (user databases).
The exam will also test your understanding of how these services interact. For instance, a computer gets an IP address via DHCP, which also tells it the DNS server's IP. Then, when you browse a website, the computer queries the DNS server (using UDP port 53) to resolve the domain name. The correct sequence is DHCP, then DNS. This cause-and-effect reasoning is a common multi-concept question.
DNS translates human-readable domain names into machine-readable IP addresses, like a phone book for the internet.
DHCP automatically assigns IP addresses and other network configuration settings to devices, eliminating the need for manual setup.
NAT allows multiple devices on a private network to share a single public IP address, conserving the limited IPv4 address space.
NTP synchronises all network device clocks to a common time source, which is critical for security logs and authentication protocols like Kerberos.
SNMP enables network administrators to monitor and manage devices remotely by querying them for status and performance data.
LDAP provides a centralised directory of user accounts and resources, allowing for single sign-on and permission management across a network.
When a DHCP server is unreachable, Windows devices automatically assign themselves an APIPA address in the 169.254.0.0/16 range, which only allows local network communication.
The default gateway, often provided by DHCP, is the router's IP address that connects the local network to other networks, including the internet.
These come up on the exam all the time. Here's how to tell them apart.
DNS (Domain Name System)
Translates human-readable domain names (like google.com) into IP addresses.
Uses UDP and TCP port 53.
Stores and serves records such as A, AAAA, CNAME, and MX records.
DHCP (Dynamic Host Configuration Protocol)
Automatically assigns IP addresses and network configuration to devices.
Uses UDP ports 67 (server) and 68 (client).
Manages a pool of IP addresses and leases them to clients for a set time.
Static IP
Manually configured on a device and never changes.
Requires you to know network settings (subnet mask, gateway, DNS) and type them in.
Useful for servers and devices that must always have the same address.
Dynamic IP (via DHCP)
Assigned automatically by a DHCP server and can change over time.
Easy to set up — just turn on 'Obtain an IP address automatically'.
Ideal for client devices like laptops and phones that move between networks.
NAT (Network Address Translation)
Operates at the network layer (Layer 3) of the OSI model.
Translates multiple private IP addresses to a single public IP address.
Transparent to the client device — no configuration is needed on the client.
Proxy Server
Operates at the application layer (Layer 7).
Acts as an intermediary for specific traffic (e.g., web traffic), forwarding requests and responses.
Often requires clients to be configured to use the proxy server.
SNMP (Simple Network Management Protocol)
Used to actively poll network devices for status (e.g., CPU load, interface errors).
Uses UDP ports 161 (queries) and 162 (traps).
Returns structured data that can be parsed by monitoring tools.
Syslog
Used to passively collect and store log messages generated by network devices.
Uses UDP port 514 by default.
Stores unstructured log text that is useful for security analysis and troubleshooting.
Active Directory (LDAP-based)
Centralised user database stored on domain controllers.
User can log into any computer joined to the domain with same credentials.
Supports group policies, single sign-on, and centralised security management.
Local User Account
User account exists only on a single computer.
User can only log into that specific machine.
No central management; each computer must be configured separately.
Mistake
DNS and DHCP are the same thing because they both involve addresses.
Correct
DNS translates domain names to IP addresses (a phone book), while DHCP assigns IP addresses to devices (a landlord giving out apartment numbers). They solve completely different problems.
Beginners see 'address' in both definitions and conflate them. The similarity is superficial; the functions are distinct.
Mistake
If I can ping a website's IP address but not its name, the problem is my internet connection.
Correct
The internet connection is working fine (ping works). The problem is specifically the DNS service, which is failing to translate the name to the IP. The connection itself is healthy.
People assume 'no internet' means everything is broken, when often a single service (DNS) is the culprit. Troubleshooting requires isolating the symptom.
Mistake
NAT is a security protocol that protects against hackers.
Correct
NAT was designed to conserve IPv4 addresses, not as a security feature. While NAT does hide internal IPs from the public internet (providing some obscurity), it is not a firewall and offers no real encryption or security policy enforcement. A firewall is separate.
Because NAT hides internal IPs, it feels like a security barrier. But the primary purpose is address translation, not security. The exam tests the core purpose, not side effects.
Mistake
If a device gets a 169.254.x.x address, it means the network cable is unplugged.
Correct
A 169.254.x.x address (APIPA) means the device tried to contact a DHCP server and failed. It could be the cable, the DHCP server being down, the switch port being disabled, or a faulty router. It is a symptom of no DHCP, not necessarily a loose cable.
People see 'no network' and jump to the most physical cause. APIPA is a specific autoconfiguration result that points to a DHCP failure, which can have many causes.
Mistake
SNMP is only used for security monitoring.
Correct
SNMP is a general-purpose network management protocol. It can monitor bandwidth usage, CPU load, temperature, fan speed, and uptime of network devices. It is used for capacity planning, fault detection, and performance monitoring, not just security.
The word 'management' and 'simple' might make people think of simple security tools. But SNMP covers a broad range of metrics, not exclusively security.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
It means your computer is asking a DNS server to translate a domain name into an IP address, but the server is not responding or cannot find the record. This usually means the DNS server is down, misconfigured, or your computer has the wrong DNS server address.
A DHCP lease is a temporary assignment of an IP address to a device for a set period (like 24 hours). When it expires, the device must renew the lease. If it renews successfully, it keeps the same IP; if it fails, the device loses its IP and eventually gets a new one or falls back to APIPA.
No, they are different. NAT only translates IP addresses; it does not inspect or filter traffic for security. A firewall actively blocks or allows traffic based on rules. Many home routers combine both functions in one box, but they remain separate services.
A public IP address is unique on the internet, and it is assigned by your ISP. A private IP address is used only within a local network (like your home or office) and is not routable on the internet. NAT translates private IPs to a single public IP for internet access.
The exam tests your ability to associate protocols with their default ports. For example, DNS uses UDP and TCP port 53, DHCP uses UDP 67/68, and HTTPS uses TCP 443. Knowing these helps you identify services in troubleshooting scenarios.
LDAP stands for Lightweight Directory Access Protocol. It is used to access and manage a central directory of user names, passwords, and permissions, so employees can log into any computer on the network with the same credentials.
Clocks on network devices will drift apart. This can cause authentication failures (Kerberos tickets rely on time stamps), inaccurate log timestamps for security investigations, and issues with scheduled tasks that run at specific times.
You've just covered Network Services and Connectivity — now see how well it sticks with free 220-1201 practice questions. Full explanations included, no account needed.
Done with this chapter?