<?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: Howto let inside users access SSLVPN on outside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558935#M602318</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately you can't connect to the outside ip address for SSL VPN connection from the inside network. If you are connected to your inside network, you would need to enable SSL VPN on the inside interface, and connect to the ASA inside interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Sep 2010 14:28:29 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2010-09-29T14:28:29Z</dc:date>
    <item>
      <title>Howto let inside users access SSLVPN on outside</title>
      <link>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558934#M602317</link>
      <description>&lt;P&gt;We use a ASA5505 for as a firewall appliance and for users to connect to SSLVPN via the webvpn client. We can connect fine from home but we would also like to be able to connect from inside the firewall to be able to install the client onto new notebooks. What is needed to allow this? When ever we try no connection is established and the log shows first: 192.168.170.11&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;23088&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;x.x.104.84&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;443&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Built inbound TCP connection 8729087 for inside:192.168.170.11/23088 (192.168.170.11/23088) to identity:x.x.104.84/443 (x.x.104.84/443)&lt;BR /&gt;and then&lt;BR /&gt;192.168.170.11&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;23088&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;x.x.104.84&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;443&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Teardown TCP connection 8729087 for inside:192.168.170.11/23088 to identity:x.x.104.84/443 duration 0:00:00 bytes 0 TCP Reset by appliance&lt;BR /&gt;Does anybody know what will allow us to access the SSL portal page from inside? We don't want to enable SSLVPN on the inside interface because this will require us to configure split DNS and we dont use that. Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 18:47:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558934#M602317</guid>
      <dc:creator>infarm2010</dc:creator>
      <dc:date>2019-03-11T18:47:09Z</dc:date>
    </item>
    <item>
      <title>Re: Howto let inside users access SSLVPN on outside</title>
      <link>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558935#M602318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately you can't connect to the outside ip address for SSL VPN connection from the inside network. If you are connected to your inside network, you would need to enable SSL VPN on the inside interface, and connect to the ASA inside interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Sep 2010 14:28:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558935#M602318</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-09-29T14:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Howto let inside users access SSLVPN on outside</title>
      <link>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558936#M602319</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply. I do find that a bit strange since I had this working for a few month and then it just stopped. I would like to hear if anyone else can verify that the ASA doesn't allow this. Also does that mean you also have to configure split dns to reach the stuff in your DMZ (homepage, webmail and so forth) Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Sep 2010 06:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558936#M602319</guid>
      <dc:creator>infarm2010</dc:creator>
      <dc:date>2010-09-30T06:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Howto let inside users access SSLVPN on outside</title>
      <link>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558937#M602320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, you are correct. You would need to configure split dns as well.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Sep 2010 07:49:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/howto-let-inside-users-access-sslvpn-on-outside/m-p/1558937#M602320</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-09-30T07:49:13Z</dc:date>
    </item>
  </channel>
</rss>

