- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the info. Your post suggests that we cannot configure around this problem from the VMware View environment itself. These are disconnection error messages and need to be addressed on the infrastructure level between the Client and the CS.
> so you're going to want to look at an affected TCP connection itself from your router logs and see if there's TCP retransmits, packet loss etc.
I was afraid it was going to come to this. Since our impacted end users are external vendors access to their personal network equipment and physical machines is going to be difficult. Ideally when packet sniffing you want to have both client and server logs to compare and isolate where the problems are occurring. Logging from the Security Server [SS?] in our situation isn't very easy to do since its a Cisco appliance and doesn't have persistent logging enabled at the moment. We might have to explore more traditional packet tracing such as Wireshark to collect more info. Still, since I can reproduce these errors with my own connection testing we might be able to rig up something and review before coordinating logging efforts on their side of the equation.