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

Multihomed Domain Controller: DNS and Reachability Checks for LDAP/RPC Failures

On a multihomed domain controller, investigate published DNS addresses and reachability before assuming LDAP replies use the wrong NIC. Multiple interfaces are a configuration detail, not proof of the packet-level mechanism behind an intermittent failure.

Correction, September 12, 2026: The earlier article asserted a specific reply-address mechanism and vendor-confirmed cause without supporting traces. It also recommended hosts-file overrides as a general recovery step. Those conclusions have been removed. This is a documentation-based diagnostic guide.

Separate name discovery from the connection

Microsoft documents unwanted NIC registration on multihomed domain controllers. An address published in DNS may be unreachable from some clients. That is a concrete hypothesis to test, distinct from proving asymmetric routing or an unexpected source address in a capture.

Active Directory also uses DNS SRV locator records. A local hosts entry maps a hostname to an address; it is not a replacement for domain-controller discovery, site-aware selection or service records.

Evidence checklist

LayerCollectInterpret carefully
Client resolutionConfigured resolver, actual SRV/host answers, selected DC and timeAnother client's answer may differ due to cache or site.
DC interfacesAddresses, routes, DNS registration and listening configurationTwo NICs alone do not identify the fault.
Network pathReachability and approved trace for the resolved destinationPing does not prove LDAP/RPC authentication works.
ApplicationExact LDAP/RPC error, destination and retry timelineDo not infer every provisioning error is caused by LDAP.

Correct the authoritative configuration

If DNS publishes an unwanted address, have the AD/DNS owner follow the vendor procedure for that role and OS version, including the services responsible for registration. Merely deleting a record may not stop it returning. Preserve DNS/interface configuration and assess replication and dependent services before changing registration or interface settings.

If resolution is correct but the path fails, investigate routing and filtering separately. Direct-IP testing may help test transport, but name-based authentication and certificate validation can behave differently; do not treat a successful IP probe as end-to-end application validation.

Why a hosts override is not the default fix

Static pinning can mask stale DNS, outlive an address change and undermine expected failover. If an incident team explicitly authorizes a temporary override for one dependency, record its owner, expiry and removal test. Do not distribute a blanket hosts file across domain members or disable a DC interface without impact assessment.

After a correction, recheck records over their normal refresh cycle, validate from affected and known-good networks, and test the original authenticated application operation. Check dependent AD services rather than closing on one successful query. Roll back unsuccessful changes under the AD recovery plan and escalate with preserved evidence.

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