https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-issues-with-cch-engagement/m-p/1259751#M126772 <P>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:</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RPerez481389_0-1784765718878.png" style="width: 400px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/72091iC5CB7EC22D1F94B9/image-size/medium?v=v2&amp;px=400" role="button" title="RPerez481389_0-1784765718878.png" alt="RPerez481389_0-1784765718878.png" /></span></P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RPerez481389_1-1784765772928.png" style="width: 400px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/72092iDF3DABB79EC068B0/image-size/medium?v=v2&amp;px=400" role="button" title="RPerez481389_1-1784765772928.png" alt="RPerez481389_1-1784765772928.png" /></span></P> <P>&nbsp;</P> <P><SPAN>We also increased the minimum port allocation size from <STRONG>200</STRONG> to <STRONG>500</STRONG> and changed the source port allocation range to <STRONG>25000–45000</STRONG>. From our observations, CCH Engagement appears to use ports in the <STRONG>22000-23k&nbsp;</STRONG>range as well as anywhere between <STRONG>40000–60000</STRONG>, so the source port usage seems quite random.</SPAN></P> <P><SPAN>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.&nbsp;</SPAN></P> Thu, 23 Jul 2026 04:18:09 GMT R.Perez481389 2026-07-23T04:18:09Z https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-issues-with-cch-engagement/m-p/1259751#M126772 <P>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:</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RPerez481389_0-1784765718878.png" style="width: 400px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/72091iC5CB7EC22D1F94B9/image-size/medium?v=v2&amp;px=400" role="button" title="RPerez481389_0-1784765718878.png" alt="RPerez481389_0-1784765718878.png" /></span></P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="RPerez481389_1-1784765772928.png" style="width: 400px;"><img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/72092iDF3DABB79EC068B0/image-size/medium?v=v2&amp;px=400" role="button" title="RPerez481389_1-1784765772928.png" alt="RPerez481389_1-1784765772928.png" /></span></P> <P>&nbsp;</P> <P><SPAN>We also increased the minimum port allocation size from <STRONG>200</STRONG> to <STRONG>500</STRONG> and changed the source port allocation range to <STRONG>25000–45000</STRONG>. From our observations, CCH Engagement appears to use ports in the <STRONG>22000-23k&nbsp;</STRONG>range as well as anywhere between <STRONG>40000–60000</STRONG>, so the source port usage seems quite random.</SPAN></P> <P><SPAN>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.&nbsp;</SPAN></P> Thu, 23 Jul 2026 04:18:09 GMT https://live.paloaltonetworks.com/t5/general-topics/terminal-server-agent-issues-with-cch-engagement/m-p/1259751#M126772 R.Perez481389 2026-07-23T04:18:09Z