Windows 8 fails to to log into connection server

[mhashemi]

We're setting up View 5.2 and have two desktops for testing. One desktop is running Windows 7 SP1 and the other, Windows 8. The desktops are on different networks.

When we try connect to the Connection server from the Windows 7 desktop (server.domain.com), authentication happens without issue and we can see the pools. When we do the same thing from Windows 8, we get the following message:

The View Connection Server authentication failed. Initialization failed while connecting to server 'https://server.comain.com:443'

We tried rebooting the machine, and have verified that we can telnet to the connection server, over port 443. How do we resolve this issue?

Thanks.

[abhilashhb]

try un checking the 'Use secure tunnel connection to desktop' and try?

[mhashemi]

In the View Client?

[mhashemi]

Yeah, I tried that, and it still fails to authenticate. The View log shows:

2013-10-11T18:26:56.658+01:00 ERROR (2264-059C) <MessageFrameWorkDispatch> [wswc_ui] wswc_ui_operation::GetTunnelMsg: Unable to start the tunnel: "Tunnel failed to connect". Error message displayed was "The View Connection Server authentication failed. Initialization failed while connecting to server 'https://pool.domain.tld:443'.". Proxy used to connect was '(null)', connection server was 'https://pool.domain.tld:443'.

I had the user try from a different box (Windows 7), and it still failed. I tried changing the external URL from pool.domain.tld:443 to serverName.domain.internalTLD:443, but no luck. I also verified that the user is entitled to the pool and that no software firewalls are enabled. Finally, my user (entitled through the same AD group) can connect, just fine.

[Calyps0Craig]

Hi, did you get a resolution to this? I am seeing the same problem

Cheers

Craig

[Shan_Virtual]

Hi mhashemi , Calyps0Criag,

  Did you get any solution to  the above issue ?

Regards

Shan

[Calyps0Craig]

Hi Shan,

Our problem was the load balancer had the wrong intermediate and root certificates installed. Once we had the correct certs, all clients were able to connect and it's been happy days since.