Slow external view connection

[rli123]

Hi I've managed to get vmware view working externally (without the use of an security server) using RDP protocol to connect. But the connection lags a lot, anyone know why?

Thanks

Robert

[mittim12]

Welcome to the forums.  There could be a lot of difference reasons why your not getting the performance you need.    How robust is the external connection the person is using?   Is there an opportunity to use PCOIP instead of RDP?   

[eeg3]

RDP is going to have a lower user experience than PCoIP, as PCoIP can adapt to bandwidth needs among other improvements. If possible, I would recommend using the PCoIP protocol.

It's also best to use a security server if possible, as you're opening up a larger footprint for intrusions by exposing the connection server itself to the itnernet.

[rli123]

Thanks for the quick response.

I've tested the connection at home and I have a decent enough broadband connection. I've also tested during out of hours over the weekend when activity on the network is minimal.

I tried to get it to work with PCOIP but can only get to a blank screen then disconnects.

Is it possible to get PCOIP to work without security server? I understand security server is a must but wanted to get it working without in a test environment.

Thanks

[eeg3]

PCoIP will work from the internet without a security server (I actually expose my home lab this way due to resources, but wouldn't recommend it in an enterprise envrionment). If it's going blank and then disconnects, it is likely a firewall rule. Are port 4172 (TCP & UDP) open to your connection server?

[rli123]

Yep ports 4172 are open for TCP and UDP.

Do I need a dedicated connection server just for external connections?

[eeg3]

Not technically. Did you enable 'Use PCoIP Secure Gateway for PCoIP Connections to desktop' under the connection server properties, and also put in your external IP in the 'External URL' field (e.g. 24.24.24.24:4172)?

[rli123]

Ok, Ive read to use internal IP address of connection server for 'External URL' field.

I've made the changes you suggested, now works for external PCoIP connections but internal users can't use that server to connect.

[markbenson · Accepted solution]

What happens?

If external users can use PCoIP when using that Connection Server but internal users just get a black screen, it will be because internal users cannot connect PCoIP using the "PCoIP External URL" you specified.

One option is just to install a replica Connection Server. That way you can have one for external users who will gateway their PCoIP connections through this Connection Server, then for the new one, configure it for direct PCoIP. This is the recommended approach.

See http://communities.vmware.com/docs/DOC-14974 for details on how to support internal and external PCoIP users with the same View environment.

Mark

[eeg3]

Is the address you put into the External URL reachable by the clients? You probably don't want your internal clients necessarily going that route, so you'd still want another server under ideal circumstances.

[markbenson]

eeg3: couldn't have put it better myself 🙂

[eeg3]

You beat me by ~30 seconds. :smileylaugh:

Your advice was awesome as always.

[rli123]

We do have 2 connection servers, so I'll just need to set one up for external and the other for internal.

Much appreciated for the feedback

Thanks