Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

165480

July 25th, 2013 03:00

Can't launch vWS app, but can connect to Broker on android/iPhone

Hi Guys,

Hoping you can tell me what I've done wrong.  Here's a basic network diagram of how we have things set up:

vWS-network.png, here's how our Secure-IT box is configured: vWS-secureIT.png

On a windows laptop (using port 443), I can connect in fine, I get the vWS webpage, I can login, I can then see my applications, and I can click one and successfully launch it.

On my android or iPhone, I can connect fine (using port 47443), I can login to the vWS app, I can see my applications, but when I try and click one to launch it, I get a "There are no available terminal servers to connect to at this time.  Please report this message to your systom administrator".  This is using the same user, so I know the application is configured correctly as it works fine on a laptop.

Any ideas what I've done wrong?  In the android/iPhone app in the location settings I have it configured like this:

HTTPS selected

Broker Name / IP:

Broker TCP Port: 47443

NAT: ticked

RDP over SSL: ticked

Secure Gateway Name/IP:

Secure Gateway TCP Port: 47443

This is using vWorkspace v8.0 on 2008 R2

Thanks!

1 Message

July 25th, 2013 07:00

Hi Nick,

Should the Secure Gateway TCP Port be 443?

43 Posts

July 25th, 2013 05:00

Hi Nick,

We had simulair issues with version 7.2 en 7.6. we notised that a iphone / ipad user cannot connect trough a load balancer.

So if you use redundant servers with a load balancer. try to connect to just a single server.

July 25th, 2013 23:00

Hi Sander,

Interesting, but not really a solution.  We do have 2 F5s inbetween the internet and the Secure-IT box, but they're non negotiable.  We don't actually do any load balancing though, there's only 1 Secure-IT box and one CB.

Hi Paula,

which bit are you talking about?  In the first diagram?

[edit]

Paula you were right!  I figured out what you meant, it was a client misconfiguration, I changed the port from 47443 to 443 in the client and it works.  Now that I think abou it, it's obvious, really

[/edit]

Cheers,

Nick.

No Events found!

Top