2.1.7. Configure Microsoft Windows networking features on a client/desktop. (Obj. 1.7)

💡 First Principle: Correctly configuring a client's network settings is fundamental to enabling communication with local resources and the internet.

A computer is only as useful as its ability to communicate with other devices. As a technician, you are responsible for ensuring a Windows client can connect to the network correctly. This involves more than just plugging in a cable; it requires understanding the logical configuration of network identity, addressing, and security profiles.

The most fundamental decision is whether the computer will be part of a Workgroup or a Domain. A workgroup is a simple, decentralized peer-to-peer network, suitable for a SOHO (Small Office/Home Office) environment. All computers are equal, and security is managed on a per-machine basis. A domain, powered by Active Directory, is for corporate environments. It provides centralized authentication, management, and security. A computer must be explicitly "joined" to the domain to be managed by it.

Next is the client's network address configuration. This is handled in the network adapter's properties.

• IP Addressing: An IP address can be static (manually assigned and permanent) or dynamic (automatically assigned by a DHCP server). Almost all client workstations use dynamic addressing for ease of management. Servers, printers, and routers typically use static IPs so they can always be found at the same address.
• DNS Settings: The Domain Name System (DNS) translates human-friendly names (like www.google.com) into IP addresses. A client must be configured to point to the correct DNS server. In a corporate environment, this will be an internal DNS server that can resolve both internal resource names and external internet addresses.
• Default Gateway and Subnet: A static configuration needs four values: IP address, subnet mask, default gateway (the router's address, required to reach any other network, including the internet) and DNS server. A static address must sit in the same subnet as the gateway, must not duplicate the gateway or another host, and should be outside the DHCP pool. Without a gateway the PC can still reach local hosts, but nothing beyond its own subnet.
• APIPA (169.254.x.x): A DHCP client that cannot reach a DHCP server assigns itself an address in 169.254.0.0/16. Seeing one means "DHCP failed" - check the cable/Wi-Fi link and the DHCP server, then ipconfig /renew. It is a link-local address: not routable, and never one to assign statically.
• Proxy Settings (Settings > Network & internet > Proxy): Sends the client's web traffic to an intermediary proxy server, which forwards it for content filtering, caching or logging. A web proxy handles the browser/app requests sent to it; the default gateway routes all traffic leaving the subnet, and a VPN encrypts traffic in a tunnel to a private network.
• Metered Connections: Marking a Wi-Fi or Ethernet connection as metered tells Windows to limit background data - some Windows Update downloads are deferred and apps such as OneDrive may pause syncing. It changes neither speed nor security.

Finally, Windows uses network profiles to apply different security settings based on the network's trust level. When you first connect to a new network, Windows asks if it is Public or Private. Selecting Private (for your trusted home or office network) turns on features like network discovery and file sharing. Selecting Public (for an untrusted network like a coffee shop or airport) locks the computer down, making it invisible to other devices on the network and disabling sharing to protect it from potential threats. A third profile, Domain, is applied automatically (never chosen by the user) when a domain-joined computer detects it can reach its domain controller, and domain Group Policy controls its firewall rules. File and Printer Sharing (Advanced sharing settings) is the switch that lets a PC offer its local folders and printers to other computers; keep it off on Public networks.

Technician's Action Plan: Scenario: You are setting up a new PC for an employee in the accounting department. The office uses an Active Directory domain called corp.local. The internal DNS server is at 10.10.1.5, and the department has a network printer at the static IP 10.10.20.100.

1. Physical Connection: Connect the PC to the network via an Ethernet cable.
2. Join the Domain:
   • Navigate to System Properties (right-click This PC -> Properties -> Domain or workgroup).
   • Click "Change settings", then "Change...".
   • Select the "Domain" radio button and type corp.local.
   • You will be prompted for credentials. Enter the username and password of a domain administrator account that has privileges to join computers to the domain.
   • Reboot the computer as prompted.
3. Verify Network Configuration: After rebooting, have the user log in with their corporate credentials. Open a command prompt and run ipconfig /all.
   • Confirm the PC received an IP address from the DHCP server (e.g., 10.10.15.121).
   • Crucially, confirm that the DNS Server listed is the internal one (10.10.1.5). If it's not, you'll need to manually configure it in the network adapter properties.
4. Configure Network Profile: Since this is a trusted corporate network, ensure the network profile is set to Private or Domain to allow access to local resources.
5. Install the Network Printer: Go to Devices and Printers -> Add a printer. Choose "The printer that I want isn't listed". Select "Add a printer using a TCP/IP address or hostname". Enter the printer's static IP address (10.10.20.100), and follow the prompts to install the correct driver. Print a test page to verify.

Reflection Question: Why is it important to configure a client's network profile as "Public" when connecting to an untrusted network like a coffee shop Wi-Fi?