Windows Networking on the Desktop

Connecting a Windows PC to a network involves several independent layers: the network model the machine belongs to, the profile Windows assigns to the connection, the firewall rules that govern traffic, the TCP/IP parameters the adapter uses, and the connection method itself. This lesson applies the Core 1 Networking concepts you already know to the Windows client configuration context — it does not re-teach IP addressing, DNS, or DHCP. The focus is where to configure those parameters in Windows and what a technician does in each scenario.

Domain Joined vs Workgroup

Every Windows PC participates in one of two network models.

Domain — A Windows domain is a centrally managed network anchored by a Windows Server running Active Directory (AD). Every machine in the domain authenticates against AD:

• Single sign-on: A domain user logs in with one account that works on any domain-joined machine. No per-machine account setup required.
• Centralized user account management: Accounts, passwords, and groups live in Active Directory on the server, not on individual machines.
• Group Policy: Administrators push configuration and security settings to all machines from a central location — password policies, software restrictions, drive mappings, and more.
• Edition requirement: Only Windows Pro, Pro for Workstations, and Enterprise can join a domain. Windows Home cannot. See L3 for the complete edition breakdown — this lesson does not duplicate it.
• Typical environment: Corporate offices, schools, and any organization managing more than a handful of machines.

Workgroup — The default Windows peer-to-peer configuration. Each machine stands alone:

• No central server: Each machine manages its own local user accounts. Accessing a resource on another machine requires a matching local account on that machine — accounts are not shared.
• Peer-to-peer sharing: Files and printers are shared directly between machines. Any machine can be a resource provider. There is no dedicated server, no centralized policy.
• Any edition: Windows Home, Pro, and Enterprise can all participate in a workgroup. There is no edition restriction.
• Typical environment: Home networks and small offices that do not need centralized management.

Shared Resources

Both models support sharing resources across the network:

• Shared printers: A printer attached to one machine is shared so other network machines can print to it. In domain environments, a dedicated print server role manages this at scale. In workgroups, one peer machine shares its local printer directly.
• File servers: In domain environments, a dedicated file server stores shared folders with access controlled by domain account permissions. In workgroups, peers share folders directly from their own drives.
• Mapped drives: A network share can be assigned a local drive letter — Z:, Y:, etc. — so it appears in File Explorer and applications as though it were a local drive. The drive reconnects automatically at logon when configured to do so. The net use command maps drives from the command line — see L5 for syntax; this lesson does not re-teach it.

Public vs Private Network

When Windows connects to a new network for the first time, it asks you to classify the connection. The classification controls which firewall profile Windows applies. Three classifications exist:

• Private: Windows treats the network as trusted. Network discovery is enabled (the PC announces its presence so other devices can find it), and file and printer sharing is allowed. Use Private for home routers and internal office networks you control.
• Public: Windows treats the network as untrusted. Network discovery is disabled (the PC is invisible to other devices on the network), and unsolicited incoming connections are blocked more aggressively. Use Public for coffee shops, airports, hotel Wi-Fi, or any network you do not control.
• Domain: Automatically assigned when a domain-joined machine can reach its Active Directory domain controller. Domain profile settings are controlled by Group Policy rather than local user configuration — no manual classification needed.

Windows Defender Firewall

Windows Defender Firewall is the host-based firewall built into Windows. It filters traffic based on rules and applies different rulesets per network profile. A technician most often interacts with it when a newly installed application cannot receive incoming connections.

Application exceptions: Control Panel → Windows Defender Firewall → "Allow an app or feature through Windows Defender Firewall." Each application can be permitted individually, with separate checkboxes for the Domain, Private, and Public profiles. An application can be allowed on Domain and Private while remaining blocked on Public.

Inbound vs outbound: By default, Windows Defender Firewall blocks unsolicited inbound connections but permits outbound connections. Advanced rules for both directions are configured in Windows Defender Firewall with Advanced Security (wf.msc). Core 1 Networking covered the stateful inspection concepts; here the focus is on the Windows administration surface.

Client Network Configuration

The four parameters a technician configures on a Windows network adapter — these are Core 1 Networking concepts applied here to the Windows configuration path:

1. IP address — the machine's address on the network
2. Subnet mask — identifies the network vs host portion of the address
3. Default gateway — the router address for off-subnet traffic
4. DNS server addresses — primary and secondary name server addresses

Where to configure: Network and Sharing Center → Change adapter settings → right-click the adapter → Properties → "Internet Protocol Version 4 (TCP/IPv4)" → Properties. This is the adapter configuration dialog; L6 covered how to reach Network and Sharing Center from Control Panel — this lesson does not duplicate that path in detail.

Static vs dynamic:

