<?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: DMZ server access problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937815#M26842</link>
    <description>Additional details required as the given configuration is partial. But I think you have route issue.&lt;BR /&gt;&lt;BR /&gt;What is the Gateway for your Anti-Virus server 124.124.124.2?&lt;BR /&gt;Do you have ROUTE for the DMZ server 172.16.1.100 on the ROUTER 1841?&lt;BR /&gt;Can you post "Show ip route" on the Router?&lt;BR /&gt;Output of the packet tracer "packet-tracer input OUTSIDE icmp 124.124.124.2 8 0 172.16.1.100 detailed&lt;BR /&gt;&lt;BR /&gt;To give brief explanation.&lt;BR /&gt;&lt;BR /&gt;Your Internal and DMZ network go through ASA to reach to Anti-Virus Server. The ASA send traffic for Anti-Virus Server on the OUTSIDE interface but it NAT the traffic with OUTSIDE IP 123.123.123.x. going out. So when it reaches to the Anti-Virus Server, It has path back to 123.123.123.x hence ping from Internal and DMZ to the Anti-Virus Server Succeed.&lt;BR /&gt;Now when Anti-Virus Server 124.124.124.2 initial Ping to DMZ server 172.16.1.100 it sends traffic to the Gateway (Which at the moment we are not aware as if it is your Router's interface 124.124.124.1 or the ISP's Interface). If it is your Router's interface 124.124.124.1, The ROUTER must have ROUTE to that destination 172.16.1.100 sending traffic to ASA on the OUTSIDE interface. It can be Static or Dynamic ROUTE.&lt;BR /&gt;&lt;BR /&gt;First You should have proper ROUTE so that packet can reach to ASA.&lt;BR /&gt;Then we can check for block on the ASA, however your ACL applied on the OUTSIDE interface allow all traffic. (These is not consider secure)&lt;BR /&gt;&lt;BR /&gt;I hope this helps you.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;### RATE ALL HELPFUL RESPONSES ###</description>
    <pubDate>Wed, 09 Oct 2019 11:01:22 GMT</pubDate>
    <dc:creator>bhargavdesai</dc:creator>
    <dc:date>2019-10-09T11:01:22Z</dc:date>
    <item>
      <title>DMZ server access problem</title>
      <link>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937768#M26829</link>
      <description>&lt;P&gt;We are configured Cisco ASA firewall with three network , One Router and a Switch.&lt;/P&gt;&lt;P&gt;One Anti-Virus server are used for antivirus server updated,&amp;nbsp;IP 124.124.124.2 which is connected to Campus Router&amp;nbsp;&lt;/P&gt;&lt;P&gt;*Campus Router Cisco 1841 Interface&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gig0/1 = 124.124.124.1&lt;/P&gt;&lt;P&gt;Gig0/0 = 123.123.123.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*Cisco ASA 5506 interface&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gig 0/1 (Inside=10.10.10.1 /24)&lt;/P&gt;&lt;P&gt;Gig 0/3 (DMZ = 172.16.1.0/24)&lt;/P&gt;&lt;P&gt;Gig 0/8 (Outside =123.123.123.0/24)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All lasted AntiVirus definition update package are download Server (124.124.124.2) and it is send to DMZ server 172.16.1.100.&amp;nbsp;&lt;/P&gt;&lt;P&gt;All internal endpoint are ping to DMZ server as well as 124.124.124.2 server&lt;/P&gt;&lt;P&gt;DMZ server 172.16.1.100 are ping to internal network as well as 124.124.124.2 server.&lt;/P&gt;&lt;P&gt;But when I ping Update server 124.124.124.2 to DMZ server 172.16.1.100 , Not able to ping&lt;/P&gt;&lt;P&gt;===================Campus Router 1841 Configuration=============&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/1&lt;/P&gt;&lt;P&gt;IP address&amp;nbsp;124.124.124.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;/P&gt;&lt;P&gt;IP address 123.123.123.1 255.255.255.0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Router ospf 1&lt;/P&gt;&lt;P&gt;network 124.124.124.0 255.255.255.0 area 0&lt;/P&gt;&lt;P&gt;network 123.123.123.0 255.255.255.0 area 0&lt;/P&gt;&lt;P&gt;==================ASA 5506 Configuration=====================&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;BR /&gt;nameif inside&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.10.10.1 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface GigabitEthernet1/8&lt;BR /&gt;nameif outside&lt;BR /&gt;security-level 0&lt;BR /&gt;ip address 123.123.X.X 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;object network LAN&lt;BR /&gt;subnet 10.10.10.0 255.255.255.0&lt;BR /&gt;nat (inside,outside) dynamic interface&lt;/P&gt;&lt;P&gt;object network VLAN-2&lt;BR /&gt;subnet 10.20.10.0 255.255.255.0&lt;BR /&gt;nat (inside,outside) dynamic interface&lt;BR /&gt;object network VLAN-3&lt;BR /&gt;subnet 10.30.10.0 255.255.255.0&lt;BR /&gt;nat (inside,outside) dynamic interface&lt;BR /&gt;object network VLAN-4&lt;BR /&gt;subnet 10.40.10.0 255.255.255.0&lt;BR /&gt;nat (inside,outside) dynamic interface&lt;BR /&gt;!&lt;BR /&gt;route outside 0.0.0.0 0.0.0.0 123.123.X.1&lt;BR /&gt;!&lt;BR /&gt;access-list in-to-internet extended permit ip any any&lt;BR /&gt;access-list in-to-internet extended permit icmp any any&lt;BR /&gt;!&lt;BR /&gt;access-group in-to-internet in interface outside&lt;BR /&gt;access-group in-to-internet in interface dmz&lt;BR /&gt;!&lt;BR /&gt;class-map inspection-default&lt;BR /&gt;match default-inspection-traffic&lt;BR /&gt;!&lt;BR /&gt;policy-map global-policy&lt;BR /&gt;class inspection-default&lt;BR /&gt;inspect dns&lt;BR /&gt;inspect http&lt;BR /&gt;inspect icmp&lt;BR /&gt;!&lt;BR /&gt;service-policy global-policy global&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 10:16:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937768#M26829</guid>
      <dc:creator>dinchavan</dc:creator>
      <dc:date>2019-10-09T10:16:48Z</dc:date>
    </item>
    <item>
      <title>Re: DMZ server access problem</title>
      <link>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937815#M26842</link>
      <description>Additional details required as the given configuration is partial. But I think you have route issue.&lt;BR /&gt;&lt;BR /&gt;What is the Gateway for your Anti-Virus server 124.124.124.2?&lt;BR /&gt;Do you have ROUTE for the DMZ server 172.16.1.100 on the ROUTER 1841?&lt;BR /&gt;Can you post "Show ip route" on the Router?&lt;BR /&gt;Output of the packet tracer "packet-tracer input OUTSIDE icmp 124.124.124.2 8 0 172.16.1.100 detailed&lt;BR /&gt;&lt;BR /&gt;To give brief explanation.&lt;BR /&gt;&lt;BR /&gt;Your Internal and DMZ network go through ASA to reach to Anti-Virus Server. The ASA send traffic for Anti-Virus Server on the OUTSIDE interface but it NAT the traffic with OUTSIDE IP 123.123.123.x. going out. So when it reaches to the Anti-Virus Server, It has path back to 123.123.123.x hence ping from Internal and DMZ to the Anti-Virus Server Succeed.&lt;BR /&gt;Now when Anti-Virus Server 124.124.124.2 initial Ping to DMZ server 172.16.1.100 it sends traffic to the Gateway (Which at the moment we are not aware as if it is your Router's interface 124.124.124.1 or the ISP's Interface). If it is your Router's interface 124.124.124.1, The ROUTER must have ROUTE to that destination 172.16.1.100 sending traffic to ASA on the OUTSIDE interface. It can be Static or Dynamic ROUTE.&lt;BR /&gt;&lt;BR /&gt;First You should have proper ROUTE so that packet can reach to ASA.&lt;BR /&gt;Then we can check for block on the ASA, however your ACL applied on the OUTSIDE interface allow all traffic. (These is not consider secure)&lt;BR /&gt;&lt;BR /&gt;I hope this helps you.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;### RATE ALL HELPFUL RESPONSES ###</description>
      <pubDate>Wed, 09 Oct 2019 11:01:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937815#M26842</guid>
      <dc:creator>bhargavdesai</dc:creator>
      <dc:date>2019-10-09T11:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: DMZ server access problem</title>
      <link>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937855#M26849</link>
      <description>&lt;P&gt;As per security policy, internet are not allowed in Campus network. Every Morning , We will connect Anti-Virus (124.124.124.2) server to internet and download latest update file. Then Anti-Virus server should be connect to Campus_Router, and all endpoint system are automatically updated.&lt;/P&gt;&lt;P&gt;124.124.124.2 = Anti-Virus Server for latest package download and DMZ server 172.16.1.100 is Anti-Virus server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;**Anti-Virus Update Server 124.124.124.2 gateway is 124.124.124.1 (which is Campus Router IP)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;** Router 1841 just configured interface and&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Router ospf 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Network 124.124.124.0 255.255.255.0 area 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; Network 123.123.123.0 255.255.255.0 area 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;***&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Below detail will be share ASAP&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can you post "Show ip route" on the Router?&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Output of the packet tracer "packet-tracer input OUTSIDE icmp 124.124.124.2 8 0 172.16.1.100 detailed&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 12:26:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dmz-server-access-problem/m-p/3937855#M26849</guid>
      <dc:creator>dinchavan</dc:creator>
      <dc:date>2019-10-09T12:26:29Z</dc:date>
    </item>
  </channel>
</rss>

