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 PCoIP Fails on Home Wi-Fi: Compare Paths Before Blaming NAT

A Horizon session working on a hotspot but failing at home isolates a path-dependent symptom, not a proven NAT defect. Keep the endpoint, account, pool, and protocol constant and compare the two paths before blaming the router or excluding the managed infrastructure.

Correction, September 12, 2026: The earlier article generalized ISP and hotspot behavior, attributed failures to symmetric NAT without packet evidence, and described Blast as universally using port 443. Those conclusions have been removed. This is a documentation-based investigation guide; no measured ISP comparison is supplied.

Make the comparison meaningful

ComparisonWhat it helps isolateWhat it does not prove
Same laptop, home Wi-Fi versus approved hotspotA change in the access path or location-dependent policyWhich router, carrier, gateway or rule causes the failure.
Home wired versus home Wi-FiLocal wireless conditions, where wiring is availableThat the ISP or gateway is healthy.
Same route, another supported endpointEndpoint configuration differencesA firmware defect without a controlled version comparison.

Record timestamps, DNS answers, actual gateway destination, Client version, protocol and endpoint VPN/security state. Do not disable managed security software to make the comparison. Repeated tests may reach different gateway or broker nodes; capture that distinction where logs permit.

Separate login from desktop traffic

Use Omnissa's connection-stage guide and port tables to map the actual deployment. HTTPS authentication can succeed while display traffic fails. PCoIP and Blast use different flows; Blast's ports depend on direct/gateway routing and configuration, so switching protocols is neither a universal NAT fix nor proof of the cause.

Evidence before changing the router

Compare Client and gateway events for the failed attempt. Look for the destination reached, negotiation failure, timeout, and any observed packet loss or filtering. NAT behavior, routing, name resolution, wireless congestion, security policy and gateway selection remain hypotheses until corroborated. A single speed test cannot validate this application path.

Do not request router DMZ exposure or inbound port forwarding as a generic fix for an outbound remote-access session. If router or ISP behavior is implicated, provide sanitized timestamps and flow details to the network owner or provider. Do not publish home addresses, subscriber information or raw captures.

Temporary access and closure

An approved hotspot can provide temporary access if it passes the real workload test, but consider data charges, signal quality and organizational policy. Label it a workaround, not proof that every hotspot is more permissive or reliable. Validate login, reconnect and the previously failing operation over an agreed observation period. Restore any pilot configuration if it causes regressions and retain the unresolved root-cause status until evidence supports closure.

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