VMWare View 4.6 dual screen error

Similar Questions

• VMware View 5-10 seconds screen white of abandonment

  Hello

  Internally everything works very well both RDP and PCOIP, but when I try and connect to the outside I get a blank screen and the error message below is displayed

  'The connection to the remote computer is done '.

  We have a firewall watchguard I have a configuration of "Any", and NAT rule to the internal IP address of the server view connection, originally I have just limited the ports concerned but even after I put the port in the ports 'ALL', it still does not work.

  If I try to RDP, he just does not connect "failed to connect to the remote computer", it makes no sense that in their own country I can RDP and PCOIP without problem...

  I tried all the below

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1016633

  Including the increase to increase the VRAM, see increase the video memory on VMware View desktops (1031002)

  Any help would be most appreciated.

  Ian

  Live in Stockholm, not that far away! ;-)

  Please reward points!

  Linjo

• VMware View - RDP works, PCoIP mit error

  HI Leute

  ICH habe bei meiner VMware View Architektur das problem, dass ich beim Verbinden uber den View Client nur das Protokoll RDP use kann. DAS will work wunderbar. As soon as ich aber das PCoIP Protokoll auswahle, kommt also Fehlermeldung beim Verbinden:

  Dieser Office steht zurzeit nicht available. Try later Rubis, eine connection Sie mit diesem herzustellen office, oder wenden Sie sich an your Systemadministrator.

  ICH use VMware View 4.6, mit zugehorigem vCenter Server und connection to the server. Alles ist auf dem could Stand. Am is nicht mit einem Security Server. Lafut're too im trainee alles Moment.

  Die virtuellen Maschinen, die ich mich verbinden laufen auf mit Win 7 x 64

  Hat eine idea, wo yesterday someone das problem konnte liegen? Habe ich vergessen oder please konfiguriert something?

  ICH würde mich freuen, wenn einen Losungsansatz had someone.

  Grüße

  Bopa

  OK, so I ran it through a translator and got the below.

  People in the back, I have the problem with my VMware View architecture that I can use the minutes RDP with the connection by the Client to view only. Will work wonderfully. As soon as I select the PCoIP minutes however, the following error message is delivered with connection: this office is not available at the present time. Try again later connection with this desktop computer or contact your system administrator. I use VMware View 4.6 with partner vCenter server and connecting to the server. Everything is on the latest terms. I'm not however with a security server. It lafut so for now everything in-house. Virtual machines, on which I connect run me with Win 7 x 64 does anyone have an idea, the problem could lie where here? A I forgot something or configured incorrectly? I would be happy, if someone had a solution. Greetings

  So, it sounds like RDP works but you are having problems with PCOIP and everything is internal.    Have you checked that PCOIP is not blocked by any firewall?  It uses the port 4172 so make sure that you unlock that.    Also is this a problem with this particular machine or all of your machines?

• VMware VIew 5.3 with SQL 2008 R2 Express

  Hello world!

  I'm about to deploy VMware View 5.3.

  I'll use a linked clone pool with 100 workstations.

  Can I use SQL 2008 R2 Express X 64 for the composer?

  Y at - there any restrictions I can find in the future?

  Oh, I give bad link VMware View the database to screen sizing & #187; myvirtualcloud.net . Yes, he should be allowed to use Express even for 100 clones, but only for the View Composer database. AFAIK it is recommended not to use SQL Express for vCenter database if you want to run more than 50 virtual machines, BUT it is old recommendation and with the current SQL Express limited 10 GB and 1 CPU or 4 cores, you can also use it to vCenter database I think.

