<?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 Teamviewer with HTTPs Proxy on Ironport S160 not working in Web Security</title>
    <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443608#M4491</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Donny,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for the repley.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the identity No Authentication is selectet only the User Agent is set to DynGate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the grep output I take it that&amp;nbsp; for all Teamviewer trafic the correkt user agent "useragent.dyngate.id" and the correct decrytion policy "no.dp" is applied with the PASSTHRU aktion being set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any further insight is appriciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Feb 2014 07:25:38 GMT</pubDate>
    <dc:creator>BetonKemmlerIT</dc:creator>
    <dc:date>2014-02-14T07:25:38Z</dc:date>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443606#M4489</link>
      <description>&lt;P&gt;I activated the HTTPS Proxy on our Ironport S160 . To start with I created decrypt rule that puts all request on passthru. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now everything is working except Teamviewer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a UserAgent identity für DynGate and included this identity in the no.de rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A GREP gives me this output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CONNECT tunnel://master12.teamviewer.com:443/ - PASSTHRU_CUSTOMCAT_7-no.dp-useragent.dyngate.id-NONE-NONE-NONE-DefaultGroup&lt;/P&gt;&lt;P&gt;CONNECT tunnel://95.211.37.202:443/ - PASSTHRU_WEBCAT_7-no.dp-useragent.dyngate.id-NONE-NONE-NONE-DefaultGroup&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could anybody give me a hint as to what i need to to get Teamviewer working. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If disable the https proxy Teamviewer is working again.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2014 07:57:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443606#M4489</guid>
      <dc:creator>BetonKemmlerIT</dc:creator>
      <dc:date>2014-02-13T07:57:01Z</dc:date>
    </item>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443607#M4490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using authentication in your identity, disable authentication and try again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;Donny&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2014 01:32:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443607#M4490</guid>
      <dc:creator>donnylee</dc:creator>
      <dc:date>2014-02-14T01:32:35Z</dc:date>
    </item>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443608#M4491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Donny,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for the repley.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the identity No Authentication is selectet only the User Agent is set to DynGate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the grep output I take it that&amp;nbsp; for all Teamviewer trafic the correkt user agent "useragent.dyngate.id" and the correct decrytion policy "no.dp" is applied with the PASSTHRU aktion being set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any further insight is appriciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2014 07:25:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443608#M4491</guid>
      <dc:creator>BetonKemmlerIT</dc:creator>
      <dc:date>2014-02-14T07:25:38Z</dc:date>
    </item>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443609#M4492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Markus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share the whole access log (there should be more entries) from grep so we can look at the details from all teamviewer traffic?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2014 16:46:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443609#M4492</guid>
      <dc:creator>donnylee</dc:creator>
      <dc:date>2014-02-14T16:46:08Z</dc:date>
    </item>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443610#M4493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Donny,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your repley. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since this went a little deeper into the ironport config then my expertise in this matter, I consultet our Cisco partner.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He found out that there is a setting that is only available through the cli that applies to this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Advancedproxyconfig-&amp;gt;MISCELLANEOUS-&amp;gt;Would you like to block tunneling of non-SSL transactions on SSL Ports?&lt;/P&gt;&lt;P&gt;-&amp;gt;Yes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can´t say much about it but it might point someone else with the same problem in the right direction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway Teamviewer 9 is now working with https proxy enable. Teamviewer ist set on passthru.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Feb 2014 16:15:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443610#M4493</guid>
      <dc:creator>BetonKemmlerIT</dc:creator>
      <dc:date>2014-02-21T16:15:21Z</dc:date>
    </item>
    <item>
      <title>Teamviewer with HTTPs Proxy on Ironport S160 not working</title>
      <link>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443611#M4494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Markus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Glad to know you could find local support to get this issue solved.&lt;/P&gt;&lt;P&gt;For sure this information can be used as assistance in case someone else gets into the same problem.&lt;/P&gt;&lt;P&gt;Thanks for sharing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Donny&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Feb 2014 23:02:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/web-security/teamviewer-with-https-proxy-on-ironport-s160-not-working/m-p/2443611#M4494</guid>
      <dc:creator>donnylee</dc:creator>
      <dc:date>2014-02-22T23:02:38Z</dc:date>
    </item>
  </channel>
</rss>

