I have a VDI env where I get this error message whenever I launch the newly created VDI for the first time. But it is intermittent and will work most of the time. Appears specifically after restarting the VDIs. One click, error message, second click it works. This doesn't feel stable at all. Not sure if its related to Netscaler or what it is but I have checked everything pretty much and it all looks good. I'm running full clone persistent VDIs in vmware through Citrix Cloud MCS & just standard 2 cloud connectors and so on. Did someone have this before?

So those are winsocket drops. Do you have rendezvous setup? If not it could be something with one of the cloud connectors not having access to tunnel.

I don't have any rendezvous setup nope. Goes through NS gw. Can I somehow confirm if its one of the connectors that is the issue? except for removing one by one from the listofddc

I don't think it does for 10054, but if you go into Monitor and enter the Transaction ID, then go into the details of the connection failure and export the full CSV log, it might have add'l details there.

Are you using Gateway Service for Storefront?

Thanks a lot Balint and everyone! Thanks a lot Jon for that one as well and Jeff!. So far what I did was basically configure static IPs and now it seems stable. Now this might be a beginner mistake but I have been kind of used to run DHCP when MCS or PVS is involved. However, it seems like the reason for this issue might be DNS but still not hundred percent sure. So far I can't re-create the issue so lets hope for that. I'm running static VDIs so its fine for me to configure static IPs. This can be related to internal DC/DNS issues as well, haven't been working with this customer for that long and the env is a bit messy =)

Sure! You could do also a reservation on your dhcp server as it requires less manual intervention. If dhcp is the culprit, take a look on the lease expiration or dns scavenging time.

IMG_3880.png

oh yeah you bet I'm going to do some reservations! what a mess it can become and meanwhile I thought I did something wrong citrix wise...