Horizon View 6: "Tunnel reconnection is not permitted" in Win + "Connection reset by peer" in OSX

[oivinde]

Just upgraded View from 5.3 to 6.0, and have problems logging on to security gateway with Windows and Mac clients. HTML5/Blast via browser works just fine -> Logs in, and show me the available desktops, and of course lets me connect to them.

Logging on directly to connection manager works fine with client in LAN. Logging into security gateway via LAN gives same error.

Event log in connection manager confirms me logging on, but no trace of connection dropping.

Really don't get this, since the session fails/disconnects right after autentication (do not complete the logon, stuck in login dialogue).

Tested with 2.3 and 3.0 clients.

Have generated a support bundle on the security gateway and looked at most of the logs, and don't see any obvious stuff there.

IPSec tunnel between sec.gateway and connection manager is okay.

Anyone else seen this and have a couple of hints before I "go deep"? 🙂

Hva rebooted all servers and desktops, as well as clients, and don't understand the "reconnect" message, since I do a "fresh" connection.

br

Oivind

[Gaurav_Baghla]

To me it sounds in the PCoip Gateway Configuration  http://kb.vmware.com/kb/1036208

[oivinde]

Yeah, that's what I tought too, but since there's no config changes related to this (upgrade), and connection drops before I even get to choose what desktop I want to connect to, I'm not so sure that this is a PCoIP isolated problem.

Does the client communicate over PCoIP when it authenticates and requests the list of available desktops? Isn't that done over SSL? I tought the PCoIP tunnel was initiated when the client connected to a spesific desktop.

--

And just testet with an iPad -> Works just fine. Can logon, and connect to desktops successfully.

So, again, not certain that this is a PCoIP problem.

In the client log in Windows, I get this:

BrokerItem::Connect : [User] Enter ConnectToServer:view.XXXXX.no.

2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::SSLSettings : SSL 2.0: Disabled

2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : SSL 3.0: Enabled

2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.0: Enabled

2014-07-02 10:19:08.083+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.1: Enabled

2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::IsProtocolDisabled : TLS 1.2: Disabled

2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::GetCipherControlString : SSL cipher control string from registry: AES:!aNULL:!eNULL:!EXPORT:@STRENGTH

2014-07-02 10:19:08.084+01:00 DEBUG (1628) [WinCDK] SSLSettings::GetSSLSettings : Cipher String from client: AES:!aNULL:!eNULL:!EXPORT:@STRENGTH

2014-07-02 10:19:08.175+01:00 INFO (1628) [WinCDK] BrokerItem::Connect : [User] Exit  ConnectToServer:view.XXXXXX.no.

2014-07-02 10:19:08.175+01:00 INFO (1628) [libcdk] TUNNEL INTERRUPTED: Could not establish tunnel connection

--

Running the 2.3 client on another machines throws this message:

Error reading from tunnel HTTP Socket: An established connection was aborted by software in your host machine.

Message was edited by: Oivind Ekeberg

[oivinde · Accepted solution]

Well, figured out that I might as well could do a reinstall of the security server.

And, that's when I found the issue!

During reinstall wizard, I noticed something that dodged the radar yesterday, and that was the portnumber on External URL. During upgrade yesterday, this got changed to 8443 in some way (I know I didn't type it in), and after correcting that to 443, everything now works just fine.

Problem solved! 🙂