Vmware connection issue after install of NCPA 3.1.1

[HCR3333]

We encountered vdi issues installing on our VMware servers. We could not access VDI from these servers until 3.1.1 was uninstalled (back to 3.1.0. Has anyone encountered anything similar?
I will edit and add error messages as soon as I get the exact details.
Details:
about 20 minutes after installation started seeing this in the VMWare admin console:

When I logged in to the console of one of the dead desktops, I was able to test dns, ping, and telnet to the VCS servers on port 4001 and 4002 as expected, but in the logs I was seeing that the View Agents were not actually fully connecting to JMS on VCS server 1, and then would connect to VCS server 2 “successfully” but VCS server 2 was never aware of this connection working. Something was awry:

Then when the vms needed to be rebuilt after someone logged off produced the error
Broker_provisioning_error_vm_customization_networking
Provisioning error occurred for Machine VDI-Admin-xx: Customization error due to no network communication between the view agent and Connection server.

Everything worked fine as is unless the person logged off. Then it couldn't create the new virtuals as it was trying to communicate but could not. The only thing we did was uninstall 3.1.1 client and everything was back to normal after that and it could communicate again. Just wondering how 3.1.0 client works fine but 3.1.1 won't work with our VCS servers?

[ne-bbahn]

I can't see anything among the changes to NCPA that should be making a difference here, but NCPA 3.1.1 does update the Python and OpenSSL version, which shouldn't affect your VCS server connections, but it is possible that it's related. Have you tried re-installing NCPA 3.1.1 to ensure that NCPA 3.1.1 is indeed the issue?

[HCR3333]

Yes I have tried reinstalling after fixing the issue and still had the same problem. Its a weird one for sure.