Resources6 min read·Apr 11, 2026

Complete Windows Networking Checklist for Small Offices

A printable, step-by-step checklist for setting up and maintaining reliable file sharing on a small office Windows network. Covers initial setup, common failures, and maintenance.

How to Use This Checklist

Work through each section sequentially for a new setup. For diagnosing an existing problem, jump to the relevant section. Tick items off as you confirm them — most networking issues in small offices are caused by one unchecked item in this list.

Section 1 — Hardware Foundation

  • All file-sharing machines are connected via wired Ethernet (Cat5e or better) where practical
  • Switch or router supports Gigabit Ethernet (most equipment purchased after 2015 does)
  • All cables are Cat5e or Cat6 — Cat3 and Cat5 (not Cat5e) are limited to 100 Mbps
  • No cables exceed 100 metres in length between devices
  • Network adapters report 1000 Mbps link speed (check: Settings → Network → your connection)
  • For WiFi-dependent machines: confirmed WiFi 5 (802.11ac) or WiFi 6 (802.11ax) adapter and access point

Section 2 — Network Profile (The Silent Killer)

This is the most common cause of sudden file sharing failures.

  • All machines are on a Private network profile
    • Windows 11: Settings → Network and Internet → click your active connection → Network Profile Type → Private Network
    • Windows 10: Settings → Network and Internet → Status → click your connection → find and switch to Private
  • Verified on every machine that needs to share — not just the host
  • Checked after any recent Windows Update (updates occasionally reset this)

Section 3 — Required Services

These four services must be Running with Startup Type = Automatic.

Check via: Win+R → services.msc → find each service

  • Function Discovery Resource Publication — Running, Automatic
  • SSDP Discovery — Running, Automatic
  • UPnP Device Host — Running, Automatic
  • DNS Client — Running, Automatic

Quick fix if any are wrong (PowerShell as Administrator):

Set-Service FDResPub -StartupType Automatic
Set-Service SSDPSRV -StartupType Automatic
Set-Service upnphost -StartupType Automatic
Start-Service FDResPub, SSDPSRV, upnphost

Section 4 — Sharing Configuration (Host Machine)

  • Advanced Sharing Settings → Private → Network Discovery: On
  • Advanced Sharing Settings → Private → File and Printer Sharing: On
  • The folder to be shared has been shared via Properties → Sharing → Advanced Sharing
  • Share name set (simple, no spaces preferred: e.g., Projects)
  • Permissions configured: appropriate users have Read or Full Control
  • NTFS permissions also set (separate from share permissions — both must allow access)

Section 5 — Windows Firewall

  • Windows Defender Firewall is not blocking file sharing
    • Check: Control Panel → Windows Defender Firewall → Allow an app through → confirm "File and Printer Sharing" is ticked for Private network
  • Third-party antivirus/security suite is not blocking LAN traffic
    • Test by temporarily disabling and retrying — re-enable immediately after testing

Section 6 — Authentication and Credentials

  • Password-protected sharing policy is understood: if enabled, connecting users need a matching local account on the host machine
  • Local accounts exist on the host for each user who needs access (or a shared service account exists)
  • Windows Credential Manager has correct, current credentials for the host machine
    • Control Panel → Credential Manager → Windows Credentials → look for the host machine entry, update if outdated
  • No duplicate credential conflicts (two entries for the same host with different passwords)

Section 7 — Connecting From Other Machines

  • Can reach the host by IP address: open Run (Win+R) → \\192.168.1.X\ShareName → enter credentials → confirms SMB and authentication work
  • Can reach the host by computer name: open Run (Win+R) → \\HOSTNAME\ShareName → confirms name resolution works
  • Mapped drive configured for daily use: right-click This PC → Map network drive → choose letter, enter UNC path, tick "Reconnect at sign-in"
  • Drive letter is consistent across all machines (important for applications that store network paths)

Section 8 — After Each Windows Update (Maintenance)

Run through these quickly after any major Windows cumulative update:

  • All four services (Section 3) still Running / Automatic
  • Network profile still set to Private
  • Mapped drives still connect (open File Explorer, check Z: or whichever letter is mapped)
  • Spot-test one file transfer to confirm throughput is normal

Time to complete this check: approximately 5 minutes

Section 9 — Optional Improvements

  • Reserve a DHCP lease for the host machine in the router settings (prevents IP address from changing, making UNC paths permanently stable)
  • Create a desktop shortcut to \\HOSTNAME\ShareName for all users who need regular access
  • Configure Windows to not require re-entering credentials by saving them via the Map Network Drive dialog
  • Test transfer speed using Task Manager or iperf3 to confirm gigabit throughput is being achieved

Section 10 — Using an Application-Level Tool Instead

If Section 3 through Section 7 fail repeatedly or reset after updates, an application-level file sharing tool removes most of this dependency:

  • Oxolan (Windows): install on each machine, peers discover each other automatically, no Windows networking configuration required
  • LocalSend (Windows, Mac, Linux, iPhone, Android): same approach, cross-platform, free

Get Oxolan for Windows

Mac users: Finder → Connect to Server → smb://IP-ADDRESS/ShareName for SMB access. For application-level transfer, LocalSend works on macOS without any of the above Windows-specific configuration.

Frequently Asked Questions

How long should a first-time setup take? With this checklist as a guide and no pre-existing configuration conflicts: 30–60 minutes for a 2–5 machine office. Most of this is configuration, not actual work. Subsequent setups on the same network are faster.

Should I go through this checklist every month? Only Section 8 (post-update check) is recommended regularly — approximately monthly after Windows Update restarts. The full checklist is for initial setup or diagnosing a failure.

We have a mix of Windows 10 and Windows 11 machines. Does that matter? The checklist applies to both. Windows 10 and 11 have the same dependencies. SMB2 is the negotiated protocol between any combination of Windows 10/11 machines.

Can I automate most of this? The services (Section 3) and network profile (Section 2) can be enforced via Group Policy on Windows Pro and Enterprise. Contact your IT provider if you have Pro licences and want a more permanent enforcement solution.

Done troubleshooting Windows?

Oxolan handles file sharing so you never have to think about this again.

Get Oxolan for Windows
← All articles