VMware Horizon works in the office but lags or disconnects on the factory floor: how to troubleshoot it
When the same desktop behaves differently by location, compare VLANs, uplinks, port errors, loss and jitter, MTU, QoS, firewall policy, and the display-protocol path.
When the same desktop behaves differently by location, compare VLANs, uplinks, port errors, loss and jitter, MTU, QoS, firewall policy, and the display-protocol path. For this case, first verify office-versus-shop-floor path comparison and switch-port errors and packet loss, then use VLAN, gateway and firewall path to decide whether remediation is needed.
Define the failure boundary first
For this virtualization and VDI case, establish the failure boundary with office-versus-shop-floor path comparison and switch-port errors and packet loss, then continue to VLAN, gateway and firewall path. Capture the current state, incident time and one known-good comparison before changing production configuration.
Work through the dependency chain
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · office-versus-shop-floor path comparison | Verify office-versus-shop-floor path comparison on the affected path using logs, counters or state information rather than relying only on the configured rule. | Record the current value, evidence source and timestamp for office-versus-shop-floor path comparison. If adjustment is required, change one condition only and retain the original setting for rollback. |
| 02 · switch-port errors and packet loss | Verify switch-port errors and packet loss on the affected path using logs, counters or state information rather than relying only on the configured rule. | Check switch-port errors and packet loss read-only and save the result. If it differs from the baseline, correlate it with the incident time and recent changes before remediation. |
| 03 · VLAN, gateway and firewall path | Verify VLAN, gateway and firewall path on the affected path using logs, counters or state information rather than relying only on the configured rule. | Compare VLAN, gateway and firewall path with a known-good peer, the log timeline and the real application path; confirm whether it is causal before changing production. |
| 04 · MTU and QoS | Review the current state, related logs and recent changes for MTU and QoS, then align them with the incident timeline before deciding whether a change is required. | Record the current value, evidence source and timestamp for MTU and QoS. If adjustment is required, change one condition only and retain the original setting for rollback. |
| 05 · wireless roaming and signal quality | Review the current state, related logs and recent changes for wireless roaming and signal quality, then align them with the incident timeline before deciding whether a change is required. | Check wireless roaming and signal quality read-only and save the result. If it differs from the baseline, correlate it with the incident time and recent changes before remediation. |
| 06 · Blast/PCoIP protocol statistics | Review the current state, related logs and recent changes for Blast/PCoIP protocol statistics, then align them with the incident timeline before deciding whether a change is required. | Compare Blast/PCoIP protocol statistics with a known-good peer, the log timeline and the real application path; confirm whether it is causal before changing production. |
Change only after the evidence is clear
- Start with read-only evidence. Check office-versus-shop-floor path comparison and switch-port errors and packet loss before changing configuration.
- If the first checks are normal, continue with VLAN, gateway and firewall path and MTU and QoS, keeping evidence tied to the incident time.
- Change configuration only when the evidence explains the symptom. For wireless roaming and signal quality, preserve the original value and define the rollback trigger before adjustment.
- Validate Blast/PCoIP protocol statistics in a controlled scope before expanding to production users or traffic.
Validation and rollback
- Validate the complete user or application workflow; do not stop at the single status of office-versus-shop-floor path comparison.
- Recheck wireless roaming and signal quality and Blast/PCoIP protocol statistics after the change and confirm that no new bypass, permission expansion or secondary error has appeared.
- Archive evidence from office-versus-shop-floor path comparison through Blast/PCoIP protocol statistics, together with before/after configuration, business validation and the rollback point.
Common wrong turns
- Changing office-versus-shop-floor path comparison and switch-port errors and packet loss at the same time, which makes the original cause impossible to prove.
- Treating a normal result for VLAN, gateway and firewall path as proof that MTU QoS and the rest of the business path are healthy.
- Leaving a temporary exception related to wireless roaming and signal quality or Blast/PCoIP in production without an owner, expiry time and rollback note.
Related questions
Where should I start with “VMware Horizon works in the office but lags or disconnects on the factory floor: how to troubleshoot it”?
Start with office-versus-shop-floor path comparison and switch-port errors and packet loss; they establish the first useful troubleshooting boundary without changing production state.
What should be checked after the first layer looks normal?
Continue with VLAN, gateway and firewall path and MTU and QoS, then correlate the result with the incident time and the actual user or application path.
What should be retained after the change?
Keep evidence for wireless roaming and signal quality and Blast/PCoIP protocol statistics, plus the original configuration, validation result, observation notes and rollback point.