grekings.blogg.se

I will contact Terradici and have a look at the documentation available on the techsupport desk. Am I supposed to see any traffic on port 4172 when attempting to connect to the desktop?ĭon't know if anyone else has experienced this issue or not.

I ran a tcpdump on each of the LB's in & out interfaces and all I can see is HTTPS traffic. Example: Compatibility Notes for VMware Horizon 6 version 6.1 Other interoperabilities can be found when viewing VMwares matrix, pending your choices. There will be a link under the Compatibility Notes section. "the connection to the remote computer timed out". See the VMware Release Notes for the version of Horizon pertinent to your environment. The driver comes as a component within the PCoIP Component Installer. This is intended to provide analog recording and dictation support for virtual desktops. I get a frame but no desktop inside ) and then get the error message: The Teradici's virtual audio driver provides bi-directional analog audio support for virtual desktops using PCoIP Software such as VMware View. I created a separate virtual server and server pool on my LB for 4172 (UDP and TCP) and I can authenticate and connect the View client to the CS server, When I click the 'connect' button to connect to my actual desktop, the desktop frame opens but the content is all black (i.e. Their remote desktop software, Teradici CAS, powers the most secure remote solutions with unparalleled performance for even. PCoIP however has been a bit hit and miss so far. Teradici is the creator of the PCoIP remote display protocol, which delivers desktops and workstations from the data center or public cloud to end users with the highest levels of security, responsiveness, and fidelity. RDP seems to work perfectly as I can connect to a linked clone desktop remotely (WAN access), check it out and back in etc. I will also ultimately have a pair of everything (as oppose to 1 of each for now) to ensure resilience.Īnyway, at the moment I have a public address NAT'ed to a LB front end VIP which is then NAT'ed to a backend VIP that my CS & SS can talk to in their private space. My goal is to have a mixed platform for local (LAN) and remote workers (on VPN/WAN) hence the deployment of the SS. PCoIP offers great desktop display experience for LAN users. I have tested the setup for local users (with and without local mode) prior to deploying the SS & LB and everything works a treat. I'm also having some difficulties making PCoIP work through my Security Server/Load Balancers/Firewall.Ĭlient 4.6 (with local mode) on remote client machine. I might need to pick your support guys' brain a little too :smileygrin: