Wyse P20 and View 4.6 PCoIP Secure Gateway

[eeg3]

When we enable "Use PCoIP Secure Gateway for PCoIP connections to desktop" on our connection server, everything works fine for normal desktops both internally and externally; however, when this is enabled it seems to break authentication for our Wyse P20 zero clients. Once that box is checked, the login hangs at "Authenticating" then ultimately bombs at "View Connection Server Communicator Error." I don't even get to the point where I can select a desktop or even pick RDP or PCoIP. Unchecking the "Use PCoIP Secure Gateway for PCoIP connections to desktop" immediately fixes the issue and the P20 can again log in.

The firmware for the device has been updated to 3.3.0. I've opened a case with Wyse which has been sent to Tier 2 support, but they have not gotten back to me yet.

Has anyone else seen this issue before?

[Linjo]

Hi EEG.

This might be the AES/Salsa issue, PCoIP gateway is only supported with AES encryption and I suspect that you have disabled that on you P20.

Turn off Salsa, only allow AES and try again.

// Linjo

[eeg3]

Well, now it hangs at authentication for a long time and then eventually lets me in.

I've turned off salsa and only enabled AES. Is there something that is timing out before it uses AES?

Wyse still hasn't gotten back to me.

[Linjo]

How long?

[eeg3]

It would take about 55 seconds, and it was intermittent. It seemed like it only worked if I logged in and let it sit at authenticating then started tinkering in the P20 web interface. Now I can't get it to do it at all.

I can see in the P20 Diagnostic Event Log that AES is enabled and Salsa is disabled, but seems any combination of settings I try won't work.

IN FLASH:              enable_aes_128_gcm = enabled
IN FLASH:      enable_salsa20_256_round12 = disabled

[Linjo]

Hmm, that is interesting.

I would start with reseting the P20 to factory defaults. (If you are like me you might have changed MTU settings etc that could cause issues.)

Any loadbalancing configured? If there is try to disable one side so you are sure the traffic goes all the same way.

Also doublecheck that you have proper nameresolution.

Anything in the logs from the Security Server? (You might need to turn on debug to get the all information needed.)

I would also put in a ticket with Teradici-support, don't think Wyse actually can do anything about this.

// Linjo

[eeg3]

I tried resetting the defaults... no luck. I think I have tried every configuration combination possible, unfortunately. Thanks for the tip on opening a request with Teradici, I've done that now. Now just to wait for someone to get back to me.

It's weird it works internally, externally, and even with the iPad client, but not with the P20.

[eeg3]

I've managed to "fix" this by installing a Windows 2008 Replica server. It seems the P20 isn't compatible with Windows 2003 as the Connection Server when trying to use the PCoIP gateway, even though this is a supported combination in the View 4.6 Upgrade Guide.

[ludchrs]

@chaz112182 shared a link with me he found that covers some of the 4.5 -> 4.6 tips to take note of in the update process that covers what @eeg3 discovered (more or less).  I didnt get to it until this morning but hopefully it will help someone going forward in addition to whats already been found out.

http://www.clearpathsg.com/blogs/2011/03/10/tips-when-upgrading-vmware-view-45-46

Cheers

[eeg3]

I still believe it's a bug (not on VMware's part), and I'm keeping my tickets with Wyse and Teradici open. If I hear anything, I'll update the thread.

Thanks for everyone's help.

[Linjo]

Wow, thats very strange.

So the P20 have problem connecting when you have a CS with w2k3 and a SS with w2k8r2, but with both w2k8r2 it works fine?

If that is the case could you please send me the number of the tickets and I try to look into it a bit closer?

Thanks

// Linjo

[chrissuddekor]

I am having the same exact problem.  I had a win2k3 CS and a 2008 r2 SS.  Windows view client works perfect inside and outside.  P20 (Firmware 3.3.0) doesn't work on the inside or outside with the "Use PCoIP secure gateway" option checked.  Today I installed a 2008 R2 replica CS, I was able to get past authentication problem, but now when i connect to the pool with the P20 I get a "session timed out" almost instantly.  Again windows view client works without issue.

thanks

[eeg3]

Linjo, I messaged you the ticket IDs. Thanks!

[DaIceMan]

We were having the same issue. By removing the "Use PCoIP Secure Gateway for PCoIP connections to desktop" check, the problem did not go away.

However, a restart of the View Connection Server fixed this. We have a Leadtek VP200 (hardwarewise identical to the P20 and others, they are all OEM) with firmware 3.3.0 (4 Feb 2011).

Evidently, removing the checkbox does not update some setting in the CS or there must be some bug. For the moment, we'll keep it like this. We'll try again with a new 2008 R2 SS in due time.