Windows Networking and File Sharing

Windows networking is built on the TCP/IP protocol suite, which is the standard for communication across the internet and most local networks. In Windows, you configure network settings primarily through the Network and Sharing Center, Settings app, or command-line tools like netsh, ipconfig, and powershell. The exam expects you to know how to configure IP addresses (static vs. dynamic), DNS, and default gateway, as well as understand network locations (Private, Public, Domain) and how they affect firewall rules and discovery.

Every network interface in Windows needs an IP address to communicate. There are two methods: - Dynamic Host Configuration Protocol (DHCP): The client sends a broadcast DHCPDISCOVER message, the DHCP server responds with DHCPOFFER, the client sends DHCPREQUEST, and the server acknowledges with DHCPACK. This process uses UDP ports 67 (server) and 68 (client). Windows clients by default obtain an IP automatically. If DHCP fails, Windows uses Automatic Private IP Addressing (APIPA) to assign an address in the 169.254.0.0/16 range with a subnet mask of 255.255.0.0. APIPA addresses are not routable and only allow communication with other APIPA hosts on the same subnet. - Static IP: Manually configured using the network adapter's properties. You must provide IP address, subnet mask, default gateway, and DNS servers. Static IPs are typically used for servers or devices that need a fixed address.

To check IP configuration, use:

ipconfig /all

This displays all network adapters, their IP addresses, MAC addresses, DHCP status, lease information, and DNS servers.

The subnet mask determines which part of the IP address identifies the network and which identifies the host. For example, with a mask of 255.255.255.0, the first three octets are the network portion. The default gateway is the IP address of the router that forwards traffic to other networks. Without a correct default gateway, your computer can only communicate within its own subnet.

Domain Name System (DNS) resolves hostnames to IP addresses. In Windows, you can configure DNS servers manually or via DHCP. To verify DNS resolution, use:

nslookup example.com

Or:

ping -n 1 example.com

If DNS fails, you may get a 'Name not resolved' error. Windows also supports DNS suffixes and the Hosts file (located at C:\Windows\System32\drivers\etc\hosts) for manual name-to-IP mappings. The Hosts file takes precedence over DNS.

Windows categorizes networks into three profiles: - Public: Used for networks like coffee shops or airports. Network discovery and file sharing are turned off by default. Firewall rules are more restrictive. - Private: For home or work networks you trust. Network discovery and file sharing are enabled. Firewall rules are less restrictive. - Domain: Used when the computer is joined to an Active Directory domain. Settings are managed by Group Policy.

You can change the network location via Settings > Network & Internet > Wi-Fi or Ethernet > click on the network name > change network profile. The exam may ask which profile to choose for a home network (Private) or a public hotspot (Public).

Network discovery allows your computer to see other devices on the network and be seen by them. It uses the Function Discovery Resource Publication (FDResPub) and Function Discovery Provider Host (FDPHost) services, along with SSDP (Simple Service Discovery Protocol) and NetBIOS over TCP/IP. To enable network discovery, go to Control Panel > Network and Sharing Center > Advanced sharing settings. For file sharing, Windows uses the Server Message Block (SMB) protocol, which operates over port 445 (TCP). SMB allows sharing of files, printers, and other resources.

To share a folder: 1. Right-click the folder > Properties > Sharing tab > Share. 2. Add users or groups (e.g., Everyone) and set permissions (Read or Read/Write). 3. Click Share and note the network path (e.g., \\COMPUTERNAME\ShareName).

Permissions are cumulative: the effective permission is the most permissive combination of share permissions and NTFS permissions. For example, if share permissions allow Read and NTFS permissions allow Write, the effective permission is Write (since NTFS is more restrictive? Actually, the most restrictive permission applies when combining share and NTFS: the effective permission is the more restrictive of the two. So if share says Read and NTFS says Write, the user gets Read. If share says Full Control and NTFS says Read, the user gets Read. This is a common exam trap.

Note: HomeGroup was a feature for easy sharing in Windows 7, 8, and 10. It has been removed from Windows 10 (version 1803 and later) and Windows 11. The exam may reference it historically, but modern Windows uses workgroups or domains.

Windows Firewall with Advanced Security can block or allow traffic based on rules. By default, it blocks inbound connections except those matching an allow rule. For file sharing, you may need to enable the 'File and Printer Sharing' inbound rule. You can manage firewall via Control Panel or wf.msc.

Remote Desktop Protocol (RDP) allows remote connection to another Windows computer. Port 3389 (TCP). To enable: System Properties > Remote tab > Allow remote connections. The exam may ask about RDP vs. Remote Assistance (which uses port 3389 as well, but requires user invitation).

Understanding these concepts is crucial for the exam. You will be asked to configure network settings, choose appropriate profiles, troubleshoot connectivity, and set up file sharing. Practice using the command-line tools and know the default ports and protocols.

In an enterprise environment, Windows networking and file sharing are fundamental. Consider a company with 500 employees using Windows 10/11 workstations joined to an Active Directory domain. The IT team configures DHCP to assign IP addresses from a specific scope (e.g., 10.0.1.0/24) with DNS servers pointing to internal domain controllers. File servers running Windows Server share departmental folders using SMB. For example, the Accounting department has a shared folder '\\fileserver\accounting' with NTFS permissions granting Read/Write to the 'Accounting' AD group and Read to 'Auditors'. Share permissions are set to 'Everyone: Full Control' so that NTFS permissions alone control access. This is a common best practice: set share permissions to Full Control for Everyone and rely on NTFS for fine-grained control.

Another scenario: A remote office with a small workgroup of 10 users. They use static IPs because there is no DHCP server. They share a printer via 'File and Printer Sharing' and a common folder for documents. Troubleshooting often involves checking that all computers are on the same subnet (e.g., 192.168.0.x with mask 255.255.255.0) and that the Windows Firewall allows SMB traffic (port 445). If a user cannot access the shared folder, the help desk checks if network discovery is enabled, if the folder is shared, and if the user has permissions. They might use net use to map a drive: net use Z: \\SERVER\Share /user:DOMAIN\username. If that fails, they check DNS resolution with nslookup SERVER or ping the server by name.

Common misconfigurations include: forgetting to change network profile from Public to Private (blocks discovery), incorrect subnet mask (causing 'unreachable' errors), or APIPA addresses from a failed DHCP server. In large networks, performance considerations include SMB Multichannel for faster transfers and disabling SMB1 due to security vulnerabilities (like EternalBlue). The exam expects you to know these real-world practices, including the fact that SMB1 is disabled by default in modern Windows and should remain disabled.