VMware Horizon disconnects frequently: how can you distinguish client, network, Agent, and Connection Server problems?
Correlate Client, Agent, Connection Server, and firewall timestamps, then verify the display protocol, loss and jitter, MTU, proxy path, and session timeouts.
Correlate Client, Agent, Connection Server, and firewall timestamps, then verify the display protocol, loss and jitter, MTU, proxy path, and session timeouts. For this case, first verify client logs and Horizon Agent logs, then use Connection Server logs to decide whether remediation is needed.
Define the failure boundary first
For this virtualization and VDI case, establish the failure boundary with client logs and Horizon Agent, then continue to Connection Server. 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 · client logs | Verify client logs 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 client logs. If adjustment is required, change one condition only and retain the original setting for rollback. |
| 02 · Horizon Agent logs | Verify Horizon Agent logs on the affected path using logs, counters or state information rather than relying only on the configured rule. | Check Horizon Agent logs read-only and save the result. If it differs from the baseline, correlate it with the incident time and recent changes before remediation. |
| 03 · Connection Server logs | Verify Connection Server logs on the affected path using logs, counters or state information rather than relying only on the configured rule. | Compare Connection Server logs with a known-good peer, the log timeline and the real application path; confirm whether it is causal before changing production. |
| 04 · Blast/PCoIP path | Review the current state, related logs and recent changes for Blast/PCoIP path, then align them with the incident timeline before deciding whether a change is required. | Record the current value, evidence source and timestamp for Blast/PCoIP path. If adjustment is required, change one condition only and retain the original setting for rollback. |
| 05 · packet loss, jitter and MTU | Review the current state, related logs and recent changes for packet loss, jitter and MTU, then align them with the incident timeline before deciding whether a change is required. | Check packet loss, jitter and MTU read-only and save the result. If it differs from the baseline, correlate it with the incident time and recent changes before remediation. |
| 06 · firewall session timeout | Review the current state, related logs and recent changes for firewall session timeout, then align them with the incident timeline before deciding whether a change is required. | Compare firewall session timeout with a known-good peer, the log timeline and the real application path; confirm whether it is causal before changing production. |
ping -t connection-server.corp.example
pathping connection-server.corp.exampleChange only after the evidence is clear
- Start with read-only evidence. Check client logs and Horizon Agent logs before changing configuration.
- If the first checks are normal, continue with Connection Server logs and Blast/PCoIP path, keeping evidence tied to the incident time.
- Change configuration only when the evidence explains the symptom. For packet loss, jitter and MTU, preserve the original value and define the rollback trigger before adjustment.
- Validate firewall session timeout 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 client logs.
- Recheck packet loss, jitter and MTU and firewall session timeout after the change and confirm that no new bypass, permission expansion or secondary error has appeared.
- Archive evidence from client logs through firewall session timeout, together with before/after configuration, business validation and the rollback point.
Common wrong turns
- Changing client logs and Horizon Agent at the same time, which makes the original cause impossible to prove.
- Treating a normal result for Connection Server as proof that Blast/PCoIP path and the rest of the business path are healthy.
- Leaving a temporary exception related to packet loss, jitter and MTU or firewall session timeout in production without an owner, expiry time and rollback note.
Related questions
Where should I start with “VMware Horizon disconnects frequently: how can you distinguish client, network, Agent, and Connection Server problems?”?
Start with client logs and Horizon Agent logs; they establish the first useful troubleshooting boundary without changing production state.
What should be checked after the first layer looks normal?
Continue with Connection Server logs and Blast/PCoIP path, 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 packet loss, jitter and MTU and firewall session timeout, plus the original configuration, validation result, observation notes and rollback point.