Terminal Server Agent issues with CCH Engagement

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Terminal Server Agent issues with CCH Engagement

L1 Bithead

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:

RPerez481389_0-1784765718878.png

RPerez481389_1-1784765772928.png

 

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. 

0 REPLIES 0
  • 20 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!