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 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.

StageQuestionUseful comparison
AuthenticationDid the user receive desktop entitlement?Failed login versus successful desktop selection.
AssignmentWhich desktop was selected and was it ready?One affected desktop versus a known-good peer.
Display pathWhich component contacted the Agent?Actual route versus configured gateway destinations.
Session operationDoes launch work but reconnect or another feature fail?First launch versus repeat operation, with timestamps.

Read port numbers in context

The official port tables distinguish destination and direction. For example, internal Blast to an Agent uses destination 22443, while a UAG-facing Blast connection commonly uses 8443 or configured port sharing. Those numbers are not interchangeable tests against a Connection Server. Only permit flows required by the deployed protocol and route.

Test from the relevant source network and pair transport checks with protocol logs. A successful TCP connection does not validate UDP, certificate checks, or completed display negotiation. RDP succeeding does not prove Blast is repaired, and changing protocols is not an acceptable security bypass.

Separate service failure from network rejection

If the service fails to start, retain its exact event and startup error before a restart. If it starts but the connection times out, examine the expected listener, route, gateway, and effective policy. Do not translate a generic Windows service event into a specific blocked-port cause without corroboration. Collect diagnostics using the installed release's supported procedure.

Test one correction

Have the owning team change one evidenced setting in a pilot: a wrong advertised destination, a narrowly scoped firewall rule, or a confirmed component configuration problem. Record the original value and rollback trigger. Do not disable the firewall or add broad EDR exclusions merely to see whether the session launches.

Verify login, launch, reconnect, and the original business action on the selected protocol. Retest the known-good route for regression. If the same failure remains, restore the previous setting before moving to another hypothesis. Escalate with the traffic map and correlated diagnostics rather than a list of ports already opened.

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