Hi
A couple of weeks ago we upgraded from 5.01 to 5.1 (and went through the delights of getting all these certificates to play nicely). However, since then, we are having terrible PCoIP performance through our 5.1 security server.
Firstly, we've been running View for years and since PCoIP was first introduced we have never had any issue with it. It has always 'just worked' over the WAN. Now, after this latest upgrade we find that although general 'static' usage is generally OK, if I wave a window around the screen the amount of traffic this creates causes the entire VM to hang up for about 20 seconds or so, then it 'catches up'.
General network performance between remote clients is good - no packet loss connecting to our firewall external interface and RDP sessions work well. It just affects PCoIP - I have tested Windows based, 5.2 client but this affects everyone. Analysing the pcoip_server logs using the parser/log viewer shows that latency is always well within acceptable limits, as is throughput - there is lots of bandwidth available, and no major delay. However, we are seeing massive PCoIP packet loss when we do our 'window waggle' - up to 80% dropped.
Our security server is in a DMZ (obviously) but to eliminate that I have built a security server on the LAN and paired it with an internal broker. Same performance when connecting from the outside world. So, DMZ networking is out of the question. LAN switching is fine as looking at the same pcoip_server logs from desktops in use locally on the LAN show no loss. So, we're looking at firewall or external networking/routing. However, none of this has changed since the upgrade...why would this suddenly be an issue? Has the protocol changed to such an extent as part of 5.1 that our firewall now handles it differently? We do have remote sites that come in over IPSEC VPN into the same firewall and these also seem OK - it just seems to affect remote connections over SSL.
I have a call logged with VMware who have passed it on to Teradici, but from what I've seen so far I think I'm going to be told 'its your network'. Why then did it work without issue before?
If anyone can shed some light on this I would be very, very grateful. Its really getting on my nerves!