<?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 Could I add a nat rule and in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515503#M237860</link>
    <description>&lt;P&gt;Could I add a nat rule and create a network object for the owa ip, say source interface outside destination int any, destination address OWA? &amp;nbsp;just a thought..:)&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2014 15:29:46 GMT</pubDate>
    <dc:creator>smason1970</dc:creator>
    <dc:date>2014-06-04T15:29:46Z</dc:date>
    <item>
      <title>Setup webmail with public IP on a ASA 5512x</title>
      <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515502#M237858</link>
      <description>&lt;P&gt;I have a 5512x Running ASA Ver 9.1(2) ASDM&amp;nbsp; Ver 7.1(3) and I am trying to figure out how to setup my companys Webmail,&amp;nbsp;The webmail is on a public ip addres seperate from the address of the&amp;nbsp;ASA,&amp;nbsp;the request will be coming in the 0/0 port from the outside looking for the webmail address, so how would I set this up. with a static route or?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:17:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515502#M237858</guid>
      <dc:creator>smason1970</dc:creator>
      <dc:date>2019-03-12T04:17:28Z</dc:date>
    </item>
    <item>
      <title>Could I add a nat rule and</title>
      <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515503#M237860</link>
      <description>&lt;P&gt;Could I add a nat rule and create a network object for the owa ip, say source interface outside destination int any, destination address OWA? &amp;nbsp;just a thought..:)&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 15:29:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515503#M237860</guid>
      <dc:creator>smason1970</dc:creator>
      <dc:date>2014-06-04T15:29:46Z</dc:date>
    </item>
    <item>
      <title>Create a network object with</title>
      <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515504#M237863</link>
      <description>&lt;P&gt;Create a network object with the inside IP Address of your OWA server (ie 192.168.1.150) and add a static nat&lt;/P&gt;&lt;P&gt;&lt;EM&gt;object network owa-server&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&amp;nbsp;host 192.168.1.150&lt;BR /&gt;&amp;nbsp;nat (inside,outside) static interface service tcp https https&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;then create an access rule to allow outside traffic to be directed to that server&lt;/P&gt;&lt;P&gt;&lt;EM&gt;access-list outside_access_in extended permit tcp any host 192.168.3.150 eq https &lt;/EM&gt;&lt;/P&gt;&lt;P&gt;that should be all you need. then to access the server, just type in your public IP Address i.e. &lt;A href="https://10.10.10.10/owa&amp;nbsp;" target="_blank"&gt;https://10.10.10.10/owa&amp;nbsp;&lt;/A&gt;; (or if you have dns setup, you would do &lt;A href="https://owa.mycompany.com/owa&amp;nbsp;" target="_blank"&gt;https://owa.mycompany.com/owa&amp;nbsp;&lt;/A&gt;; and you should be good.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Lee&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 16:08:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515504#M237863</guid>
      <dc:creator>Lee Dress</dc:creator>
      <dc:date>2014-06-04T16:08:35Z</dc:date>
    </item>
    <item>
      <title>Ok thanks for that reply I</title>
      <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515505#M237865</link>
      <description>&lt;P&gt;Ok thanks for that reply I havent tried it yet , I went live with this after work and our echange can send email but not recive. strange&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 21:09:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515505#M237865</guid>
      <dc:creator>smason1970</dc:creator>
      <dc:date>2014-06-04T21:09:54Z</dc:date>
    </item>
    <item>
      <title>Even though your client sends</title>
      <link>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515506#M237869</link>
      <description>&lt;P&gt;Even though your client sends and receives with https when using OWA, the server also needs to be able to receive mail (from external servers) via smtp (tcp/25). So add an ACL entry to the outside_access_in list above with "eq smtp" at the end. e.g.:&lt;/P&gt;&lt;P&gt;&lt;EM style="color: rgb(119, 119, 119); font-size: 14px;"&gt;access-list outside_access_in extended permit tcp any host 192.168.3.150 eq smtp&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 21:33:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/setup-webmail-with-public-ip-on-a-asa-5512x/m-p/2515506#M237869</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-06-04T21:33:51Z</dc:date>
    </item>
  </channel>
</rss>

