Troubleshooting Wiki

1. Verify SSID & password (watch for smart quotes when copy/pasting).
2. Forget the network, then re‑add.
   • Windows: Settings → Network & Internet → Wi‑Fi → Manage known networks
   • macOS: System Settings → Wi‑Fi → Details → Forget This Network
3. Reset adapter (Windows):

   netsh int ip reset
   netsh winsock reset
   ipconfig /flushdns
   shutdown /r /t 0

4. Remove stale profiles (macOS):

   # Delete SSID from preferred networks, then reconnect
   sudo /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport --delete=SSID

5. Check time & date (cert auth can fail if clock drifts).

1. Test DNS latency vs HTTPS:

   # Windows
   nslookup example.com
   curl -I https://example.com
   
   # macOS/Linux
   dig example.com +stats
   curl -I https://example.com

2. If DNS is slow, switch to a known resolver (temporarily): 1.1.1.1 or 9.9.9.9.
3. Check packet loss / path:

   # Windows
   pathping example.com
   
   # macOS/Linux
   traceroute example.com
   mtr -rw example.com

4. Suspect MTU? Try:

   # Windows (PowerShell as admin)
   netsh interface ipv4 show subinterfaces
   # Try lower MTU (example 1472 + 28 = 1500)
   netsh interface ipv4 set subinterface "Wi-Fi" mtu=1472 store=active

1. Confirm split vs. full‑tunnel policy with network team.
2. Check default route:

   # Windows
   route print
   
   # macOS/Linux
   netstat -rn

3. On Windows, disable “Use default gateway on remote network” if split tunnel is intended.
4. Flush & renew IP:

   ipconfig /release && ipconfig /renew

1. Confirm ipconfig/ifconfig address and check ARP:

   # Windows
   arp -a
   
   # macOS/Linux
   ip neigh

2. Release/renew DHCP; if static, coordinate to assign a unique IP.
3. Clear ARP cache (Windows): arp -d *.

1. Right‑click → “Run as administrator”.
2. Check SmartScreen / reputation prompts.
3. Use winget (if allowed):

   winget install --id Vendor.App -e --source winget

4. If GPO blocks MSI, request a Software Center / Intune deployment.
5. Logs:

   msiexec /i installer.msi /L*V C:\Temp\install.log

Install required runtimes first, then retry the setup.

• .NET Desktop Runtime (x64) matching app’s target.
• Visual C++ Redistributables (2015–2022).

1. System Settings → Privacy & Security → “Open Anyway”.
2. Or remove quarantine attribute:

   xattr -dr com.apple.quarantine /Applications/AppName.app

3. Prefer signed packages via Homebrew when possible:

   /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
   brew install --cask iterm2

1. Update repos; read the exact missing packages from output.
2. Use the distro’s package manager:

   # Debian/Ubuntu
   sudo apt update && sudo apt install <pkg>
   
   # RHEL/CentOS/Fedora
   sudo dnf install <pkg>
   
   # Generic RPM
   sudo rpm -Uvh package.rpm

1. Find the printer’s IP (label or DHCP lease list).
2. Windows: Settings → Bluetooth & devices → Printers & scanners → Add device → Add manually → Add a printer using a TCP/IP address.
3. macOS: System Settings → Printers & Scanners → Add Printer, Scanner, or Fax → IP (use IPP if supported).
4. Install the correct vendor driver or use generic PCL/PS.

1. Windows:

   services.msc  # Stop "Print Spooler"
   del /q C:\Windows\System32\spool\PRINTERS\*.*
   # Start "Print Spooler"

2. macOS (CUPS):

   cancel -a
   cupsctl --debug-logging
   lpstat -t

1. Ping the IP; if unreachable, verify VLAN, cabling, power.
2. Ensure the print server/firewall allows printing protocols (SMB, IPP, RAW 9100).
3. Confirm DNS record matches the current IP (A/AAAA).

Title: <Problem Name>
Scope: Who is this for? What systems?
Impact: What breaks / who is affected?
Prereqs: Access, permissions, tools

Steps:
1) <Action>
2) <Action>
3) Validate: <expected output>

Rollback:
- <safe undo path>

Notes:
- Links to vendor docs / tickets
- “Gotchas” / common traps

Last Updated: <YYYY‑MM‑DD>  Owner: <name>

Summary: <1‑2 sentence user‑friendly summary>
User/Asset: <user@company / PC‑12345>
Timeline:
- <HH:MM> Reported
- <HH:MM> First response
- <HH:MM> Fix applied
- <HH:MM> Verified with user

Root Cause: <when known>
Resolution: <final actionable fix>
Follow‑ups: <PR, policy, KB link>