• Error "Failed to connect to the remote computer" VMware View Client

  Hello everyone. I'm currently testing the package VMware view, but stuck on a problem, I can't understand.  I have already tried Googling every possible thing, but still came short on what to do.

  Currently I have:

  Server ESXi 3.5

  -vCenter Server

  -Connection to the server

  -3 swimming pools installed individual office xp host w/view agents

  At the moment, I seemed straight installation because I am able to connect using VMware client/portal with any full blown windows box anywhere in the internal network.  The problem I have is when I try to load the client software VMware view on a HP Neoware e90 box running windows xp embedded.  When I loaded the software and try to connect, I get the address connection server, authentication screen passes, but receives the error "the connection to the remote computer failed" when I try to select one of the desktop images in the list.

  I am capable of everything everywhere, ping from thin client to conn. Server, thin client desktop image and vice versa.  I am also able to RDP in the desktop images in the light client area but just can't understand why it won't pass this error above.  I tried to disable the firewall on everything, but it still doesn't seem to work.  Am I missing a simple step or has someone else has encountered this problem before? Any help would be greatly appreciated. Thank you.

  When you have disabled the firewall was that the firewall or service / network level? If it was at the level of the network, then you must disable the service and stop it. If you have the service, then can you get the logs of the client and post them. Often this info can indicate where he is faced with a problem.

  You want to make a difference in the future of VMware products? Feature to ask your ideas ( http://www.vmware.com/support/policies/feature.html )!

• Event Viewer has perflib and repeated pc blue screen error

  My husband PC crashes which is especially used for WOW; When I checked the critical errors with perflib event log are the problem. I don't know that Vista had hoped for the entry of any person who might have had the same problem, do fix while it goes back into his room.

  Hello

  Check this thread for more information using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive download collected files and after shot/screenshot.
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  -------------------------------------------------------------------------

  Also this, so you can see the probable bluescreens.

  Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
  (also Windows 7)
  http://www.winvistatips.com/disable-automatic-restart-T84.html

  ===========================================================

  Check out these utilities to see if information may be collected:

  It is an excellent tool for displaying the blue screen error information

  -Free - BlueScreenView scans all your minidump files created during "blue screen of death," collisions
  and displays information about all accidents of a table.
  http://www.NirSoft.NET/utils/blue_screen_view.html

  -------------

  MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
  time of the BSOD to provide more information about the possible cause - see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

  ------------

  AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
  application goes down has occurred in your system. The information breaks down is extracted from the .wer
  the files created by the Windows Error Reporting (WER) of the operating system component of each
  time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
  text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

  I hope this helps and happy holidays!

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• How to fix VMware View Server certificate revocation check connection error?

  Dear community,

  For about 2 weeks, I feel a revocation of the certificate check error in our environment Horizon see 6.2. The strange thing is that, within 12 hours about two (replication) connection servers and the vCenter Server / server of composer (on the same machine) are considered as having invalid certificates, even if, in fact, they are valid (CA certificates). We use no security servers.

  The view admin console shows the following for servers connection:

  The server certificate is not approved.

  The server certificate cannot be verified.

  For the vCenter, he said (that I have validated manually the certificate):

  No problems found.

  Certificate is not approved, but the thumbprint of the certificate is accepted.

  With the connection series on 'full', States that the login server logs for the vCenter server:

  TRACE (B 17-0 - 0E98) < VCHealthUpdate > [NativeKeyVault] validateCertificateChain response: {result = FAIL, EndEntityReasons = cantCheckRevoked, ChainReasons = invalid, SelfSigned = false, EndErrorCode = 16777280, EndInfoCode = 258, ChainErrorCode = 16777280, ChainInfoCode = 256, PolicyErrorCode =-2146885613}

  As far as I can see there no similar entries for login server certificates in the newspaper.

  At the moment I am under the environment with composer and vCenter certificates manually valid and invalid connection (red) server certificates (as view clients and browsers are not disabled).

  I already checked that I am able to do everything 'green' again via setting the registry key 'CertificateRevocationCheckType'2 (as described here Configure the server certificates certificate revocation check). This brings me to the conclusion that one of the intermediate certificates cannot be validated. So, I had the information a "version" of an intermediate (intermediate certification authority) certificate has been revoked. There seems to be no coincidence - like the time point is as well, but this particular version does not appear to be used in the servers of my connection.

  However, even with full logging enabled, I can't information which (intermediate) certificate cannot be validated and why. I expected to see something like 'OCSP verification' or 'check the CRL' but I can't find it in the newspapers. However, I noticed that one of the intermediate certificates lacked the OCSP URL (even if the field "Authority Information Access" existed). Of course I updated the certificate with a version that contains the OCSP URL, but it has not changed anything.

  In addition, I checked manually all of the certificates in the chain with openssl (for OCSP) and CRLs as well, but everything seems to be OK (all URLS are accessible and no opportunity of certificate has been revoked). Actually, I do not interpret the error as "that the connection to the server is an invalid certificate because it has been revoked", but "it cannot check if it has been revoked. The servers do not need a proxy and nothing configured, so (I checked the proxy settings system context, also).

  For now, the problem is not critical, such as 'red' status connection server has no effect on our customers and so I could turn off certificate revocation check (or switch to check that the certificate of the server (2)). But of course, I would really solve the problem.

  Is there someone who can give me a hint on what to check, for example, how do I know which certificate cannot be controlled and why? Someone had the same or a similar problem? Support VMware is working on the problem as well, but they seem don't know is not the problem, either.

  I appreciate the thoughts and responses! Thank you!

  Best regards

  Fabian

  Dear community,

  During this time, I was able to correct the error described at the beginning of this thread. Jump to the end to see what could probably help you...

  1. At first, I installed an additional standalone VMware View Server connection in order to check the following related certificates:
     1. VMware support always told me to renew my certificates because they "were not valid" etc. - even if in fact they were (like external URL calls and attested manual verification and tests).
     2. That's why I created new additional certificates for the login server and configured to include the vCenter even as my production environment - only difference was I didn't inlcude the composer who runs the server vCenter himself.
     3. The result was that the server was "green" including both the vCenter Server certificate which could be 'not reliable' by the environment of production - strange, huh?
  2. After I reset the additional server to a turned wink where connection to the server was not yet installed (before that, I uninstalled the connection to the server in case there is information in vCenter thereon) and reinstalled as a replica of the production environment server. Somehow I expected this, but still quite strange the vCenter Server (and composer) now again was considered "invalid", even if the certificate of the server connection itself considered still valid and green. For test purposes, so I put certifice revocation checking on '2' (only one server certificate check) - but only on the 'old' production servers' and 'magical' everything has been considered valid. So as I see it, there seems to be some sort of information stored on the 'old' connection servers that makes them believe that invalid certificates and that the information is replicated on the third server unless I lower the revocation of the certificate controls on these servers. Altervative explanation could be that VMware View does not accept certificates with aliases that do not include the 'real' server name - that is / was in fact certificates the old servers connection. The new server certificate connection included the real name and the alias. I understand if this is the case, but then I expect that it be documented somewhere (I have not found this information) and also wouldn't understand why it worked without problem for several years before.
  3. After finding that out, I created new certificates for the 'old' connection servers, including aliases and real names and replaced the certificate on one of the servers (and restarted the login server) - only a few successfully. Once I put the revocation checking on '4' again on this server, the login server certificate was still considered valid, but not the vCenter and certificate of composer.
  4. Now, I've uninstalled the old login server (removed from the view) and reinstalled completely (including an update of the 2008 R2 2012 R2 OS) and after I have it reintegrated into the environment, everything remained green - as long I have will activate revocation checking on the second login server "old." This is why I did the same with this (completely reinstalled and reinstated it) and now everything is green with the revocation checking enabled on all replicas of server connection.
  5. The next step I uninstall the additional replica because I created only for troubleshooting purposes.

  So what will no doubt help in similar cases:

  • Reinstall the servers of connection one by one, including:
  • Uninstalling html access (if used), uninstall the login server to view, uninstall 'VMware' AD LDS Instance.
  • Removal of the connection to the server of replication group: run "s - r s uninstalled_ vdmadmin.exeservername" on one of the servers connection remaining.
  • Reinstall/Update OS (may not be necessary, but I did not test that)
  • Reininstall, return to the login server replica. If you used the certificates which included only the alias of the server I recommend you to create new ones, including the name of the server as well, but maybe it's not necessary as well. If you want to keep the certificates which only inlcude the alias it will be necessary to install this certificate after the first replication of the servers (see below).

  My question for technicians of VMware/developers: It is supported to use certificates include only the server alias. Otherwise why it worked before and where is it documented? Where are certificate cached information so that simply replace the certificate was only some, and not a complete success (see above). FYI - when I paired initially replicas that I had to install the CA (including only the pseudonym) after the first replication - now with certificates (including the server name and the alias), I could install the certificate before you replicate (= the login server installation).

• Host VMware 5.5 - purple screen error

  Hello.

  Spent months last im getting a purple screen error I have attached it. I called dell since we have the guarantee of the server after I showed the them.the screenshot... they said his mistake of vmware. Please help me what error is.

  Hello and welcome to the community:

  The first line megasas_reset_fusion indicates there is a problem with the driver megasas

  Looks like on there is a known issue with the MegaSAS driver and they recommend you upgrade the version of the driver at: 6.506.51.00.1vmw and later

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2052368

  Suhas

• VMware View 5.1.1 Security Server LDAP errors

  Im having a serious amount of errors on my VMware View (5.1.1) security server

  Log debugging shows a large amount of LDAP errors, see below.

  2012-09 - 06T 10: 46:49.075 + 02:00 ERROR (0610-0940) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 01:50.102 + 02:00 ERROR (0610-0CB8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 16:50.109 + 02:00 ERROR (0610-0FE8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 31:51.120 + 02:00 ERROR (0610-0DD8) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 11: 46:51.132 + 02:00 ERROR (0610-0244) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 01:52.159 + 02:00 ERROR (0610-0F3C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 16:52.155 + 02:00 ERROR (0610-0E5C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 31:53.182 + 02:00 ERROR (0610-0F68) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 12: 46:53.194 + 02:00 ERROR (0610-092 C) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 13: 01:54.217 + 02:00 ERROR (0610-08E4) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE
  2012-09 - 06T 13: 16:54.227 + 02:00 ERROR (0610-0504) < WSAdminDomainTimerThread > [ws_admin] cannot bind to LDAP://rootDSE

  Anyone got any suggestions?

  Hello

  The plugin ws_admin trying to make field checks every 15 minutes, but given that your security server is not on the field these checks fail. It is completely harmless, but they should not run in first place, I raised this in their own country.

  Mike

  Edit:

  There is a simple solution for this in 5.1.x:

  Under the current registry key HKLM\Software\VMware, Inc. \VMware VDM\plugins\wsnm\admin, create a new key named Params, and under that a new DWORD value named InitiateDomainChecks with 0 data. Once set, you will need to restart the VMware View Security Server service for the change to take effect.

• 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.

• Auto-hide taskbar Client - full screen - VMware View 5

  Hello

  We intend to deploy a VMware View solution to all our staff.

  I'm looking for a way to make the default client full screen WITH the bar higher in auto-hide mode (and all this from the command line).

  

  So far, I found no documented to achieve command line option.

  I know that if the first time you have to click once to release the top bar it will remain like this for the next sessions.

  But I would avoid and explain this to all of the staff.

  Alternatively, if you know a registry/command line option to have this totally hidden bar, I'm interested too!

  Thank you,

  Good day

  Eric

  See the Administration Guide from view for the Client Group policies. The search option is the following:

  The shadow pin

  X determines if the PIN on the shadow at the top of the window View Client is enabled and floating of the menu bar does not occur. This setting has no effect if the shadow is disabled. This setting is enabled by default.

• VMware View 4.5 - disconnected sessions connect to black screen or simply close after 5 seconds...

  In collaboration with VMware View 4.5 using images of Windows XP Pro SP3 and connection through PCoIP, everything works perfectly on cloned VMs with the exception of reconnects.

  If I have a user disconnect from their office and then tries to reconnect to the desktop, the screen will be black, if you act quickly, you can retrieve the screen if you enter any keyboard input, but it will come back as if CTRL-ALT-DEL was pressed as I see the pop-up "Windows Security".  I checked for the screensavers screen or something like that and nothing so far.

  Do not have this problem in 4.0.1.

  Any help would be appreciated!

  Thank you

  Shane

  You have the same problem with a desktop XP vanilla without modification? Are there of the sureties or banner of the GPO applied to these desktop computers?

  May panic if there is a logon banner.

  ____________

  blog.eeg3.net | Useful links related to VMware

  If you have found this device or any other post useful, please consider the use of buttons useful/correct for award points.

• Error with Vmware View Client conencting

  Hi guys

  Software

  See 3.1.2

  VMware View 3.1.2

  See Agent 3.1.2

  I created an individual office.

  Windows XP SP3 virtual MACHINE, I've enabled RDP (Remote Desktop) and added to the domain users group access to

  This virtual machine.

  Now I use the test account that is part of the domain users.

  I opened Vmware View Client I get the WinXP which has the right to the domain users but when I click on connect

  I get this error

  Error when using Vmware View Client 3.1.2

  ""This Office is currently not available. " "Please, try to connect to this desktop computer later, or contact your system administrator.

  This is linked with the permissions?

  check the fixing

  Thank you very much

  Make sure that the Windows Firewall is disabled really. Allowed, start, stop and then turn it off again.

  The view Agent starts the firewall service (even if it has been disabled) to add a firewall rule for RDP. The sequence above should ensure that really, he is arrested.

  Mike

• 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

• 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.