<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: EUC Access Point 2.8 - BLAST not working in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/EUC-Access-Point-2-8-BLAST-not-working/m-p/2746550#M74603</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are several possible causes of this. The common ones are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Check your UAG/AP appliance blastExternalURL setting. e.g. httpss://ap1.myco.com:443. Make sure it references a hostname that can be resolved by the client to get to your UAG/AP appliance. If PCoIP is working then this hostname will the name that resolves to the IP address you used in the equivalent pcoipExternalURL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If your blastExternalURL uses port 8443 instead of 443, then make sure your Internet facing firewall also allows TCP 8443 in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. If you have a firewall between the UAG/AP appliance and the virtual desktops and RDS Hosts make sure that allows TCP port 22443 from the UAG/AP appliance to any virtual desktop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Make sure you don't have the option set in Connection Server to gateway Blast connections. The setting for Connection Server "Use Blast Secure Gateway ..." should be unticked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. If you use a load balancer, make sure it is set up correctly to ensure that this Blast connection from the client (on TCP 443 or 8443) gets directed to the same UAG/AP appliance as was used for the initial authentication. This is described in more detail here - &lt;A href="https://communities.vmware.com/docs/DOC-32792"&gt;Load Balancing across VMware Unified Access Gateway Appliances (formerly known as Access Point)&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let us know if any of these resolve this for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Mar 2017 08:17:36 GMT</pubDate>
    <dc:creator>markbenson</dc:creator>
    <dc:date>2017-03-24T08:17:36Z</dc:date>
    <item>
      <title>EUC Access Point 2.8 - BLAST not working</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/EUC-Access-Point-2-8-BLAST-not-working/m-p/2746549#M74602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a new UAG install using version 2.8 and our Blast isn't working.&amp;nbsp; All else is fine, and we even have the certificate installed.&amp;nbsp; There is another post hinting that the complex password in the deploy script should be simple and ours is simple.&amp;nbsp; PCoIP is working.&amp;nbsp; The client works.&amp;nbsp; Blast does not.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When accessing via Blast, we can login, we see the desktop but when we click the desktop, we just get a white or gray screen and nothing ever happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our locked.properties file has the balancedhost entry in it with our VIPs IP address.&amp;nbsp; Still no joy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cliff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 20:44:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/EUC-Access-Point-2-8-BLAST-not-working/m-p/2746549#M74602</guid>
      <dc:creator>crp0499</dc:creator>
      <dc:date>2017-03-23T20:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: EUC Access Point 2.8 - BLAST not working</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/EUC-Access-Point-2-8-BLAST-not-working/m-p/2746550#M74603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are several possible causes of this. The common ones are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Check your UAG/AP appliance blastExternalURL setting. e.g. httpss://ap1.myco.com:443. Make sure it references a hostname that can be resolved by the client to get to your UAG/AP appliance. If PCoIP is working then this hostname will the name that resolves to the IP address you used in the equivalent pcoipExternalURL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. If your blastExternalURL uses port 8443 instead of 443, then make sure your Internet facing firewall also allows TCP 8443 in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. If you have a firewall between the UAG/AP appliance and the virtual desktops and RDS Hosts make sure that allows TCP port 22443 from the UAG/AP appliance to any virtual desktop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Make sure you don't have the option set in Connection Server to gateway Blast connections. The setting for Connection Server "Use Blast Secure Gateway ..." should be unticked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. If you use a load balancer, make sure it is set up correctly to ensure that this Blast connection from the client (on TCP 443 or 8443) gets directed to the same UAG/AP appliance as was used for the initial authentication. This is described in more detail here - &lt;A href="https://communities.vmware.com/docs/DOC-32792"&gt;Load Balancing across VMware Unified Access Gateway Appliances (formerly known as Access Point)&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let us know if any of these resolve this for you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Mar 2017 08:17:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/EUC-Access-Point-2-8-BLAST-not-working/m-p/2746550#M74603</guid>
      <dc:creator>markbenson</dc:creator>
      <dc:date>2017-03-24T08:17:36Z</dc:date>
    </item>
  </channel>
</rss>

