Triage the impact
Start with the user, the symptom, what changed, and the scope of the failure.
Endpoint support at work · Infrastructure at home
I troubleshoot systems at work. I build them at home.
I support Windows endpoints by tracing connectivity, service, certificate, proxy, firewall, and remote-access issues to their source. Outside of work, I run a Proxmox homelab where I build segmented networks, secure VPN access, Windows Server services, and the automation that ties it together.
- Windows
- Endpoint support
- DNS → TLS
- Connection-path checks
- 3 Networks
- Home lab design
STARTIssue reported
TRIAGE
METHODIsolate the layer
VERIFY
NETWORK
DNS + TCP
Resolution · Route · Port
ENDPOINT
Windows
Services · Proxy · Firewall
TRUST
TLS + Access
Certificates · Remote support
WINDOWS SUPPORT
◆REMOTE TROUBLESHOOTING
◆DNS + TCP/IP
◆POWERSHELL
◆PROXMOX + PFSENSE
◆WIREGUARD
01 / What I do at work
I help people get unstuck and find the technical reason why.
My day-to-day work is endpoint troubleshooting: understanding what a user is seeing, reproducing the issue, checking the full connection path, and turning the result into either a verified fix or a clean technical handoff.
What that looks like
- Support Windows endpoints through guided and remote troubleshooting.
- Check services, processes, event information, system time, and local configuration.
- Trace DNS resolution, TCP reachability, proxy settings, firewall behavior, and routes.
- Review certificate and TLS conditions when trust or encrypted connections fail.
What I deliver
- A calm, understandable path for the person dealing with the issue.
- Evidence that separates endpoint, network, access, and service-side failures.
- Clear notes, tests performed, results, and reproducible next steps.
- Focused escalation when the fix depends on another team or environment owner.
Isolate the layer
Test from name resolution through the endpoint, network path, trust, and service.
Close the loop
Verify the result, explain it plainly, and leave useful context for what comes next.
02 / Professional toolkit
The layers I work through every day.
A support-focused toolkit backed by deeper infrastructure practice at home.
01
Endpoint Support
Working directly with users and Windows systems to reproduce issues and restore normal operation.
02
Network-Path Diagnostics
Following a failed connection across the dependencies between an endpoint and a service.
03
Access & Trust
Checking the controls and trust relationships that sit between a user and a protected service.
04
Documentation & Automation
Making troubleshooting repeatable and making the outcome useful to the next person.
03 / Home lab projects
Where I turn theory into operating experience.
Personal infrastructure designed, built, broken, tested, and documented at home.
01FEATURED BUILD
Segmented Proxmox Homelab
Designed a virtualization environment around an i9 Proxmox host, with pfSense controlling traffic between the home network, management services, lab systems, and a dedicated jumpbox network.
CHALLENGE
Keep infrastructure manageable without exposing the rest of the home network.
APPROACH
Path-based Proxmox permissions, pfSense aliases, ordered allow rules, and default-deny segmentation.
RESULT
A cleaner administrative boundary with tightly scoped access to Proxmox and the upstream gateway.
Proxmox VEpfSenseVLANsRBAC
02REMOTE ACCESS
WireGuard + Privileged Jumpbox
Built a secure remote administration path that terminates WireGuard on pfSense and routes authorized traffic to a dedicated Windows jumpbox—without exposing RDP directly to the internet.
FLOW
Remote client → WireGuard → pfSense → Windows jumpbox → approved management targets.
CONTROL
Restricted VPN rules, RDP/NLA hardening, host firewall controls, and management allowlists.
VALIDATION
Verified tunnel handshakes, routed reachability, and TCP 3389 connectivity step by step.
WireGuardpfSenseRDPWindows Firewall
03IDENTITY SERVICES
Active Directory & DNS Lab
Deployed a Windows domain lab and worked through the dependencies behind reliable domain joins: static addressing, AD-integrated DNS, secure dynamic updates, SRV registration, account separation, and Group Policy.
DIAGNOSIS
Used DCDIAG, NSLookup, NLTest, and Netlogon to isolate missing AD DNS records.
DESIGN
Separated everyday and administrative identities and kept the built-in account for recovery.
OPERATIONS
Planned policies for Defender, firewall, updates, RDP, PowerShell logging, and auditing.
AD DSDNSGroup PolicyWindows Server
04AUTOMATION
Windows Connectivity Diagnostic Toolkit
Built a reusable PowerShell 5.1 tool outside of work to turn common Windows connectivity checks into one repeatable workflow with readable and structured reports.
COVERAGE
DNS, TCP, proxy, firewall profiles, services, system time, certificates, adapters, routes, and internet access.
OUTPUT
Color-coded PASS/WARN/FAIL results with TXT and JSON reports for review or automation.
DESIGN
Safe error handling, configurable endpoints, explicit timeouts, and meaningful process exit codes.
PowerShell 5.1JSONTLSTCP/IP
05VALIDATION
External Attack-Surface Review
Tested the public-facing edge from outside the network and interpreted filtered TCP results separately from the intentionally forwarded WireGuard UDP service.
METHOD
Compared TCP scanning with focused UDP checks to avoid drawing the wrong conclusion from default scans.
FINDING
Common TCP ports were silently filtered and RDP was not directly exposed.
OUTCOME
Confirmed a deliberately narrow edge: authenticated VPN access instead of public management services.
NmapUDPTCPEdge security
06TROUBLESHOOTING
Wake-on-LAN Packet Automation
Wrote and tested a PowerShell magic-packet sender for a Proxmox host, then used tcpdump and ethtool to separate packet-generation issues from NIC and BIOS power-state behavior.
PACKET
Generated the standard 102-byte payload and sent it over UDP to the subnet broadcast address.
PROOF
Captured traffic on the physical NIC and Linux bridge to validate the complete network path.
ISOLATION
Narrowed the remaining fault domain to shutdown-state NIC power and firmware behavior.
PowerShellUDPtcpdumpethtool
04 / The lab
A safe place to break things carefully.
The environment is designed as a small enterprise playground: virtualization at the core, policy at the edge, identity and services inside, and one controlled path for remote administration.
- 01Segmented by role
Home, management, jumpbox, services, and future security workloads are treated as separate trust zones.
- 02Managed through policy
pfSense rules and Proxmox RBAC define who can reach which services and what they can do.
- 03Built for expansion
Active Directory, monitoring, backup, automation, and container orchestration fit into a deliberate roadmap.
WANInternet
→
EDGERouter
→
POLICYpfSense
Management
Proxmox GUI · pfSense admin · SSH
RESTRICTEDServices
DC01 · DNS · Windows · Ubuntu
INTERNALRemote access
WireGuard · JUMP01 · RDP
ENCRYPTED ROUTED FILTERED LOGGED
05 / Next layer
Always building forward.
Planned work that extends the same systems, networking, and security foundation.
Proxmox Backup Server
Scheduled retention, verification, and a documented restore test.
Centralized monitoring
Infrastructure metrics and security events with Grafana, Prometheus, and Wazuh.
Kubernetes on Proxmox
A three-node virtual cluster for services, ingress, CNI, and NetworkPolicy practice.
06 / Contact
Let's build something reliable.
I'm interested in opportunities where thoughtful troubleshooting, strong fundamentals, and a security-minded approach make infrastructure better.