Start a Conversation

Unsolved

This post is more than 5 years old

3521

August 2nd, 2015 03:00

Unable to connect to View 4 server

Exclamation Unable to connect to View 4 server

Works fine from Windows 7, iPhone, and iPad, but not Android... It just hangs at "Loading Connection..." after manually connecting to a saved profile. This is using port 80, just like on my iPhone, and I can see all of the HTTP traffic going back and forth.


These are the pertinent logs from View4 Admin console:

(SESSION:C2731006BD40A17095B21C2C353BECDB Kfletcher) User DOMAIN\user has successfully authenticated to VDM

(SESSION:C2731006BD40A17095B21C2C353BECDB) BROKER_LOGON:USER OMAIN\user;USERSID:S-1-5-21-220523388-1614895754-682003330-12529;USERDN:CN=S-1-5

(SESSION:C2731006BD40A17095B21C2C353BECDB) BROKER_LOGON:USER OMAIN\user;USERSID:S-1-5-21-220523388-1614895754-682003330-12529;USERDN:CN=S-1-5-21-220523388-1614895754-682003330-12529,CN=ForeignSecurityPrincipals,DC=vdi,DC=vmwar e,DC=int;

 

Here's the last HTTP POST from PocketCloud Pro v1.1.208. I did a comparison with iPhone and basically the iPhone uses all 1 HTTP channel for the POSTs while Android uses individual HTTP sockets. The client sends a FIN each time it finishes a command to View. On iPhone, it is all one HTTP socket the whole time.


POST /broker/xml HTTP/1.1
Host: 172.20.1.42
User-Agent: WTOS/1.0
OSVersion: 1.0
Content-Length: 80
Keep-Alive: 300
Connection: Keep-Alive
Cookie: com.vmware.vdi.broker.location.id=287c99ac-6fe3-477e-a7c7-c41c9b693dfe;JSESSIONID=E00CAE36F6AA9C39B3EA0D53EC 7952FA
Accept: */*



HTTP/1.1 200 OK
Content-Length: 376
Content-Type: text/xml;charset=UTF-8


.
.
.
.
.. ok
..

.
.
.
.. E00CAE36F6AA9C39B3EA0D53EC7952FA
.. 16344
.. http://view4.acmegizmo.com:80
..
.. 4
.
.
.
.
.
.
.

iPhone shows client version 3.1 while Android shows client version 4.0. Both are setup as Vmware VDI (not RDP).

Both devices send the same HTTP commands in the same order, but then the iPhone sends get-desktops to get more info, while while Android jumps right to get-tunnel-connection, which is the next one. On iPhone, when it gets a response for get-desktops and then get-tunnel-connection, it then POSTs get-desktop-connection which is the final command it appears. On Android, it never does anything after the (premature?) get-tunnel-connection command. It just gives up on the wire (no more packets) and the UI just sits there spinning at "Loading Connection..." I never waited more than a few minutes, but it goes and goes forever it seems like.



Any ideas??

5 Posts

August 5th, 2015 23:00

Thanks Roger!

623 Posts

August 5th, 2015 23:00

I will pass the information to the developers. We'll let you know.

 

 

 


Roger Montalvo 
Visit our Dell Wyse Thin Client Knowledge Base and Manuals web site at www.wyse.com/KB
Visit our Dell Wyse PocketCloud Knowledge Base and Manuals web site at http://pocketcloudsupport.wyse.com/forums
[SIGPIC][/SIGPIC]

5 Posts

August 13th, 2015 01:00

Any updates on this?

No Events found!

Top