topic Re: Terminal Server Agent issues with CCH Engagement in General Topics

Terminal Server Agent issues with CCH Engagement

R.Perez481389 — Thu, 23 Jul 2026 04:18:09 GMT

Hi everyone, we recently deployed Terminal Server Agents on our AVD Hosts. We're having issues with about 3-5 users that use CCH Engagement. Users would get the below errors when trying to open binders:

We also increased the minimum port allocation size from 200 to 500 and changed the source port allocation range to 25000–45000. From our observations, CCH Engagement appears to use ports in the 22000-23k range as well as anywhere between 40000–60000, so the source port usage seems quite random.

We also tried the EnableTWS, TwsTimeout, and FreePortBlockDelay fixes which initially appeared to resolve the issue as the tickets stopped coming in during yesterday. However, one user reported last night that they are still experiencing the same problem. For context, we have approximately 8 users per AVD host.

Re: Terminal Server Agent issues with CCH Engagement

Brandon_Wertz — Thu, 23 Jul 2026 14:45:22 GMT

We deployed TS agents to AVD hosts and ran into a similar conflict. This KB article helped us get past our issues:

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000HCccCAG

Specifically this section:

Re: Terminal Server Agent issues with CCH Engagement

R.Perez481389 — Fri, 24 Jul 2026 02:37:15 GMT

Hi Brandon, we currently have that set to 1. Should we set it to 2 instead? Also we haven't gotten a ticket about the issue for 2 days now( Knock on wood.) but will try setting it to 2 later if we get more tickets about it.