VMware View - RDP works, PCoIP mit error

Similar Questions

• VMWare View 4.6 PCoIP tunneling problem. UDP is not get tunnel

  
  Hello

  I have the black screen "classic" - question.
  So, when I try to connect to a virtual desktop, I am well auhtenticated, I can select a pool of offices, but once the bureau is launching,
  I just get a black screen and afterawhile it times out.

  I read the manuals, the document http://communities.VMware.com/docs/doc-14974 , written by Mark benson; Watched the video; Checked and re-checked the 3 magic steps;
  Blog reading Sláger, Paul http://paulslager.com/?p=1300 and still I'm stuck. I read the (some the) logs from the login view, view Security Server, View Client and Agent of the view server.
  None of the newspapers I read gave me all significant errors that would have solved this for me. Admitted, 'full' newspapers - trace State, there's a lot that wasn't exactly clear to me.

  I have simplified our mitigation debugging environment to be as follows:

  See connection to the server,
  running on Windows Server 2008 R2 (Datacenter) 64-bit VMware View Server connection 4.6.0 - 366101,.
  Checkboxes for both "Tunnel secure HTTPS: connection to Tunnel secure usage on the desktop" and "PCoIP Secure Gateway: use PCoIP PCoIP Gateway Secure connections to desktop" have been checked.

  View secure server,
  running on Windows Server 2008 R2 (Datacenter) 64-bit VMware View Server Security 4.6.0 - 366101,.
  has been paired with the login server and the two aswell "HTTPS Secure Tunnel: external URL" as "PCoIP Secure Gateway: PCoIP external URL" has been set to a virtual IP address in the firewall external dmz with a dst - nat on the real IP address of the Security Server.

  The reviews are pointing to the virtual IP address of the Server Secure View.

  Since it is not a production environment, I installed a bunch of Wireshark to see traffic;
  I ran traffic snooping on the view connection server, see Security Server, View Client and the virtual desktop connected
  at the same time and have verified that traffic TCP PCoIP on get 4172 port of talked about between my security server host <>client - and the
  securityserver <>- virtual desktop just fine. TCP traffic seems to be in the tunnel. But what bothers me is the wireshark on the virtual office reveals that the virtual office is trying
  to talk subject port 4172 - UDP back directly to my reviews host IP traffic. Because this is not allowed by the firewall, the virtual office propably does not work...

  But all scenarios describe only the Security server could handle all pcoip-traffic with the agent of the view (as shown in the documentation of the Architecture in Figure 5-6), so that no direct connection between the Client of the view and the view Agent is necessary... I can't work. But it is possible, right?

  Any ideas what I could do wrong?

  Help really appreciated.

  It works in the way that you described in your original post. There is no obligation for the virtual office send UDP responses to the client. They will be sent on the Security Server, which will forward them to turn to the customer.

  Something must be configured incorrectly.

  Check very carefully the UDP traffic in your wireshark traces. The client, you should see 4172 TCP for the VIP of your SS. You should then see 4172-UDP to the same VIP. You should see the UDP of SS response to the customer data. The destination for this data answer UDP port must be the source port used for the UDP request. The source for the response data port must be 4172.

  Then check your wireshark SS track. You should see the same customer traffic and you should see a similar PCoIP conversation between the SS and the virtual office. From the virtual desktop, the SS looks like a customer. PCoIP UDP must be sent to the SS, when it is properly configured.

  Client - TCP 4172-> SS - TCP 4172-> Virtual Office

  Customer - UDP 4172-> SS - UDP 4172-> Virtual Office

  Customer<-UDP 4172--="" ss=""><-UDP 4172--="" virtual="" desktop="" (the="" 4172="" here="" is="" src="" port,="" the="" dst="" udp="" port="" will="" be="" the="" source="" port="" of="" the="" udp="" request="" packets="" above)="" 4172--="" virtual="" desktop="" (the="" 4172="" here="" is="" src="" port,="" the="" dst="" udp="" port="" will="" be="" the="" source="" port="" of="" the="" udp="" request="" packets="">

  If you have verified that you can connect to the same virtual desktop with PCoIP then this problem will not be something to do with the virtual office or agent of view etc.

  Check your display settings, network, firewall and NAT.

  Select this option.

• VMWare View 4.6 dual screen error

  Question:

  VMWare View 4.6 process run on a laptop computer of company, with connected external monitor.  Start the display & choose multiple monitors. Starts fine & you can use both screens.

  However, when cell phone and it auto locks VDI, returns the user and their password. Both pop displays perfectly for a fraction of second (the two indidpendant on the other) but then displays update the position of the Office is in the center between the screens and you end up with a shared between the half of each screen, remote desktop effictivly centralize office.

  Only will is to login to vmware view and restore the session. Then, throw two screens independtly from each other.

  

  Action taken:

  Upgrade users view client to version 5 that actually no difference. Disable all screensavers etc, but the auto screen locks. View log files but can find no appearent fault.

  Please see the attached for reference log files

  I'd be very apricate any help because now I am at a loss.

  If you experience this problem only with PCoIP (and not RDP) then follow the Vmware KB 1027899

• VmWare View and working group

  You can install VMware View in a workgroup environment. What is the view installation sequence?. I tried to installed on a working group and it keep asking to connect to a domain during installation View Composer. Then I discovered that you must install sight connection to the server first, then composer. But the view connection server doesnot allow me to install in a workgroup environment. Thank you.

  In regards FT then is it not possible to have that between physical and virtual. Both machines must be virtual.

  It should be easy to connect your computers to a new network. Did you create a new vSwitch? The error messages?

  Best regards

  Linjo

  If you find this information useful, please give points to "correct" or "useful".

• Problems with the module supplier of personalized identification information and overview of VMware View Client working together

  I have a Horizon of VMware View client that connects me HVD Windows 7. So when I give view client Vmware Horizon my credentials, it auto logs me. I also created a custom credential provider that works on Windows 7 PC. When I install the custom in the HVD credentials provider, it works if I am already connected to HVD and I simulate CTRL + ALT + DELETE. Can I use my credential provider to "unlock" in. However, if I disconnect of HVD and try to connect using VMware Horizon View client to connect to Windows 7 of HVD, it gets stuck on the screen of the tile. I see the VMware SSO user tile but nothing happens when I click it. Then, I use my provider of customized credentials to connect. I expect to bypass my ISP credentials on the first connection and self as before.

  Anyone have any ideas?

  Thanks for your help.

  OK, I did some more troubleshooting and discovered that it was a problem with auto connection set to TRUE on my side of custom credentials provider (I pbAutoLogonWithDefault to TRUE). Since I still like it TRUE, I had originally set it to FALSE and then change for REAL once my credential provider was used.

  Thank you!

• VMware View 4 - newspapers PCoIP

  Hello

  Where can I find PCoIP logs (logs from VMware View Client 4.0) in thin or thick client?

  M

  Please watch it on thick Client where the Agent is installed in C:\windows\temp.

  Or also in C:\Document and Setting\All Users\ApplicationData\VMware\VDM\logs.

  MCP, VCP

• VMware view connection failed with status 502 code

  2014 01-20 T 12: 14:40.545 - 03:00 INFO (1248-128 C) < 4748 > [MessageFrameWork] program "wswc - VMware View Client" started, version = 5.4.0 build-1219906, pid = 0 x 1248, buildtype = release, usethread = 1, closeafterwrite = 0

  2014 01-20 T 12: 14:40.576 - 03:00 (1248-1080) INFO < logloaded > [MessageFrameWork] Plugin "wswc_command - VMware View Manager of server connection commands" load, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.576 - 03:00 INFO (1248-0F68) < logloaded > [MessageFrameWork] 'wswc_http - VMware View Client HTTP Handler' Plugin loaded, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.576 - 03:00 INFO (1248 - 16 B 4) < logloaded > [MessageFrameWork] 'wswc_pcoip - VMware View Client PCoIP Interaction Handler' Plugin support, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.576 - 03:00 INFO (1248 - 16 B 8) < logloaded > [MessageFrameWork] "wswc_rdp - VMware View RDP Manager" Plugin support, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 INFO (1248-16BC) < logloaded > [MessageFrameWork] "wswc_tunnel - Secure Tunnel of VMware View Client" Plugin loaded, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 (1248-1698) INFO < logloaded > [MessageFrameWork] 'wswc_rsa - VMware View Manager RSA' Plugin support, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 INFO (1248-062 C) < logloaded > [MessageFrameWork] Plugin "wswc_ui - Manager of user interface of the VMware View Client", version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 INFO (1248-07F8) < logloaded > [MessageFrameWork] 'wssm_uimanager - VMware View Host UI Framework' Plugin loaded, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 INFO (1248 - B 17, 0) < logloaded > [MessageFrameWork] Plugin 'ws_winauth - support for VMware View infrastructure Windows Authentication' support, version = 5.4.0 build-1219906, buildtype = output

  2014 01-20 T 12: 14:40.592 - 03:00 (1248-128 C) INFO < main Thread > [wswc] Option 'ServerURL' set by GPO

  2014 01-20 T 12: 14:40.592 - 03:00 (1248-128 C) INFO < main Thread > [wswc] Option "Domain_name" set by GPO

  2014 01-20 T 12: 14:40.592 - 03:00 (1248-128 C) INFO < main Thread > [wswc] Option "DesktopLayout" set by GPO

  2014 01-20 T 12: 14:40.592 - 03:00 (1248-128 C) INFO < main Thread > [wswc] Windows Client started

  2014 01-20 T 12: 14:42.919 - 03:00 (1248-1024) < MessageFrameWorkDispatch > [wswc_command] year HTTP error error: status code = 502.

  Use the instructions in this KB: KB VMware: VMware View Client configuration to work around the Internet Explorer proxy settings

• Test environment for VMware View 7 - PCoIP Protocol does not work properly

  We test VMware View 7 with as many Thin Clients and customers zero (Teradici)

  When we try to connect via RDP Protocol, it works fine. When we try to connect via the PCoIP Protocol, desktop display seems to blink (about 2 times per second) and display resolution is not acceptable. So, there is a problem with the Protocol (broker or Office VM)

  There are no firewall in the middle.

  Desktop virtual has a clean install.

  So... anyone have the same number? or similar?

  How much video Ram?

  You can increase the video Ram.

• VMWARE HORIZION VIEW 6.0: it does not serve any which RDS (using PCoIP) session to my zero Teradici Clients but it works with Horizon of VMware View client 3.0.0 from my computer

  Hi all

  I'm testing view Horizon 6.0 Service sessions (Windows 2008 R2) RDS through PCoIP. I think that my setup is just because I can connect via Horizion View Client (installed in my laptop or my Android smartphone). But when I try to connect from a Client Tera zero, 1 or 2 (with the latest firmware), at the same time I did logon, I still have this error:

  "View server connection has no return of available virtual desktops."

  Could someone tell what can be wrong?

  Concerning

  As a result of this discussion "Re: RDS support is included in Vmware View (broker)?" I saw that I must spend my customers zero to 4.5.1 firmware. Once I did, Tera 2 Zero Clients work very well but do not have customers zero 1 Tera.

  I expect response from Teradici.

  Concerning

• VMware View Agent 5.2.0 PCoIP over WAN fails

  Recently, I did an upgrade on VMware View VMware view horizon 5.2 4.6 square.

  After the upgrade the 4.6.0 view agent in virtual machines of my parents to view agent 5.2.0 and rebuild the office pools, external PCoIP does not work. Can I open a session in the 5.2 Client view, see the list of office pools, select a pool, the desk at work close and try to open remotely. After 1 second, this error appears:

  Error: Overview of VMware View Client: The connection to the remote computer has ended.

  What does not work:

  • External/WAN via PCoIP for workstations with the view Agent 5.2.0

  What does not work:

  • Internal/LAN via PCoIP for workstations with the view Agent 5.2.0
  • Internal/LAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via RDP for workstations with the view Agent 5.2.0
  • External/WAN via PCoIP for workstations with the Agent View 5.1.3 or lower (tested up to 4.6.0 Agent view)

  I even tried to build a new pool of desktop Windows 7 in a new OU in the active without optimizations VDI directory or group policy. I tried with and without the firewall Windows is activated. In any case, this new office pool works externally via any Agent from view but the view Agent 5.2.0.

  Is it the 5.2.0 Agent view have the same firewall/port that the Agent View 5.1.3 requirements? What else can I test or try to get external PCoIP for desktop computers to work with the view Agent 5.2.0?

  Finally, we discovered the problem / solution. We on a security apparatus of Palo Alto Networks that blocked traffic PCoIP 5.2.0 but not PCoIP 5.1.3 traffic.

  According to a backline Vmware engineer:

  "A change was made to the ephemeral TLS connection that is used to establish trust and to negotiate parameters for subsequent UDP traffic network. This change allows the customer to use their own certificate for TLS server for this connection. For more details of what happens during the installation of PCoIP, and how this changed view 5.2, see KB 1038762. »

  It seems that Palo Alto Networks did not like this change. When we removed our Palo Alto of WAN device, PCoIP 5.2.0 connections could be created. We finally had create a rule to allow the category: private-ip-addresses and URL: pcoip - by default-sni. Once this change has been made, connections WAN PCoIP 5.2.0 started working.

• VMware VIew 6 (PCOIP): Windows Client and web browser connects, Android and Ubuntu - don't

  Hello colleagues!

  VMware Horizon Client 3.4.0 build-2769709

  VMware View 6.1.1 construction-2769403

  VMware vSphere 6.0.0 2776511

  That's what's wrong: used SecurityServer and connecting to the server. External connection - via a router. When it is connected to a vmware PCOIP Protocol (Internet) outside of the view with a Windows client and a web browser, it works fine. But when connecting from Android or Linux (Ubuntu 14) load the desktop does not occur. Android immediately displays the message 'connection to server lost', Ubuntu delivers all messages - I'll be back on the screen to select a pool table.

  Which connection via MS RDP connection protocol is correctly to all customers.

  In the settings ConnectionServer in PCOIP Security Gateway set up the external address of the router.

  Redirect them router ports:

  -TCP 80,443,8443,4172,32111

  -UDP 4172,32111

  Any ideas?

  In security settings server in 'URL of PCOIP' was FQDN, but it must be the IP address.

• Overview of VMware View PCoIP

  Hello

  We have a test lab test view VMware Horizon on a test environment however we find that the following questions.

  When is connected through the vmware view client, enter the user name and then select on the desktop, we find that the following two errors:

  he tries to connect to the desktop computer, then we get a black screen, then a prompt that shows the end of the connection to the remote computer.

  The other mistake that we get is "the Protocol to display for this office is currently unavailable, so if we click try again we get the black screen and then the same error message ended with the connection to the remote computer.

  If we choose RDP, it works.

  This configuration is configured as follows:

  (material f/w)                                      (Win7) (Windows Firewall)

  Client application VMware > > > Firewall > > > > connect to server > > > > Virtual Office

  Firewall hardware ports 443 has sent to the login server

  Hardware firewall has ports open 4172 server to connect to the virtual desktop

  Virtual office has ports open virtual desktop to connect to the server of 4172

  am I missing something?

  What we are seeing with RDP, is that she's bad performance on YouTube and by displaying the web

  Hello

  Looks like your firewall rules are not configured correctly.

  Please refer to this doc and set the rules http://communities.vmware.com/docs/DOC-14974

  Concerning

  Noble

• Problemas con vmware view 4.1 y terminales EVGA 'pcoip '.

  Hola todos,

  I hope to be escuentren very well

  Tengo una consulta en mi tengo vmware virtual center 4.1 entorno y vmware view 4.6

  Estoy put changing Terminal wyse working RDP por q a q el performance pcoip terminals are mucho mejor

  Tengo problemas con some las teminales cuando intentan a1 pcoip an Office Máquinas con esta version of vmware tools "vmware, Inc. product version: 8.3.17.15269, en todas estoy using esta version of officer discovers 4.6.0.366101.

  El problema're q despues el usuario type is the clave para a1 al servidor view appears una pantalla negra como por 5 segundos y despues devuelva has the pantalla inicio donde No. conectamos con el conexion server.

  If yo misma pcoip terminal uso para conectarme a otra Máquina virtual q tiene otra lower vm tools version has the 8.3.17.15269 TR conecta sin problemas. por lo q the diff q veo unica are the vmtools una Máquina a otra... pero todas no is como eso porq I have did a cluster con unas 60 vm con esa version of vm tools. Esto solo pasa con las pcoip terminals porq TR uso una wyse normal con esta version of vm tools 8.3.17.15269 if works

  Saludos,

  Hola Warrenjc

  Te cuento than amendments nosotros y paso el tema esta originado in el orden en what instalan drivers, vmware tools y officer see.

  Well as h. para y no tengas problemas you recommend respetes a raja tabla el orden of deployment of same segun lo indica vmw.

  ES decir.

  1. Instalar the vm.
  2. Instalar vmware tools.
  3. Agent view instalar.

  Fijate if asi you works adecuadamente.

  If haces algun cambio a nivel parches, plots etc, to be replaced by Recomiendan desinstalar todos los compontentes y volver a instalarlos en orden.

  Espero esto resuelva you question.

  Diego Quintana

• VMware View 5 PCoIP get a black screen on wide AREA network

  Hello community,

  I got a VMware View 5 Infrastructure with a vCenter Server, a connectionserver of view and some clients such as VMs.

  Internally, everything works - connections PCoIP and RDP do their job very well.

  Know that we want to publish the vDesktops over the WAN. Users must connect to the virtual machines in their laptops or iPad (or iPhone) at home. So, we have configured our firewall to open the IP Wan (194.209.166.xy) to the internal IP (192.168.199.xy). A DNS entry for view.xy.com shows the IP WAN. If the WAN connection to infrastructure display RDP works - but PCoIP connections shows a black screen after 10 to 30 seconds after logon. We never see an interaction of oder break Windows. The screen is black after the logoninformations in the client view.

  We have configured the connectionserver display settings as described in some articles here... 7

  The external url HTTPS: https://view.xy.com

  checkbox activ: tunnel connection secure user desktop

  PCoIP external url: 194.209.166.xy:4172

  checkbox activ: use pcoip gateway secure for pcoip Desktop connections

  We have forgotten to do some settings or is it an another workaround to work with PCoIP over the WAN?

  Kind regards

  Freddie

  Cross video related to the above article. It describes exactly the configuration you are working. If you have any questions on this subject, let us know and someone on this forum will help you.

  Select this option.

• VMWare View Tunnel error disconnected Client 4.6

  Hi all

  This whole process of view 4.6 always new.

  I get the following error when I try to connect to View Client 4.6 to automated pool of 3 XP desktops. In sight, administrator, I was able to create a pool of 3 computers of Office XP without problem. I called about 5 users to use the pool. I see the pool I created when I use the customer to view. Desktop shows as 'available' in the client.

  When I go to connect through PCOIP or RDP, I get the same error.

  I added a DNS entry for my server view I've seen a few suggestions in other posts, to ensure what has been done (it was not, is now...) but it still does not work.

  Error:

  Tunnel of disconnected

  The secure connection to the server view has suddenly disconnected.

  Reason: create new socket to connect to xx.xx.xxx.xx:443 (PCName.mydomain.com).

  I don't know that I missed something stupid. Anyone can add anything before I have the whole thing scarp and redo? No chance to find this documented error.

  This could be a firewall issue and if so do I need to disable the firewall on the image of the mother and recreate the pool?

  Once again forgive me yet because I'm just a newb... If I did not explain this well enough, hit me with additional questions and I will provide info that I have left out.

  Hello

  If you have a proxy server is configured in the clients Internet Explorer, please disable this and try.

  You are also able to launch Desktop 'use the connection to tunnel secure desktop' is disabled in administrator mode?

  -noble