Users launch VDAs failed: " Socket is not connected(socket error: 10057)"
Article ID: CTX464063
Updated On:
Description
After HA configuration enables in the ADC, a lot of users failed to login the VDA with the below error message:
"Unable to connect to the server. contact your system administrator with the following error: Socket is not connected(socket error: 10057)"
Eventually, VDAs can be logged on successfully if users launch desktops multiple times.
Resolution
Sync STA(Secure Ticket Authority) configuration between SF servers and ADC servers.
Problem Cause
STA configuration mismatch between SF servers and ADC servers
Additional Information
1. CDF trace on DDC servers show "Ticket not found":
2. From ADC network packet, the STA request number is different when issue happens compared with normal launch process, and the STA request number is not listed on "VPN Virtual Server STA Server Binding" on ADC server.
2. From ADC network packet, the STA request number is different when issue happens compared with normal launch process, and the STA request number is not listed on "VPN Virtual Server STA Server Binding" on ADC server.
Was this article helpful?
Yes
No
Powered by