• Dynamic (DHCP): Windows obtains all four parameters automatically from the network's DHCP server. The dialog shows "Obtain an IP address automatically." This is the default for most client workstations and requires no manual entry.
• Static: The technician enters all four parameters manually. Used for servers, network printers, access points, and any device that must respond at a predictable, unchanging address.

Establishing Network Connections

Wired (Ethernet): Connect the cable. Windows detects the adapter, classifies the network (Public or Private prompt for new networks), and requests a DHCP address. For most environments, no further configuration is needed. Manual IP assignment follows the path above.

Wireless (Wi-Fi): Click the network icon in the taskbar, or open Settings → Network & Internet → Wi-Fi. Windows lists available networks by SSID. Select the network, enter the passphrase or credentials, and connect. Enterprise networks often use 802.1X authentication — a username and password rather than a shared passphrase — flag for verification. Windows saves the network profile and reconnects automatically. Manage saved networks in Settings → Network & Internet → Wi-Fi → Manage known networks.

VPN (Virtual Private Network): Windows includes a built-in VPN client. Configure in Settings → Network & Internet → VPN → Add a VPN connection. Required inputs:

• VPN provider: Windows (built-in)
• Server address: the VPN server's hostname or IP address
• VPN type: the protocol — IKEv2, L2TP/IPsec, SSTP, or PPTP (select to match the server)
• Sign-in information: username and password, or certificate

The Core 1 Networking module covered VPN as a concept — this lesson covers only the Windows client configuration surface, not VPN protocol details or tunnel mechanics. Once connected, the VPN appears as a network adapter alongside the physical adapters.

WWAN (Wireless Wide Area Network) / Cellular: Laptops with a built-in cellular modem (eSIM or physical SIM) connect to mobile carrier networks independently of Wi-Fi. The cellular adapter appears in Settings → Network & Internet alongside Wi-Fi and Ethernet as a separate connection type. Used when wired and Wi-Fi connections are unavailable — flag WWAN as a Windows adapter category for verification.

Proxy Settings

A proxy server acts as an intermediary between a Windows client and the internet. Corporate networks commonly route web traffic through a proxy for content filtering, logging, or caching. The client must send its requests to the proxy rather than directly to the destination.

Where to configure: Settings → Network & Internet → Proxy. Two modes:

• Manual proxy setup: Enter the proxy server's address (hostname or IP) and port number as provided by the network administrator — port numbers vary by organization and proxy server software. This setting applies globally to Windows-aware applications (Edge, Internet Explorer, most business apps).
• Automatic configuration script (PAC file): Enter the URL of a PAC (Proxy Auto-Configuration) file. The PAC file is a script that determines, per URL, whether to connect directly or route through a specific proxy server. Internal sites bypass the proxy; external sites go through it. Flag PAC file as a proxy configuration method for exam relevance verification.

The legacy path — Control Panel → Internet Options → Connections → LAN settings — provides the same configuration for Internet Explorer-era environments and remains exam-relevant.

Network Paths in File Explorer

Network shares are addressed using UNC (Universal Naming Convention) paths.

UNC format: \\servername\sharename

• Two backslashes before the server name
• One backslash between the server name and the share name
• The server name can be a hostname or an IP address

Examples:

• \\fileserver01\documents — the "documents" share on server "fileserver01"
• \\192.168.1.50\shared — same, using an IP address instead of a name
• \\fileserver01\documents\reports\2024 — includes a subfolder path after the share name

How to access: Type the UNC path directly into File Explorer's address bar and press Enter. Windows connects to the share and prompts for credentials if required. This accesses the share without assigning a drive letter. For persistent access, map the share to a drive letter: in File Explorer, right-click "Network" → "Map network drive," or use the net use command (see L5 for syntax).

Metered Connections

A metered connection tells Windows the connection has limited data — typically a cellular connection or a Wi-Fi hotspot with a data cap. Windows reduces background data consumption on metered connections:

• Windows Update: On a metered connection, Windows defers large feature updates and non-critical app updates to conserve data. Critical security updates still download automatically regardless of the metered flag.
• Microsoft Store: App updates and background downloads are reduced.
• OneDrive and sync services: Large file uploads and syncs may be paused or slowed — flag OneDrive's specific behavior for verification.
• Apps that respect the metered flag: Reduce polling frequency and background data usage.

Where to configure: Settings → Network & Internet → Wi-Fi → [network name] → Properties → "Set as metered connection" toggle. For Ethernet connections: Settings → Network & Internet → Ethernet → [connection name] → Properties. Cellular connections are typically flagged as metered automatically.

The check questions below test your ability to choose the right network model, classify network profiles, configure IP settings, navigate to network shares, and apply metered connection behavior to a real scenario.