Release:vWorkspace Connector for Android 1.1.1

Hi,

I'm trying to get the android connector working in my company, but running into some problems.  We have tried with the iPad connector and it works fine, however with the android one it can never connect.  We are able to connect to the farm, so it displays all the icons i can click on, but when i click any of them, i get the error message:

Could not establish a connection to the server

Any ideas?  The only thing i could think of is we have legal text that comes up before you can login to the terminal server (RDSH), and maybe the android client can't handle it?  on the iPad client after you click an icon to load, it shows the legal text, you click OK, and then the rest works perfectly.

I'm having this issue on both an android phone (samsung Galaxy S II), and an android tablet (asus transformer).

Thanks in advance, and if you'd prefer that i start a new thread about this please let me know.

Nick.

Hi Nick

Can you confirm that you are using version 1.1.1 of the Android Connector and not an earlier version, such as 1.1?

Did you enable the application logging to see if that shows any more information about the connection failure. The User Guide describes how to enable the logging option.

Kind Regards

David

Hi David,

Yes, both devices are a fresh install - v1.1.1.

I have enabled logging during a connect and uploaded the results here:  http://twosx.net/work/vWorkspace_10-38-19-10-11.txt

Nick.

Hi Nick,

Thanks for uploading the log file. Can you tell me how your Android device is connected to the network, are you using a 3G connection or WIFI?

During the test was the device on a network that is connected to your vWorkspace servers, or would it have been an external connection across the Internet?

I can not see anything in the log to suggest the legal text is to blame for the connection failure. The connection details show the IP address of the server but the connection fails due to a timeout.

Are you able to install a Telnet client onto the device and check connectivity to the IP 10.1.91.33 on port 3389

Regards

David

Nick,

I was able to locate an Android device in the office and have tested a connection to my vWorkspace farm both with and without the legal text pre-logon message, it works just fine.

David

Hi David,

I'm connecting via Wifi on the public internet.  We then have a public NAT'd address to our SecureIT box.  The connection broker is 10.1.91.33, so there's no way i'd be able to telnet to it from the internet.

the location settings on the android are as follows:

broker name/IP: our public facing IP

broker TCP port: 98443

NAT: unticked

RDP over SSL: ticked

secure gateway name/ip: our public facing IP

secure gateway tcp port: 443

our secureIT settings are as follows:

RDP proxy

local IP: secureIT box IP (which the public IP gets translated to)

local port: 443

Web interface proxy

local ip: secureIT box IP

local port: 443

destination host: 10.1.91.33

destination port 443

enable SSL: ticked

connection borker proxy

local ip: secureIT box IP

local port: 98443

destination hosts: 10.1.91.33

destination port: 8080

enable SSL: ticked

i assume you are referring to this line in the logs:

INFO: com.provisionnetworks.pntsc.PNTSC:  Connecting to 10.1.91.33:3389 ...

is this saying that my android is directly trying to connect to 10.1.91.33 on port 3389?  or is it saying "through the magic of tunnelling via your secureIT box our resultant connection will be to 10.1.91.33 on port 3389"?  because if it's the former.. that'll never work.

This setup works fine for the iPad.

Nick.

Hi Nick,

Thank you for replying with the additional information. Now I know that you are not on an internal network I can see why the connection is failing. Your connection must traverse the Secure-IT (SSL Gateway) server in order to be able to connect to the internal host, otherwise as you say, it will never work.

In the connection log file that you posted the other day there is a section that would show the server name/IP and the port for the SSL gateway, in your case this is not correctly set, i.e. empty:

command:s:pnstart.exe

enablesso:i:0

enablekerberos:i:0

sslgateway:s::

This means it is attempting a direct connection without going via the SSL Gateway and is why you are getting a connection timeout.

I understand this works on your iPad so imagine that Android is more picky about the settings used. I suggest raising a case, as Andrew requested, we can then work with you to correct this.

Regards

David

ok strange, because i definitely have the SSL gateway set in my location settings.

in the android client settings above i lied a bit - for the "broker name/IP" and "secure gateway name/ip" i said our public IP, but actually i have in there the FQDN (blah.com)

i'll raise a case..

We are trying the latest Android client with our vWorkspace environment.

How should users connect to the farm if we are using the secure SSL gateway + RSA?

If I'm correct they should just go to the sucre website, login, and then the .pit should be automaticly opened with the android client. Without configuring anything.

Is this the right way? Because that doesn't seem to work.

After login, the user tabs his VDI icon. The VDI session starts in the background, but nothing happens on the Android.

Just trying the Android client on an Asus Transformer. Works good except for the keyboard. The first letter after holding shift gets swallowed. Example: holding shift and pressing qqww results in QWW. I also tried an external usb keyboard with the same result :/

Thanks Mounty,

we are working this issue and it should be resolved in the next release of the Android connector.

Kelly Craig

Are you using Web Access for two-factor?

Yes, web access for two factor!

They can login into web access, click on their virtual desktop, and then nothing happens.

I suggest you open a support case regarding this.