Advanced Hardware Lab 7-3: Connect a Computer to a Network
Connecting a computer to a network is one of the most fundamental skills every IT professional, student, and technician must master. But in Advanced Hardware Lab 7-3, you will learn how to physically and logically connect a standalone computer to a local area network (LAN), configure its network settings, and verify successful communication with other devices. Whether you are preparing for a certification exam or building real-world competence, this lab provides the hands-on experience you need to understand networking from the ground up Less friction, more output..
Introduction
In today's interconnected world, no computer exists in true isolation. That's why every device — from a personal laptop to an enterprise server — must connect to a network to share resources, access the internet, and communicate with other systems. Lab 7-3 focuses on the practical process of connecting a computer to a wired Ethernet network, configuring its IP address, subnet mask, default gateway, and DNS settings, and then verifying end-to-end connectivity.
By completing this lab, you will gain a deeper understanding of how data travels across a network and how proper configuration ensures seamless communication.
Learning Objectives
After completing Advanced Hardware Lab 7-3, you should be able to:
- Identify the physical components required for a wired network connection.
- Connect a computer to a network switch or router using an Ethernet cable.
- Configure TCP/IP settings manually and automatically.
- Use command-line tools to verify network connectivity.
- Troubleshoot basic network connection problems.
Required Equipment and Materials
Before starting, make sure you have the following items ready:
- A desktop or laptop computer with a working Ethernet port (RJ-45).
- A Cat 5e or Cat 6 Ethernet cable (straight-through cable).
- A network switch or router with available ports.
- Access to another computer or device on the same network for testing.
- A computer with an operating system installed (Windows 10/11 recommended for this lab).
If your computer does not have a built-in Ethernet port, you may use a USB-to-Ethernet adapter.
Understanding Network Basics
Before plugging in any cables, it helps to understand a few core networking concepts Most people skip this — try not to..
What is a Local Area Network (LAN)?
A LAN is a network that connects computers and devices within a limited area such as a home, office, or school. Devices on a LAN share resources like printers, files, and internet access through a central device — typically a router or switch.
The Role of the Ethernet Cable
An Ethernet cable (also called a network cable) carries data signals between your computer and the network device. The most common types are:
- Cat 5e — supports speeds up to 1 Gbps.
- Cat 6 — supports speeds up to 10 Gbps over shorter distances.
- Cat 6a and Cat 7 — used in high-performance environments.
For this lab, a standard Cat 5e straight-through cable is sufficient.
IP Addressing Fundamentals
Every device on a network needs a unique identifier called an IP address. The most widely used version is IPv4, which uses a 32-bit address written in dotted decimal notation (e.g.Still, , 192. 168.1.10).
- Subnet mask — defines the network portion of the address (e.g., 255.255.255.0).
- Default gateway — the address of the router that connects your local network to other networks.
- DNS server address — translates domain names like www.example.com into IP addresses.
Step-by-Step Procedure
Step 1: Power Off the Computer
Before making any hardware connections, power off your computer completely. This prevents potential damage to the network adapter or the switch port during the connection process.
Step 2: Connect the Ethernet Cable
Take one end of the Ethernet cable and insert it firmly into the RJ-45 port on your computer. Think about it: connect the other end to an available port on the network switch or router. Practically speaking, you should hear a soft click when the connector locks into place. Once connected, power your computer back on That's the part that actually makes a difference. That's the whole idea..
Step 3: Check the Physical Link
After the computer restarts, look at the network adapter LEDs near the Ethernet port. You should see:
- A solid or blinking green/amber light — indicating a physical link is established.
- A blinking activity light — indicating data is being transmitted or received.
If there is no light, try reseating the cable or using a different port on the switch.
Step 4: Configure TCP/IP Settings
Option A: Automatic Configuration (DHCP)
Most modern networks use DHCP (Dynamic Host Configuration Protocol) to assign IP addresses automatically. To enable this on Windows:
- Open Control Panel → Network and Sharing Center → Change adapter settings.
- Right-click on Ethernet and select Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Choose Obtain an IP address automatically and Obtain DNS server address automatically.
- Click OK to save.
Option B: Manual Configuration (Static IP)
In some scenarios, you may need to assign a static IP address:
- Follow steps 1–3 above.
- Select Use the following IP address.
- Enter the following details (adjust based on your network):
- IP Address: 192.168.1.50
- Subnet Mask: 255.255.255.0
- Default Gateway: 192.168.1.1
- Under DNS, enter:
- Preferred DNS Server: 8.8.8.8
- Alternate DNS Server: 8.8.4.4
- Click OK to apply.
Step 5: Verify the Network Connection
Open the Command Prompt by typing cmd in the Windows search bar. Run the following commands to verify connectivity:
ipconfig— Displays your current IP address, subnet mask, and default gateway. Confirm that the values match your configuration.ping 127.0.0.1— Tests the local TCP/IP stack. A successful reply means your network software is working correctly.ping 192.168.1.1— Pings the default gateway. A reply confirms your computer can communicate with the local router.ping 8.8.8.8— Tests internet connectivity through the gateway.- **`
Step 6: Interpret the Ping Results
Once the ping 8.8.8.8 command completes, examine the output:
- Successful replies (e.g., “Reply from 8.8.8.8: bytes=32 time=15ms TTL=117”) indicate that your computer has a functional path to the Internet.
- Request timed out or Destination host unreachable messages suggest a break somewhere in the chain — possibly the cable, the switch, the router, or a firewall.
If you receive replies but they show unusually high latency or packet loss, consider running a longer test (ping -n 30 8.Plus, 8. 8.8) to gather more data before proceeding to the next diagnostic stage Not complicated — just consistent..
Step 7: Test Domain Name Resolution
Connectivity to internet services often depends on DNS. From the same Command Prompt, execute:
nslookup www.google.com
A successful response will display the IP address assigned to the hostname. 8.If the command reports “Non‑existent domain” or times out, the problem may lie with the DNS servers configured on your machine. 4.8 / 8.8.So you can switch to Google’s public DNS (8. 8.4) or your ISP’s DNS and repeat the test.
Real talk — this step gets skipped all the time.
Step 8: Verify Firewall and Security Software
Sometimes security suites block outbound traffic even when the network appears healthy. Open your firewall or antivirus console and confirm that:
- Outbound traffic on TCP port 80 (HTTP) and TCP port 443 (HTTPS) is allowed.
- No custom rules are denying connections from the newly configured Ethernet interface.
After adjusting the settings, re‑run the ping 8.8.8.8 and nslookup commands to confirm that the blockage has been lifted.
Step 9: Reset the Network Stack (Optional but Effective)
If the connection still refuses to cooperate, resetting the underlying components can clear lingering glitches:
- Open an elevated Command Prompt (right‑click → “Run as administrator”).
- Execute the following sequence:
netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns```
3. Restart the computer and repeat the verification steps from Sections 5–7.
---
**Step 10: Document and Verify Persistent Settings**
When everything works as expected, record the final configuration details for future reference:
- IP address (static or DHCP‑assigned)
- Subnet mask, gateway, and DNS servers
- Any custom firewall rules that were modified
Store this information in a text file or a network‑configuration log so that, should the issue reappear, you have a clear baseline to compare against.
---
### Conclusion
Establishing a wired Ethernet connection involves a straightforward sequence: confirming hardware, selecting the appropriate IP acquisition method, and validating each layer of communication. By systematically checking the physical link, configuring TCP/IP settings, and probing both the local network and external Internet resources, you can isolate faults quickly and restore connectivity with confidence. Remember that most connectivity problems stem from a single point of failure — whether it’s a loose cable, a mis‑configured IP address, or an over‑zealous security rule. With the steps outlined above, you now possess a complete troubleshooting toolkit that not only resolves the current issue but also equips you to handle future network hiccups efficiently.