Proxmox Backup to NAS: NFS vs SMB Setup and Restore Checklist

Preparation date: September 17, 2026. Scope: This is a documentation-based implementation and verification guide, not a claim about a completed customer incident. It covers ordinary Proxmox VE VZDump backups written to NAS storage. A Proxmox Backup Server datastore is a different architecture and is called out separately. The short answer is: choose NFS when Proxmox is the main consumer and your NAS can restrict the export to the Proxmox node addresses. Choose SMB/CIFS when the same share must also fit a Windows-oriented operating model or your NAS administration is already built around named users and SMB permissions. The protocol choice matters, but the restore test matters more. A green backup task proves that an archive was written; it does not prove that you can recover a VM on replacement storage. Proxmox backup to NAS verification flow A Proxmox node writes a VZDump backup over NFS or SMB to a NAS, then a separate restore test validates recovery. ...
Post a Comment

Horizon Connectivity: Auditing Effective Windows Firewall Policy

An allowed application can still be blocked by the effective Windows Firewall configuration. This focused guide audits policy before a Horizon firewall change. It is not evidence that the firewall causes every “Agent Unreachable” event.

Correction, September 12, 2026: The previous version implied that unchecking one option or rebooting would usually resolve the issue. The current workflow requires a matching policy/traffic finding and authorization from the security-policy owner.

Distinguish default blocking from blocking all inbound connections

Microsoft describes the “Block all incoming connections” option as ignoring the allowed-app list. This is different from ordinary default inbound blocking with permitted exceptions. Do not weaken an intentional security baseline simply because an application has a connectivity problem.

Collect the effective state

The following read-only PowerShell query lists profile settings. Run it in the approved administrative context; determine which profile applies to the affected interface rather than treating all returned profiles as active:

Get-NetFirewallProfile -PolicyStore ActiveStore |
  Select-Object Name, Enabled, DefaultInboundAction, AllowInboundRules, AllowLocalFirewallRules

See Microsoft's Get-NetFirewallProfile reference. Also record the matching rule's enabled state, direction, program/service, transport, addresses, and policy origin. Domain policy can prevent a locally created exception from having the effect you expect.

FindingInterpretationAction
Rule exists but is scoped to another profile/addressExistence is not evidence of a match.Compare the actual flow and effective scope.
Inbound exceptions are ignoredA profile-level restriction may override the intended exception.Ask the security owner whether a scoped baseline adjustment is permitted.
Settings revert after policy refreshA central policy may own the setting.Correct the authoritative policy, not a recurring local workaround.
No matching deny or policy conflictThe firewall hypothesis is not established.Return to Agent and connection-stage evidence.

Validate a specific flow

Match source component, destination component, transport, port, and timestamp with the Horizon network design. Log collection settings affect what evidence is available; the absence of a log entry is not proof of an allow. Keep captures and internal addressing out of public comments.

Change, verify, restore

With policy-owner approval, test only the necessary rule or profile correction on one desktop. Preserve the original policy and ensure the management path remains available. Keep the firewall enabled. Do not add broad antivirus/EDR exclusions as a substitute for diagnosis.

Repeat the original failure, fresh login, and reconnect. Confirm effective policy again after its normal refresh and ensure unrelated inbound access has not broadened. Restore the prior approved configuration if the correction fails or creates an exposure. Microsoft's firewall rule configuration guidance is the implementation reference, not a blanket exemption for Horizon traffic.

Related troubleshooting guides

Comments

Post a Comment

Popular posts from this blog

Horizon vdpConnect_Failure: Connection-Stage Triage Before Reinstalling

vdpConnect_Failure is a starting symptom, not a root-cause diagnosis. Before reinstalling Horizon Agent or opening firewall ports, establish whether the failure occurs during authentication, desktop launch, or an established session. This documentation-based triage guide does not report a reproduced incident or a universal fix. Corrected September 12, 2026: The earlier guide suggested restarting the Windows RPC service and treated a local netstat listing as a test for blocked ports. Those instructions have been removed. A socket listing does not demonstrate end-to-end reachability. Classify the failure before making changes Observation First evidence to collect Avoid assuming Authentication never completes Exact login error, identity provider or broker event, timestamp That the display protocol is the failing component. Desktop selection succeeds, launch fails Assigned desktop, chosen protocol, Client/Agent and gateway logs That a successful HTTPS login proves the session path ...
Read more

Horizon Agent Unreachable: Registration and Desktop-Health Triage

Start an “Agent Unreachable” investigation by separating desktop health, Agent registration, and session traffic. Do not begin with a pool rebuild. This documentation-based triage guide helps decide which team should act and what evidence to preserve. Correction, September 12, 2026: The earlier guide mixed display ports with Agent communication, tested Blast against the Connection Server, and offered generic service restarts and image rebuilds. Those instructions have been replaced with path-specific investigation. First-response decision table Check Evidence Investigation owner Is the guest responsive? Approved console access, OS health, resource and disk observations Desktop/virtualization team if the OS is unavailable. Is this one desktop or a whole image family? Affected pool, image revision, Agent version, start time Image owner if failures align with a deployment. Does registration fail? Agent and Connection Server events for the same desktop and time Horizon team, then netw...
Read more

Horizon Protocol Error: Trace the Display-Session Handoff

A desktop can authenticate successfully and still fail to establish its display session. This guide investigates that handoff. Use it after identifying the actual console/client error, not as a claim that every “Protocol Error” means a firewall failure. Correction, September 12, 2026: The previous version combined a general checklist with an unverified incident narrative, conflated gateway and desktop port directions, and recommended blanket endpoint-security exclusions. Those instructions have been removed. This is a documentation-based diagnostic plan. Draw the attempted connection Record the selected protocol, assigned desktop, Client and Agent versions, gateway route, and attempt time. Distinguish a direct internal connection from an external UAG connection or a Connection Server tunnel. Use Omnissa's connection guide to identify where the failed handoff occurs. Stage Question Useful comparison Authentication Did the user receive desktop entitlement? Failed login versus ...
Read more