Pollard
Enthusiast
Enthusiast

View Client Authenticating But Unable to get to desktop

I was able to connect before to this secure network with any issues. Nothing has changed on my side

I am able to connect on a different network connection, "from home etc."

Pfsense 2.0 is my firewall.

I connect by accessing a secure cisco desktop with a token which connects fine. Then I open the vmware view client which connects and gets me as far as the login screen. Any ideas on things to check?

I get here

1.jpg

Then it goes blank and locks up

2.PNG

Log file

15:28:26,117 INFO  <3272> [MessageFrameWork] Program 'wswc - VMware View Client' started, version=4.5.0 build-293049, pid=3260, buildtype=release, usethread=1, closeafterwrite=0
15:28:26,149 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_command - VMware View Connection Server Command Handler' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,164 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_http - VMware View Client HTTP Handler' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,164 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rdp - VMware View RDP Handler' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,180 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_rsa - VMware View RSA Handler' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,180 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_tunnel - VMware View Secure Tunnel Client' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,195 INFO  <logloaded> [MessageFrameWork] Plugin 'wswc_ui - VMware View Client UI handler' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,211 INFO  <logloaded> [MessageFrameWork] Plugin 'wssm_uimanager - VMware View Framework UI Host' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,227 INFO  <logloaded> [MessageFrameWork] Plugin 'ws_winauth - VMware View Framework Windows Authentication Support' loaded, version=4.5.0 build-293049, buildtype=release
15:28:26,242 INFO  <Main Thread> [wswc] Windows Client started
15:28:58,180 INFO  <DesktopWindow> [wswc_rdp] RDP control version = 6.0.6001
15:29:06,789 INFO  <DesktopWindow> [wswc_ui] Connecting client to agent via socket channel
15:29:07,070 WARN  <NodeManagerWatcher> [MessageFrameWork] SocketChannel: Unable to connect to 10.xxx.xxx.xxx:32111
15:29:07,070 INFO  <NodeManagerWatcher> [wswc_ui] Revert to connecting client to agent via virtual channel support
15:30:04,383 INFO  <MessageFrameWorkDispatch> [wswc] VMware View Windows Client received shutdown signal
15:30:06,024 INFO  <Main Thread> [wswc] VMware Windows Client stopped (exit code 0)

0 Kudos
4 Replies
mittim12
Immortal
Immortal

If you go the console of this machine are you able to login with no issues?   

0 Kudos
Pollard
Enthusiast
Enthusiast

This, VM machine is on somebody else's Secure network I am connecting over or office wan. I am just trying to double check everything while I am waiting to here back from there IT team. I was able to connect to the desktop using a verizon cellular modem so it kind of made me think its something on my side even though I have changed nothing.

They have it serving up 5 vm machines randomly when we connect, I have been trying to connect for a couple days

0 Kudos
mittim12
Immortal
Immortal

It doesn't look to be View related to me.  In the print screens you are able to connect up via the client, you perform the login, and then the blank screen appears to happen.   My first guess would be something on the desktop.  

0 Kudos
sketchy00
Hot Shot
Hot Shot

Watch the firewall.  Depending on the brand and its abilities to inspect SSL, it may involve a process of stopping, decrypting, inspecting, reassembling, then delivering the packet.  This is exactly what happened when I used a web publishing rule on my TMG firewall.  After a modification, I was able to get it working without issue.

0 Kudos