SERVERS ON DMZ

Hello all,
I have a cisco asa 5545 on which the DMZ port is connected to the 2960 switch.Also i have two servers connected to the L2 switch which needs to be routed to Internet.
My question is can I make these two servers access the  internet through the single dmz port? Also these servers are connected to the switch on the ame vlan and the switch in turn to the dmz port of the firewall.
Thanks

Yes, just give them an IP from the subnet used for that vlan and use the dmz interface on the ASA as their default gateway.
Then depending on the access you need setup the NAT statements and the acl rules.
If you want external access you will need static NAT entries and allow that the traffic in an acl applied inbound to your outside interface.
If you just want the servers to be able to go out to the internet then you need a dynamic NAT statement and no need for an acl.
Jon

Similar Messages

  • Exchange servers in DMZ zone

    is it's right practice whether all exchange 2010 role servers in Dmz zone??
    or need to place only cas server in DMZ ZOne??

    Hello,
    It is required to place at least one writable Domain Controller with Global Catalog in every Ad site where Exchange servers are going to be deployed.
    Hope it helps,
    Adam
    www.codetwo.com
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
    find the answer faster.

  • How to manage VM servers in DMZ through NAT proxy?

    Dear all,
    We need to build some VM servers in DMZ network. And the OVM Manager is located in trust zone (behind DMZ). OVM manager can connect to the DMZ vm servers through NAT proxy. But, there are some errors after I have added the servers.
    In fact, there is no management network for OVM manager. So, I seem no workaround.
    Have you any idea about this deployment?
    Mike

    mtktang wrote:
    We need to build some VM servers in DMZ network. And the OVM Manager is located in trust zone (behind DMZ). OVM manager can connect to the DMZ vm servers through NAT proxy. But, there are some errors after I have added the servers. We do not support Oracle VM Server via NAT, because the Servers get the IP address of the Manager to connect to (and not the NAT'd address). So the API python binding download and notifications will fail. It is very unlikely that this would work.

  • Manage servers in DMZ and IBCM with the same MP/SUP/DP in DMZ

    Hi all, 
    I already asked a similar question on this forum about a month ago. I got some amswers but couldn't make it work and I still need some extra help.
    I use SCCM 2012 R2 with CU3, I only have one Primary site installed in my internal domain and a management point in my DMZ domain (different forests, no trust) that serves internet clients.
    I also want this DMZ MP to manage the intranet clients in DMZ (Web servers...) and I can't make it work. 
    I thought I could take advantage of the registry AllowedMPs offered by the CU3 because my DMZ clients are not allowed to communicate with the internal primary site on 80/443.
    I would like to avoid using the CCMALWAYSINF switch during the SCCM Client installation and to not treat my servers as internet clients. It works but I don't want the DMZ clients to use windows update to download the updates.
    Thanks again for your help.

    Hello, 
    Peter, thanks for your quick answer.
    1. I have a client certificate and it works because i was able to connect my DMZ server to the MP as an Internet client.
    2. I created the certificated with both names (Internet and Intranet), I used the alernative names filed.
    3. The MP and DP allow Intranet and Internet connnection.
    Here is the other thread I created a while ago, so you can have all the information
    https://social.technet.microsoft.com/Forums/en-US/ce18386b-8306-48d3-a27f-59fa2ee3a4fa/wrong-mp-assignement-for-clients-in-dmz?forum=configmanagergeneral#09a5ca7d-e626-4cbf-9f00-e8ef2ab745c9

  • ACE: load balancing servers using DMZ ports on FWSM

    devices; (2 core with the ff config)
    6500
    fwsm
    idsm
    msfc
    SETUP;
    Servers are connected to the dmzs on the core
    REQUIREMENT;
    to load balance the servers
    QUESTION;
    Using the ACE module, is it possibe to load balance the servers which are connected to the port which is configured as DMZ?
    Thanks

    does not matter where the servers are connected.
    However, be aware that the flows from client to server needs to go through the loadbalancer BUT also the flows server to client.
    So, you should be careful where you attach the ACE module.
    The easier would be to attach to the DMZ as well between the FW and the servers.
    Gilles.

  • Why servers in DMZ have 2 different IP addresses?

    I notice that all of my company's unix servers in the DMZ have 2 IP addresses.
    Could you expalin why?
    Thanks! Points will be given.

    Hi Laura,
    DMZ is used as Security factor!
    In this you use the NAT protocol, which has an external IP adress and a internal IP address.
    The external IP address is available for pulbic and the internal for the System to work with but not known to pulbic for security reasons!
    For details on that :
    http://documents.made-it.com/sap-int.html
    SAP Web Dispatcher Pre-Authentication
    http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm
    Regards,
    Prem
    http://compnetworking.about.com/cs/networksecurity/g/bldef_dmz.htm

  • Cisco ASA 5505 DMZ Setup

    Hello,
    I am new to Cisco firewalls and am attempting to setup a DMZ on the firewall.
    I have managed to create the interface and vlan and ip address settings etc. But im a bit lost with the NAT settings and rules i need to create for it.
    I need to be able to do the following:
    - RDP access from inside network to the DMZ servers
    - Internet access for the DMZ
    I am also setting up Active Directory Federation and requirre HTTPS traffic from the following:
    - DMZ HTTPS to outside (Office 365 Services)
    - Outside HTTPS to DMZ (ADFS Servers on DMZ only)
    - DMZ HTTPS to inside (ADFS Servers Only)
    -  Inside HTTPS to DMZ (ADFS Servers Only)      
    Running Config:
    interface Vlan1
    nameif inside
    security-level 100
    ip address ccl-sua-asa 255.255.255.0
    ospf cost 10
    interface Vlan3
    no forward interface Vlan1
    nameif dmz
    security-level 50
    ip address 172.16.0.1 255.255.255.0
    interface Vlan100
    nameif outside
    security-level 0
    ip address 77.107.90.202 255.255.255.248
    ospf cost 10
    interface Ethernet0/0
    switchport access vlan 100
    speed 100
    duplex full
    interface Ethernet0/1
    description Connected to CCL-SUA-SW1 port 16
    interface Ethernet0/2
    switchport access vlan 3
    access-list inbound extended permit icmp any any
    access-list inbound extended permit tcp host 87.86.204.100 host 77.107.90.203 eq smtp
    access-list inbound remark Inbound ACT for Ruth Edmonds Only
    access-list inbound extended permit tcp any interface outside eq www
    access-list inbound extended permit tcp any interface outside eq 5022 inactive
    access-list inbound remark Inbound rules for OWA 30/06/09 MD
    access-list inbound extended permit tcp any host 77.107.90.203 eq https log
    access-list inbound remark Inbound access for LDAP and SMTP from mimecast 02/07/09 MD
    access-list inbound extended permit tcp object-group mimecast interface outside eq ldap
    access-list inbound extended permit tcp object-group mimecast host 77.107.90.203 eq smtp
    access-list inbound remark change request MET 56030 inbound POP3 for mimecast
    access-list inbound extended permit tcp object-group mimecast host 77.107.90.203 eq pop3
    access-list inbound remark Inbound rule for helpdesk 10/07/2012 ML
    access-list inbound extended permit tcp any host 77.107.90.205 eq https
    access-list inbound remark Inbound rule for survey 011012 ML
    access-list inbound extended permit tcp any host 77.107.90.205 eq www
    access-list inbound extended deny ip any any
    access-list nonat extended permit ip 192.168.40.0 255.255.255.0 192.168.245.0 255.255.255.0
    access-list nonat extended permit ip 192.168.40.0 255.255.255.0 192.168.252.0 255.255.252.0
    access-list vpn-met-bir extended permit ip 192.168.40.0 255.255.255.0 192.168.252.0 255.255.252.0
    access-list outbound extended permit ip object-group servers 192.168.255.0 255.255.255.0
    access-list outbound extended deny ip any 192.168.255.0 255.255.255.0
    access-list outbound extended permit ip 192.168.40.0 255.255.255.0 192.168.254.0 255.255.255.0
    access-list outbound extended deny udp any 192.168.255.0 255.255.255.0
    access-list outbound extended deny ip any 10.0.0.0 255.0.0.0
    access-list outbound extended deny ip any 192.168.0.0 255.255.0.0
    access-list outbound extended permit ip any any
    global (outside) 1 interface
    nat (inside) 0 access-list nonat
    nat (inside) 1 192.168.40.0 255.255.255.0
    nat (inside) 1 192.168.41.0 255.255.255.0
    nat (dmz) 1 172.16.0.0 255.255.255.0
    static (inside,outside) tcp interface 5022 192.168.41.1 ssh netmask 255.255.255.255
    static (outside,outside) tcp interface ssh 192.168.41.1 ssh netmask 255.255.255.255
    static (inside,outside) tcp interface www WEB www netmask 255.255.255.255
    static (inside,outside) tcp interface ldap FILESERVER ldap netmask 255.255.255.255
    static (inside,outside) 77.107.90.203 MAILSERVER netmask 255.255.255.255
    static (inside,outside) 77.107.90.205 helpdesk netmask 255.255.255.255
    static (dmz,outside) 77.107.90.206 172.16.0.7 netmask 255.255.255.255
    access-group outbound in interface inside
    access-group inbound in interface outside
    route outside 0.0.0.0 0.0.0.0 77.107.90.201 1
    route inside 192.168.41.0 255.255.255.0 ccl-sua-sw1 1
    Like i mentioned I have already setup the DMZ itself but its just the NAT and rules im struggling to get working
    Many Thanks
    James          

    Hi,
    If you have only a ASA5505 Base License then you can initiate/open connections from the DMZ to INSIDE
    You can confirm the License level with "show version" command. It should read at the end of the output.
    In the Base License you only have a restricted DMZ/3rd interface on the ASA. You can connect to it from anywhere BUT you have to limit it from connecting towards one of the other 2 intefaces. You have already done this with the command
    no forward interface Vlan1
    Which to my understanding is required to get the 3rd interface active when you only have Base License on ASA5505.
    OUTSIDE -> DMZ
    INSIDE -> DMZ
    Connection initiating should be possible.
    So it seems to me that you already have one problem that will limit connectivity and not just the NAT.
    You already seem to have the Default PAT configuration for DMZ Internet traffic.
    You dont have the NAT for DMZ <-> INSIDE traffic but as mentioned above it might already be limited by something else even though your configurations were fine.
    The corrent NAT configuration to enable that traffic would be to use
    static (inside,dmz) netmask
    Repeat for all
    EDIT: Naturally you would also need an ACL on the DMZ interface for DMZ -> INSIDE traffic since the INSIDE is of higher "security-level". But as soon as you add the ACL to the DMZ interface you would also have to use it to allow Internet bound traffic since the "security-level" looses its meaning after an ACL is attached to the interface.
    - Jouni

  • How Can i Use two Different Public IP Addresses no my DMZ with ASA Firewall.

    How To Using Two Different Public IP Address on My DMZ with ASA 5520
    Postado por jorge decimo decimo em 28/Jan/2013 5:51:28
    Hi everyone out there.
    can any one please help me regarding this situation that im looking for a solution
    My old range of public ip address are finished, i mean (the 41.x.x.0 range)
    So now i still need to have in my DMZ another two servers that will bring some new services.
    Remember that those two server, will need to be accessable both from inside and from outside users (Internet users) as well.
    So as i said, my old range of public ip address is finished and we asked the ISP to gives some additional public
    ip address to address the need of the two new servers on DMZ. and the ISP gave us the range of 197.216.1.24/29
    So my quation is, on reall time world (on the equipment) how can i Use two different public ip address on the same DMZ
    on Cisco ASA 5520 v8??
    How my configuration should look like?
    I was told about implementing static nat with Sub Interfaces on both Router and ASA interface
    Can someone please do give me a help with a practical config sample please. i can as well be reached at [email protected]
    attached is my network diagram for a better understanding
    I thank every body in advance
    Jorge

    Hi,
    So looking at your picture you have the original public IP address range configured on the OUTSIDE and its used for NAT for different servers behind the ASA firewall.
    Now you have gotten a new public IP address range from the ISP and want to get it into use.
    How do you want to use this IP address range? You want to configure the public IP addresses directly on the servers or NAT them at the ASA and have private IP addresses on the actual servers (like it seems to be for the current server)?
    To get the routing working naturally the only thing needed between your Router and Firewall would be to have a static route for the new public network range pointing towards your ASA OUTSIDE IP address. The routing between your Router and the ISP core could either be handled with Static Routing or Dynamic Routing.
    So you dont really need to change the interface configuration between the Router and ASA at all. You just need a Static route pointing the new public IP address towards the ASA outside IP address.
    Now when the routing is handled between the ISP - ISP/Your Router - Your Firewall, you can then consider how to use those IP addresses.
    Do you want to use the public IP addresses DIRECTLY on the HOSTS behind the firewall?This would require you to either configure a new physical interface with the new public IP address range OR create a new subinterface with the new public IP addresses range AND then configure the LAN devices correspondingly to the chosen method on the firewall
    Do you want to use the public IP addresses DIRECLTY on the ASA OUTSIDE as NAT IP addresses?This would require for you to only start configuring Static NAT for the new servers between the inside/dmz and outside interface of the ASA. The format would be no different from the previous NAT configuration other than for the different IP addresses ofcourse
    Of the above ways
    The first way is good because the actual hosts will have the public IP addresses. Therefore you wont run into problems with DNS when the LAN users are trying to access the server.
    The second way is the one requiring the least amount of configurations/changes on the ASA. In this case though you might run into problem with DNS (to which I refer above) as the server actually has a private IP address but the public DNS might reply to the LAN hosts with a public IP address and therefore connections from LAN could fail. This is because LAN users cant connect to the servers OUTSIDE NAT IP address (unless you NAT the server to public IP address towards LAN also)
    Hopefully the above was helpfull. Naturally ask more specific questions and I'll answer them. Hopefully I didnt miss something. But please ask more
    I'm currently at Cisco Live! 2013 London so in the "worst case" I might be able to answer on the weekend at earliest.
    - Jouni

  • ZBFW - dmz-zone to in-zone access

    Hi IOSers,
    I have a Cisco 2901 which terminates a Class C address pool.
    I have split the Class C address pool into 3 sub-nets and 2 zones and created a non-addressable pool (private pool):
    dmz-zone : x.x.x.0 TO x.x.x.127 (x.x.x.0/25)
    in-zone: x.x.x.128 TO x.x.x.159 (x.x.x.128/27) & x.x.x.160 TO x.x.x.191 (x.x.x.160/27)
    private-zone: 192.168.x.0 TO 192.168.x.255 (192.168.x.0/24)
    I have configured private-zone NAT to use address pool x.x.x.161 TO x.x.x.189 within the in-zone.
    Within the:
    dmz-zone - are servers for : DNS, Syslog, SIP & HTTP/HTTPS
    in-zone - is a SMTP mail server which is behind VPN Gateway/NAT, TomCat (Application Server) and PostgreSQL Server
    private-zone - is where all standard users are operating from and they can access the SIP & HTTP/HTTPS servers within dmz-zone
    My problem is that I cannot seem to configure the ZBFW to allow the dmz-zone HTTP/HTTP server to redirect to in-zone TomCat server.
    I do not want to make the TomCat server generally visible and am instead using the Apache proxy/ajp13 to connect from dmz-zone server to in-zone server.
    However I cannot seem to get anything (including icmp) to work from dmz-zone to in-zone.
    I have Policy:
    POLICY-DMZ-IN (dmz-zone to in-zone) which has:
    any any udp/tcp inspect
    any any icmp inspect
    unmatched traffic DROP/LOG
    But I still cannot get anything from dmz-zone to in-zone...
    Can anyone please advise...
    Could the POLICY-DMZ-IN be being overridden by other dmz-zone to out-zone policies?
    I think I am making a basically incorrect assumption somewhere ...
    NOTE: I have routing rules for each of various sub-nets and all out-zone to dmz-zone, out-zone to in-zone and private-zone to out-zone, in-zone and dmz-zone routing works ok, so it appears problem is with ZBFW not routing table.
    Thank for any expertise you can bring to help resolve this.
    Regards,
    Zebity.

    Hi Karthikeyan,
    thank you for offering to look at this, I do all my configuration using CCP, which is a lot easier than pawing over IOS commands.
    I have dumped out the config, but as it is hard to pull out the partiular part of the config, so find following screen snap & config:
    The areas where I think there are problems are with "self" zone items (can I get rid of self zone case completely, with exception of blocking any external (DSL) access to self?)
    and the dmz-zone to in-zone and in-zone to dmz-zone configs.
    Building configuration...
    Current configuration : 32292 bytes
    ! Last configuration change at 00:16:54 UTC Mon Jun 11 2012 by admin
    ! NVRAM config last updated at 07:37:35 UTC Sun Jun 10 2012 by admin
    version 15.1
    no service pad
    service tcp-keepalives-in
    service tcp-keepalives-out
    service timestamps debug datetime msec localtime show-timezone
    service timestamps log datetime msec localtime show-timezone
    service password-encryption
    service sequence-numbers
    hostname big
    boot-start-marker
    boot-end-marker
    security authentication failure rate 3 log
    security passwords min-length 6
    logging buffered 51200 informational
    enable secret 5 XXXXXXXXXXXXXXXXXXXXXXXXXXX
    no aaa new-model
    no ipv6 cef
    no ip source-route
    ip cef
    ip dhcp excluded-address 168.192.200.1 168.192.200.99
    ip dhcp excluded-address 168.192.200.126 168.192.200.254
    ip dhcp excluded-address 200.200.200.1 200.200.200.79
    ip dhcp excluded-address 200.200.200.91 200.200.200.126
    ip dhcp pool PRIVATE-POOL-1
       import all
       network 168.192.200.0 255.255.255.0
       domain-name in.froghop.com
       dns-server 200.200.200.20 200.200.200.4
       default-router 168.192.200.1
    ip dhcp pool FROGHOP-POOL-2
       import all
       network 200.200.200.0 255.255.255.128
       domain-name froghop.com
       dns-server 200.200.200.20 200.200.200.4
       default-router 200.200.200.1
    no ip bootp server
    ip domain name froghop.com
    ip name-server 200.200.200.4
    ip name-server 200.200.200.20
    ip inspect log drop-pkt
    ip inspect audit-trail
    ip inspect name CCP_MEDIUM appfw CCP_MEDIUM
    ip inspect name CCP_MEDIUM dns
    ip inspect name CCP_MEDIUM ftp
    ip inspect name CCP_MEDIUM h323
    ip inspect name CCP_MEDIUM sip
    ip inspect name CCP_MEDIUM https
    ip inspect name CCP_MEDIUM icmp
    ip inspect name CCP_MEDIUM imap reset
    ip inspect name CCP_MEDIUM pop3 reset
    ip inspect name CCP_MEDIUM netshow
    ip inspect name CCP_MEDIUM rcmd
    ip inspect name CCP_MEDIUM realaudio
    ip inspect name CCP_MEDIUM rtsp
    ip inspect name CCP_MEDIUM esmtp
    ip inspect name CCP_MEDIUM sqlnet
    ip inspect name CCP_MEDIUM streamworks
    ip inspect name CCP_MEDIUM tftp
    ip inspect name CCP_MEDIUM tcp
    ip inspect name CCP_MEDIUM udp
    ip inspect name CCP_MEDIUM vdolive
    ip inspect name dmzinspect tcp
    ip inspect name dmzinspect udp
    appfw policy-name CCP_MEDIUM
      application im aol
        service default action allow alarm
        service text-chat action allow alarm
        server permit name login.oscar.aol.com
        server permit name toc.oscar.aol.com
        server permit name oam-d09a.blue.aol.com
        audit-trail on
      application im msn
        service default action allow alarm
        service text-chat action allow alarm
        server permit name messenger.hotmail.com
        server permit name gateway.messenger.hotmail.com
        server permit name webmessenger.msn.com
        audit-trail on
      application http
        strict-http action allow alarm
        port-misuse im action reset alarm
        port-misuse p2p action reset alarm
        port-misuse tunneling action allow alarm
      application im yahoo
        service default action allow alarm
        service text-chat action allow alarm
        server permit name scs.msg.yahoo.com
        server permit name scsa.msg.yahoo.com
        server permit name scsb.msg.yahoo.com
        server permit name scsc.msg.yahoo.com
        server permit name scsd.msg.yahoo.com
        server permit name cs16.msg.dcn.yahoo.com
        server permit name cs19.msg.dcn.yahoo.com
        server permit name cs42.msg.dcn.yahoo.com
        server permit name cs53.msg.dcn.yahoo.com
        server permit name cs54.msg.dcn.yahoo.com
        server permit name ads1.vip.scd.yahoo.com
        server permit name radio1.launch.vip.dal.yahoo.com
        server permit name in1.msg.vip.re2.yahoo.com
        server permit name data1.my.vip.sc5.yahoo.com
        server permit name address1.pim.vip.mud.yahoo.com
        server permit name edit.messenger.yahoo.com
        server permit name messenger.yahoo.com
        server permit name http.pager.yahoo.com
        server permit name privacy.yahoo.com
        server permit name csa.yahoo.com
        server permit name csb.yahoo.com
        server permit name csc.yahoo.com
        audit-trail on
    multilink bundle-name authenticated
    parameter-map type inspect global
    log dropped-packets enable
    parameter-map type protocol-info yahoo-servers
    server name scs.msg.yahoo.com
    server name scsa.msg.yahoo.com
    server name scsb.msg.yahoo.com
    server name scsc.msg.yahoo.com
    server name scsd.msg.yahoo.com
    server name cs16.msg.dcn.yahoo.com
    server name cs19.msg.dcn.yahoo.com
    server name cs42.msg.dcn.yahoo.com
    server name cs53.msg.dcn.yahoo.com
    server name cs54.msg.dcn.yahoo.com
    server name ads1.vip.scd.yahoo.com
    server name radio1.launch.vip.dal.yahoo.com
    server name in1.msg.vip.re2.yahoo.com
    server name data1.my.vip.sc5.yahoo.com
    server name address1.pim.vip.mud.yahoo.com
    server name edit.messenger.yahoo.com
    server name messenger.yahoo.com
    server name http.pager.yahoo.com
    server name privacy.yahoo.com
    server name csa.yahoo.com
    server name csb.yahoo.com
    server name csc.yahoo.com
    parameter-map type protocol-info aol-servers
    server name login.oscar.aol.com
    server name toc.oscar.aol.com
    server name oam-d09a.blue.aol.com
    parameter-map type protocol-info msn-servers
    server name messenger.hotmail.com
    server name gateway.messenger.hotmail.com
    server name webmessenger.msn.com
    crypto pki token default removal timeout 0
    crypto pki trustpoint TP-self-signed-2085601892
    enrollment selfsigned
    subject-name cn=IOS-Self-Signed-Certificate-2085601892
    revocation-check none
    crypto pki certificate chain TP-self-signed-2085601892
    certificate self-signed 01
      XXXXXXXX 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
      31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
      4A6B4C93 CEE0C972 CEA5A38E 3C041EAD 803F43B2 DD121173 4302DC1E XXXXXXXX
      4F5E79FE 8C76B0EC BC5DD668 69BE1A
                quit
    license udi pid CISCO2901/K9 sn FTXXXXXXXXXX
    hw-module pvdm 0/0
    username admin privilege 15 secret 5 XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    redundancy
    ip tcp synwait-time 10
    no ip ftp passive
    class-map type inspect match-any OPEN-TRAFFIC-OUT-190
    match access-group name OPEN-TRAFFIC-OUT-190
    class-map type inspect match-any SMTPS-TRAFFIC-IN
    match access-group name SMTPS-IN
    class-map type inspect match-all NAT-POOL-TCP-TRAFFIC-OUT
    match access-group name NAT-POOL-TRAFFIC-OUT
    match protocol tcp
    class-map type inspect imap match-any ccp-app-imap
    match  invalid-command
    class-map type inspect match-any ccp-cls-protocol-p2p
    match protocol edonkey signature
    match protocol gnutella signature
    match protocol kazaa2 signature
    match protocol fasttrack signature
    match protocol bittorrent signature
    class-map type inspect match-all NAT-POOL-UDP-TRAFFIC-OUT
    match access-group name NAT-POOL-TRAFFIC-OUT
    match protocol udp
    class-map type inspect match-all SELF-DNS-OUT
    match access-group name SELF-DNS-OUT
    match protocol dns
    class-map type inspect match-any SMTP-PROTOCOL
    match protocol smtp
    class-map type inspect match-all ccp-cls-POLICY-DMZ-OUT-1
    match class-map SMTP-PROTOCOL
    match access-group name DMZ-MAIL-OUT
    class-map type inspect match-any ccp-skinny-inspect
    match protocol skinny
    class-map type inspect match-any SIP-PROTOCOLS
    match protocol sip
    match protocol sip-tls
    class-map type inspect match-all ccp-cls-POLICY-DMZ-OUT-2
    match class-map SIP-PROTOCOLS
    match access-group name DMS-SIP-TRAFFIC
    class-map type inspect match-any OPEN-TRAFFIC-OUT-140
    match access-group name OPEN-TRAFFIC-OUT-140
    class-map type inspect match-any ccp-cls-insp-traffic
    match protocol pptp
    match protocol dns
    match protocol ftp
    match protocol https
    match protocol imap
    match protocol pop3
    match protocol netshow
    match protocol shell
    match protocol realmedia
    match protocol rtsp
    match protocol smtp
    match protocol streamworks
    match protocol tftp
    match protocol vdolive
    match protocol tcp
    match protocol udp
    class-map type inspect match-all ccp-insp-traffic
    match class-map ccp-cls-insp-traffic
    class-map type inspect gnutella match-any ccp-app-gnutella
    match  file-transfer
    class-map type inspect match-any OPENDIR-PROTOCOLS
    match protocol kerberos
    match protocol ldap
    match protocol ldaps
    match protocol ldap-admin
    class-map type inspect ymsgr match-any ccp-app-yahoo-otherservices
    match  service any
    match  service text-chat
    class-map type inspect msnmsgr match-any ccp-app-msn-otherservices
    match  service any
    class-map type inspect match-any SYSLOG-PROTOCOL
    match protocol syslog
    class-map type inspect match-any ICMP-PROTOCOLS
    match protocol icmp
    class-map type inspect match-all SELF-ICMP
    match access-group name SELF-ICMP-TRAFFIC
    match class-map ICMP-PROTOCOLS
    class-map type inspect match-any DMZ-DNS
    match protocol dns
    class-map type inspect match-all OPENDIR-OUT
    match class-map OPENDIR-PROTOCOLS
    match access-group name OPENDIR-TRAFFIC
    class-map type inspect match-all SMTPS-TRAFFIC
    match class-map SMTPS-TRAFFIC-IN
    match protocol tcp
    class-map type inspect match-any TRUSTED-HOSTS
    match access-group name TRUSTED-HOSTS
    match protocol udp
    match protocol tcp
    match protocol icmp
    class-map type inspect match-any TRANSPORT-PROTOCOLS
    match protocol tcp
    match protocol udp
    class-map type inspect match-any ccp-h323nxg-inspect
    match protocol h323-nxg
    class-map type inspect match-any ccp-cls-icmp-access
    match protocol icmp
    match protocol tcp
    match protocol udp
    class-map type inspect match-any ccp-cls-protocol-im
    match protocol ymsgr yahoo-servers
    match protocol msnmsgr msn-servers
    match protocol aol aol-servers
    class-map type inspect aol match-any ccp-app-aol-otherservices
    match  service any
    class-map match-any sdm_p2p_kazaa
    match protocol fasttrack
    match protocol kazaa2
    class-map type inspect match-any WEB-PROTOCOLS
    match protocol http
    match protocol https
    class-map type inspect match-all ccp-protocol-pop3
    match protocol pop3
    class-map type inspect match-any ccp-h225ras-inspect
    match protocol h225ras
    class-map match-any sdm_p2p_edonkey
    match protocol edonkey
    class-map type inspect match-any SELF-DNS-IN
    match access-group name SELF-DNS-IN
    match protocol dns
    class-map match-any sdm_p2p_gnutella
    match protocol gnutella
    class-map type inspect match-any ccp-h323annexe-inspect
    match protocol h323-annexe
    class-map type inspect match-any OPEN-TRAFFIC-IN-140
    match access-group name OPEN-TRAFFIC-IN-140
    class-map type inspect match-all SYSLOG-IN-DMZ
    match access-group name SYSLOG-TRAFFIC
    match class-map SYSLOG-PROTOCOL
    class-map type inspect pop3 match-any ccp-app-pop3
    match  invalid-command
    class-map match-any sdm_p2p_bittorrent
    match protocol bittorrent
    class-map type inspect kazaa2 match-any ccp-app-kazaa2
    match  file-transfer
    class-map type inspect match-all ccp-protocol-p2p
    match class-map ccp-cls-protocol-p2p
    class-map type inspect match-all SDM_GRE
    match access-group name SDM_GRE
    class-map type inspect match-any ccp-h323-inspect
    match protocol h323
    class-map type inspect msnmsgr match-any ccp-app-msn
    match  service text-chat
    class-map type inspect ymsgr match-any ccp-app-yahoo
    match  service text-chat
    match  service any
    class-map type inspect match-all ccp-cls-ccp-pol-outToIn-1
    match class-map SMTP-PROTOCOL
    match access-group name SMTP-TRAFFIC
    class-map type inspect match-any DNS-PROTOCOL
    match protocol dns
    class-map type inspect match-all ccp-protocol-im
    match class-map ccp-cls-protocol-im
    class-map type inspect match-all ccp-cls-ccp-pol-outToIn-2
    match class-map ICMP-PROTOCOLS
    match access-group name IN-ZONE-ICMP
    class-map type inspect match-all ccp-invalid-src
    match access-group 100
    class-map type inspect match-all ccp-icmp-access
    match class-map ccp-cls-icmp-access
    class-map type inspect match-any ACCESS-PROTOCOLS
    match protocol icmp
    match protocol tcp
    match protocol udp
    class-map type inspect match-all ccp-cls-ccp-pol-outToIn-3
    match class-map ACCESS-PROTOCOLS
    match access-group name DMZ-ZONE-TRAFFIC
    class-map type inspect http match-any ccp-app-httpmethods
    match  request method bcopy
    match  request method bdelete
    match  request method bmove
    match  request method bpropfind
    match  request method bproppatch
    match  request method connect
    match  request method copy
    match  request method delete
    match  request method edit
    match  request method getattribute
    match  request method getattributenames
    match  request method getproperties
    match  request method index
    match  request method lock
    match  request method mkcol
    match  request method mkdir
    match  request method move
    match  request method notify
    match  request method options
    match  request method poll
    match  request method propfind
    match  request method proppatch
    match  request method put
    match  request method revadd
    match  request method revlabel
    match  request method revlog
    match  request method revnum
    match  request method save
    match  request method search
    match  request method setattribute
    match  request method startrev
    match  request method stoprev
    match  request method subscribe
    match  request method trace
    match  request method unedit
    match  request method unlock
    match  request method unsubscribe
    class-map type inspect edonkey match-any ccp-app-edonkey
    match  file-transfer
    match  text-chat
    match  search-file-name
    class-map type inspect match-any ccp-sip-inspect
    match protocol sip
    class-map type inspect match-all PUSH-NOTIFICATIONS
    match access-group name PUSH-NOTIFICATIONS
    match protocol tcp
    class-map type inspect http match-any ccp-http-blockparam
    match  request port-misuse im
    match  request port-misuse p2p
    match  req-resp protocol-violation
    class-map type inspect edonkey match-any ccp-app-edonkeydownload
    match  file-transfer
    class-map type inspect match-all DEST-DNS
    match access-group name DEST-DNS
    match class-map DNS-PROTOCOL
    class-map type inspect aol match-any ccp-app-aol
    match  service text-chat
    class-map type inspect match-all ccp-protocol-imap
    match protocol imap
    class-map type inspect edonkey match-any ccp-app-edonkeychat
    match  search-file-name
    match  text-chat
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-1
    match class-map SYSLOG-PROTOCOL
    match access-group name DMZ-SYSLOG
    class-map type inspect match-any FTP-PROTOCOL
    match protocol ftp
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-2
    match class-map ICMP-PROTOCOLS
    match access-group name DMZ-ICMP
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-3
    match class-map WEB-PROTOCOLS
    match access-group name DMZ-WEB
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-4
    match class-map SIP-PROTOCOLS
    match access-group name DMZ-SIP
    class-map type inspect match-any TIME-PROTOCOLS
    match protocol ntp
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-5
    match class-map DMZ-DNS
    match access-group name DMZ-DNS-TRAFFIC
    class-map type inspect http match-any ccp-http-allowparam
    match  request port-misuse tunneling
    class-map type inspect fasttrack match-any ccp-app-fasttrack
    match  file-transfer
    class-map type inspect match-all ccp-protocol-http
    match protocol http
    class-map type inspect match-all ccp-cls-ccp-permit-dmzservice-6
    match class-map ACCESS-PROTOCOLS
    match access-group name IN-ZONE-TRAFFIC
    policy-map type inspect ccp-permit-icmpreply
    class type inspect ccp-icmp-access
      inspect
    class class-default
      pass
    policy-map type inspect POLICY-PRIVATE-TRANSIT
    class type inspect ACCESS-PROTOCOLS
      pass log
    class class-default
      drop
    policy-map type inspect p2p ccp-action-app-p2p
    class type inspect edonkey ccp-app-edonkeychat
      log
      allow
    class type inspect edonkey ccp-app-edonkeydownload
      log
      allow
    class type inspect fasttrack ccp-app-fasttrack
      log
      allow
    class type inspect gnutella ccp-app-gnutella
      log
      allow
    class type inspect kazaa2 ccp-app-kazaa2
      log
      allow
    policy-map type inspect POLICY-IN-SELF
    class type inspect ICMP-PROTOCOLS
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-SELF-IN
    class type inspect OPEN-TRAFFIC-OUT-190
      pass
    class type inspect ccp-icmp-access
      inspect
    class class-default
      drop
    policy-map type inspect POLICY-DMZ-OUT
    class type inspect TIME-PROTOCOLS
      inspect
    class type inspect WEB-PROTOCOLS
      inspect
    class type inspect FTP-PROTOCOL
      inspect
    class type inspect ccp-cls-POLICY-DMZ-OUT-2
      inspect
    class type inspect ccp-cls-POLICY-DMZ-OUT-1
      inspect
    class type inspect PUSH-NOTIFICATIONS
      inspect
    class type inspect DEST-DNS
      inspect
    class class-default
      drop log
    policy-map type inspect im ccp-action-app-im
    class type inspect aol ccp-app-aol
      log
      allow
    class type inspect msnmsgr ccp-app-msn
      log
      allow
    class type inspect ymsgr ccp-app-yahoo
      log
      allow
    class type inspect aol ccp-app-aol-otherservices
      log
      reset
    class type inspect msnmsgr ccp-app-msn-otherservices
      log
      reset
    class type inspect ymsgr ccp-app-yahoo-otherservices
      log
      allow
    policy-map type inspect http ccp-action-app-http
    class type inspect http ccp-http-blockparam
      log
      allow
    class type inspect http ccp-app-httpmethods
      log
      allow
    class type inspect http ccp-http-allowparam
      log
      allow
    policy-map type inspect imap ccp-action-imap
    class type inspect imap ccp-app-imap
      log
    policy-map type inspect pop3 ccp-action-pop3
    class type inspect pop3 ccp-app-pop3
      log
    policy-map type inspect ccp-inspect
    class type inspect ccp-invalid-src
      drop log
    class type inspect ICMP-PROTOCOLS
      inspect
    class type inspect ccp-protocol-http
      inspect
      service-policy http ccp-action-app-http
    class type inspect ccp-protocol-imap
      inspect
      service-policy imap ccp-action-imap
    class type inspect ccp-protocol-pop3
      inspect
      service-policy pop3 ccp-action-pop3
    class type inspect ccp-protocol-p2p
      inspect
      service-policy p2p ccp-action-app-p2p
    class type inspect ccp-protocol-im
      inspect
      service-policy im ccp-action-app-im
    class type inspect ccp-sip-inspect
      inspect
    class type inspect ccp-h323-inspect
      inspect
    class type inspect ccp-h323annexe-inspect
      inspect
    class type inspect ccp-h225ras-inspect
      inspect
    class type inspect ccp-h323nxg-inspect
      inspect
    class type inspect ccp-skinny-inspect
      inspect
    class type inspect ccp-insp-traffic
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-PRIVATE-IN-DMZ
    class type inspect TRANSPORT-PROTOCOLS
      inspect
    class type inspect ICMP-PROTOCOLS
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-IN-OUT
    class type inspect OPEN-TRAFFIC-OUT-140
      pass log
    class type inspect WEB-PROTOCOLS
      inspect
    class type inspect OPENDIR-OUT
      inspect
    class type inspect DEST-DNS
      inspect
    class type inspect PUSH-NOTIFICATIONS
      inspect
    class class-default
      drop log
    policy-map type inspect ccp-permit
    class class-default
      drop
    policy-map type inspect POLICY-DMZ-SELF
    class type inspect ICMP-PROTOCOLS
      inspect
    class type inspect TRANSPORT-PROTOCOLS
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-SELF-OUT
    class type inspect SELF-DNS-OUT
      pass
    class type inspect TIME-PROTOCOLS
      pass
    class type inspect NAT-POOL-UDP-TRAFFIC-OUT
      inspect
    class type inspect NAT-POOL-TCP-TRAFFIC-OUT
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-OUT-SELF
    class type inspect SELF-DNS-IN
      pass
    class type inspect TIME-PROTOCOLS
      pass
    class type inspect SELF-ICMP
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-IN-DMZ
    class type inspect SYSLOG-IN-DMZ
      pass
    class type inspect ICMP-PROTOCOLS
      inspect
    class class-default
      drop log
    policy-map type inspect POLICY-DMZ-IN
    class type inspect TRANSPORT-PROTOCOLS
      inspect
    class type inspect ICMP-PROTOCOLS
      inspect
    class class-default
      drop log
    policy-map type inspect ccp-permit-dmzservice
    class type inspect ccp-cls-ccp-permit-dmzservice-4
      inspect
    class type inspect ccp-cls-ccp-permit-dmzservice-1
      pass
    class type inspect ccp-cls-ccp-permit-dmzservice-3
      inspect
    class type inspect ccp-cls-ccp-permit-dmzservice-5
      inspect
    class type inspect ccp-cls-ccp-permit-dmzservice-2
      inspect
    class class-default
      drop log
    policy-map type inspect ccp-pol-outToIn
    class type inspect OPEN-TRAFFIC-IN-140
      pass
    class type inspect ccp-cls-ccp-pol-outToIn-1
      inspect
    class type inspect ccp-cls-ccp-pol-outToIn-2
      inspect
    class type inspect SMTPS-TRAFFIC
      inspect
    class type inspect SMTPS-TRAFFIC-IN
      pass log
    class class-default
      drop log
    policy-map sdmappfwp2p_CCP_MEDIUM
    class sdm_p2p_edonkey
    class sdm_p2p_gnutella
    class sdm_p2p_kazaa
    class sdm_p2p_bittorrent
    zone security dmz-zone
    zone security in-zone
    zone security out-zone
    zone security PRIVATE-ZONE
    zone security PRIVATE-IN
    zone-pair security ccp-zp-out-dmz source out-zone destination dmz-zone
    service-policy type inspect ccp-permit-dmzservice
    zone-pair security ccp-zp-in-out source in-zone destination out-zone
    service-policy type inspect POLICY-IN-OUT
    zone-pair security ccp-zp-out-zone-To-in-zone source out-zone destination in-zone
    service-policy type inspect ccp-pol-outToIn
    zone-pair security ZP-DMZ-IN source dmz-zone destination in-zone
    service-policy type inspect POLICY-DMZ-IN
    zone-pair security ZP-DMZ-OUT source dmz-zone destination out-zone
    service-policy type inspect POLICY-DMZ-OUT
    zone-pair security ZP-IN-DMZ source in-zone destination dmz-zone
    service-policy type inspect POLICY-IN-DMZ
    zone-pair security ZP-OUT-SELF source out-zone destination self
    service-policy type inspect POLICY-OUT-SELF
    zone-pair security ZP-SELF-OUT source self destination out-zone
    service-policy type inspect POLICY-SELF-OUT
    zone-pair security ZP-PRIVATE-OUT source PRIVATE-ZONE destination out-zone
    service-policy type inspect ccp-inspect
    zone-pair security ZP-PRIVATE-IN source PRIVATE-ZONE destination in-zone
    service-policy type inspect POLICY-PRIVATE-IN-DMZ
    zone-pair security ZP-PRIVATE-DMZ source PRIVATE-ZONE destination dmz-zone
    service-policy type inspect POLICY-PRIVATE-IN-DMZ
    zone-pair security ZP-IN-SELF source in-zone destination self
    service-policy type inspect POLICY-IN-SELF
    zone-pair security ZP-SELF-IN source self destination in-zone
    service-policy type inspect POLICY-SELF-IN
    zone-pair security ZP-DMZ-SELF source dmz-zone destination self
    service-policy type inspect POLICY-DMZ-SELF
    crypto isakmp policy 1
    encr 3des
    authentication pre-share
    group 2
    crypto isakmp policy 10
    encr 3des
    authentication pre-share
    group 2
    interface Loopback0
    ip address 200.200.200.190 255.255.255.224
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    zone-member security in-zone
    interface Null0
    no ip unreachables
    interface GigabitEthernet0/0
    description $ETH-LAN$$FW_INSIDE$
    ip address 200.200.200.130 255.255.255.224
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip nbar protocol-discovery
    ip flow ingress
    ip nat outside
    ip virtual-reassembly in
    zone-member security in-zone
    duplex auto
    speed auto
    no mop enabled
    interface GigabitEthernet0/1
    description $ETH-LAN$$FW_INSIDE$
    ip address 168.192.200.1 255.255.255.0
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip nat inside
    ip virtual-reassembly in
    zone-member security PRIVATE-ZONE
    duplex auto
    speed auto
    no mop enabled
    interface FastEthernet0/2/0
    description $ETH-LAN$$FW_INSIDE$
    ip address 192.168.1.160 255.255.255.0
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip nat inside
    ip virtual-reassembly in
    zone-member security PRIVATE-ZONE
    duplex auto
    speed auto
    no mop enabled
    interface FastEthernet0/2/1
    no ip address
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    shutdown
    duplex auto
    speed auto
    no mop enabled
    interface ATM0/3/0
    no ip address
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    no atm ilmi-keepalive
    interface ATM0/3/0.1 point-to-point
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    pvc 8/35
      encapsulation aal5mux ppp dialer
      dialer pool-member 1
    interface GigabitEthernet0/0/0
    interface GigabitEthernet0/0/1
    interface GigabitEthernet0/0/2
    interface GigabitEthernet0/0/3
    interface Virtual-Template1 type serial
    description $FW_INSIDE$
    ip unnumbered Loopback0
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip nat outside
    ip virtual-reassembly in
    zone-member security in-zone
    interface Vlan1
    description $ETH-4ESG$$INTF-INFO-10/100/1000 Ethernet$$ETH-LAN$FW-DMZ$$FW_INSIDE$
    ip address 200.200.200.1 255.255.255.128
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip nbar protocol-discovery
    ip flow ingress
    ip flow egress
    ip nat outside
    ip virtual-reassembly in
    zone-member security dmz-zone
    interface Dialer0
    description $FW_OUTSIDE$
    ip address 210.210.210.154 255.255.255.0
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip flow ingress
    ip flow egress
    ip nat outside
    ip virtual-reassembly in
    zone-member security out-zone
    encapsulation ppp
    dialer pool 1
    dialer-group 1
    ppp authentication chap pap callin
    ppp chap hostname [email protected]
    ppp chap password 7 XXXXXXXXXXXXXXXX
    ppp pap sent-username [email protected] password 7 XXXXXXXXXXXX
    service-policy input sdmappfwp2p_CCP_MEDIUM
    service-policy output sdmappfwp2p_CCP_MEDIUM
    ip forward-protocol nd
    ip http server
    ip http authentication local
    ip http secure-server
    ip flow-top-talkers
    top 200
    sort-by bytes
    cache-timeout 500
    ip dns server
    ip nat pool NAT-POOL1 200.200.200.161 200.200.200.189 netmask 255.255.255.224
    ip nat inside source route-map SDM_RMAP_1 pool NAT-POOL1
    ip route 0.0.0.0 0.0.0.0 210.210.210.1
    ip route 10.210.210.0 255.255.255.0 192.168.1.1 permanent
    ip route 192.168.1.0 255.255.255.0 FastEthernet0/2/0 permanent
    ip route 168.192.200.0 255.255.255.0 GigabitEthernet0/1 permanent
    ip route 200.200.200.0 255.255.255.128 Vlan1 permanent
    ip route 200.200.200.128 255.255.255.224 GigabitEthernet0/0 permanent
    ip route 200.200.200.160 255.255.255.224 Loopback0 permanent
    ip access-list extended DEST-DNS
    remark CCP_ACL Category=1
    permit udp any any eq domain
    ip access-list extended DMS-SIP-TRAFFIC
    remark CCP_ACL Category=128
    permit ip host 200.200.200.30 any
    permit ip host 200.200.200.40 any
    ip access-list extended DMZ-DNS-TRAFFIC
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.20
    ip access-list extended DMZ-ICMP
    remark CCP_ACL Category=128
    permit ip any any
    ip access-list extended DMZ-MAIL-OUT
    remark CCP_ACL Category=128
    permit ip any host 230.211.70.60
    permit ip any host 230.250.90.137
    ip access-list extended DMZ-SIP
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.40
    permit ip any host 200.200.200.30
    ip access-list extended DMZ-SYSLOG
    remark CCP_ACL Category=128
    permit ip 230.211.70.0 0.0.0.255 host 200.200.200.32
    permit ip 200.200.200.128 0.0.0.127 host 200.200.200.32
    ip access-list extended DMZ-WEB
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.35
    permit ip any host 200.200.200.20
    ip access-list extended DMZ-ZONE-TRAFFIC
    remark CCP_ACL Category=128
    permit ip 200.200.200.0 0.0.0.128 any
    ip access-list extended ESP-TRAFFIC
    remark CCP_ACL Category=1
    permit esp any any
    ip access-list extended IN-ZONE-ICMP
    remark CCP_ACL Category=128
    permit ip any any
    ip access-list extended IN-ZONE-TRAFFIC
    remark CCP_ACL Category=128
    permit ip host 200.200.200.140 any
    ip access-list extended NAT-POOL-TRAFFIC-IN
    remark CCP_ACL Category=128
    permit ip any 0.0.0.0 255.255.255.224
    ip access-list extended NAT-POOL-TRAFFIC-OUT
    remark CCP_ACL Category=128
    permit ip 0.0.0.30 255.255.255.224 any
    ip access-list extended OPEN-TRAFFIC-IN-140
    remark CCP_ACL Category=1
    permit udp host 230.211.70.60 host 200.200.200.140 eq isakmp
    permit esp host 230.211.70.60 host 200.200.200.140
    permit ip host 230.211.70.10 host 200.200.200.140
    permit tcp host 230.211.70.35 host 200.200.200.140
    deny   ip host 230.211.70.60 host 200.200.200.140
    ip access-list extended OPEN-TRAFFIC-OUT-140
    remark CCP_ACL Category=1
    permit udp host 200.200.200.140 host 230.211.70.60 eq isakmp
    permit esp host 200.200.200.140 host 230.211.70.60
    permit ip host 200.200.200.140 host 230.211.70.10
    permit tcp host 200.200.200.140 host 230.211.70.35
    deny   ip host 200.200.200.140 host 230.211.70.60
    ip access-list extended OPENDIR-TRAFFIC
    remark CCP_ACL Category=128
    permit ip any host 230.211.70.10
    ip access-list extended PUSH-NOTIFICATIONS
    remark CCP_ACL Category=1
    permit tcp any any eq 5223
    ip access-list extended SDM_GRE
    remark CCP_ACL Category=1
    permit gre any any
    ip access-list extended SELF-DNS-IN
    remark CCP_ACL Category=1
    permit udp any eq domain any
    ip access-list extended SELF-DNS-OUT
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.20
    permit ip any host 200.200.200.4
    ip access-list extended SELF-ICMP-TRAFFIC
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.190
    ip access-list extended SMTP-TRAFFIC
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.140
    ip access-list extended SMTPS-IN
    remark CCP_ACL Category=1
    permit tcp any any eq 465
    permit tcp any any eq 587
    ip access-list extended SMTPS-OUT
    remark CCP_ACL Category=1
    permit tcp any eq 465 any
    permit tcp any eq 587 any
    ip access-list extended SYSLOG-TRAFFIC
    remark CCP_ACL Category=128
    permit ip any host 200.200.200.32
    ip access-list extended TRUSTED-HOSTS
    remark CCP_ACL Category=128
    permit ip host 230.211.70.35 any
    permit ip host 230.211.70.60 any
    logging 200.200.200.32
    access-list 1 remark CCP_ACL Category=2
    access-list 1 permit 168.192.200.0 0.0.0.255
    access-list 1 permit 192.168.1.0 0.0.0.255
    access-list 100 remark CCP_ACL Category=128
    access-list 100 permit ip host 255.255.255.255 any
    access-list 100 permit ip 127.0.0.0 0.255.255.255 any
    access-list 100 permit ip 210.210.210.0 0.0.0.255 any
    access-list 100 permit ip 200.200.200.0 0.0.0.255 any
    access-list 102 remark CCP_ACL Category=2
    access-list 102 permit ip 168.192.200.0 0.0.0.255 any
    access-list 102 permit ip 192.168.1.0 0.0.0.255 any
    dialer-list 1 protocol ip permit
    no cdp run
    route-map SDM_RMAP_1 permit 1
    match ip address 102
    control-plane
    banner login ^CThis device is propoerty of FROGHOP and all activity is logged.^C
    line con 0
    line aux 0
    line vty 0 4
    privilege level 15
    login local
    transport input telnet ssh
    line vty 5 15
    privilege level 15
    login local
    transport input telnet ssh
    scheduler allocate 20000 1000
    ntp update-calendar
    ntp server 192.189.54.17
    ntp server 192.189.54.33
    ntp server 203.161.12.165
    ntp server 130.102.2.123
    end
    Thanks in advance for any tips.
    Regards,
    John.

  • Server proxy - mandatory on Gateway Servers?

    Can anyone confirm on this? Whether we should have the
    server proxy enabled on the “Gateway Servers” as this act as proxy for other systems connecting through the gateway server..??
    SCOM 2012 SP1
    I don't see this is as a mandatory setting where we have this enabled in the Management servers..but there is no clear cut confirmation or answer on whther we should have this enabled againt the gateway servers. We have gateway
    servers in DMZ and in other regions.
    Since the MP which needs proxying – such as AD, cluster have agents which are spread across our gateway servers too..Just my thought of having it in gateway servers too…..but again ‘if Agent proxying’ is enabled on the agents
    then I think that should be fine and it doesn’t need the server proxying on the gateway servers…this is sort of confusing for me, sorry, can someone please confirm on this.
    Thanks,
    Nirmal

    Thanks Roger..
    That sounds like a convincing one..as you said gateway just pass through the data to the MS. And I also believe it is only required when gateway serve some special purpose - especially if it runs some workflows which requires agent proxying - like the
    gateway server itself is a cluster resource or hold a DC or exchange role which is a remote possibility...
    Thanks,
    Nirmal

  • SAP NW 7.0 AS JAVA Application Server Installation in DMZ : Win 2008 SR2

    Dear Experts,
    We are installing two AS JAVA application servers in DMZ (XYZ domain) and the central instance is running outside DMZ (ABC domain). While trying to give the profile path of the CI, in the application server installation, it says that the path cannot be found. We have opened the following ports 54200,54201,54204,54218,54230,3342,3641,3310,3610,8010,8011, and 25.  The installation inside DMZ is run with a user which is part of local administration group. The DB (SQL 2008R2)is running on a different host in a distributed setup.
    Could  someone please let us know if any other port needs to be open to allow communication between the central instance and application server?
    Help is appreciated.
    KP

    If FileSharing disabled, Firewal is open, unable to do ping test. How does the poor App server can access the Path from CI ?
    Please request your network team to open firewal between CI and APP server otherwise, even if you install you might get other below access problems
    1). user's in App server can't update CI
    2). Jobs in App server might run as expected.
    etc...

  • Real Servers not connected to ACE VLAN and Real Servers are clients accessing the VIP

    Hi,
    I have a very strange set up and need some help to get my config working
    I have a ASA firewall with three VLANs
    VLAN 1 = Internet
    VLAN 2 = DMZ
    VLAN 3 = Goes to ACE
    On the ACE I have four VLANs
    VLAN 3 = Goes to ASA
    VALN 4 = Web Server Tier
    VALN 5 = DB Tier
    VALN 6 = VIPs
    Our Application team have asked us to create a New VIP on the ACE with real servers in DMZ (Server A and Server B)
    And they have told us that the cleints accessing the VIP will be Server A and Server B
    I have always created VIPs with real servers directly connected to the ACE but not connected elsewhere.
    I belive I have a big challenge of opening ports on the firewall etc to get this set up working. Also, should i use some sort of NAT / SNAT? 
    Could anyone guide me on this setup please?
    Raj

    Hi Raj,
    First of all it is possible to add servers in ACE which are HOP away from ACE interfaces. Here servers are HOP away but there VIP is part of ACE interface subnet. The only need is that servers return traffic towards client should be passed through ACE (so that ACE can manitain states and chage the source IP of the reply packet from server IP to VIP on which client has requested the connection).
    When servers are HOP away and ACE do not come in path between server and client then we have to to do SNAT for intial client request. This configuration will force the return traffic from server to ACE (as server will NAT IP as client IP).
    In your case DMZ-VIP which is created for two real servers A and B, will be accesses by these servers only. So it is a situation of server accessing there own VIP. For this scenario to work we have to have SNAT (no matter whether servers are directly connected or HOP away). So best solution here is VIP in VLAN 3, Rserevrs for this VIP in DMZ, and SNAT client request, using free IP in VLAN 3.
    Also you have to open ports on firewall for both "real server Probes" and actual application ports, moreover policies modification on firewall for allowing traffic from DMZ to ACE VIP, DMZ to NAT IP and there vice versa traffic.

  • Public URL for Business Object servers

    What is preferred method to access BO by external clients?
    Here is our setup, 2 tomcat servers, 2 BO servers and F5 for load balancing
    I am thinking to put 2 tomcat servers in DMZ and open up the ports for BO servers in the firewall.
    I would like to know what all the options you guys have in your environments.

    Dennis,
    Since we have clustered BO servers (2 node), for example, one CMS in each server, do we need to open one port in the firewall which is 6400 and assign that port to both the CMS or we need to assign different ports for each CMS, like 6400 for 1st CMS and 6411 for 2nd CMS?

  • Manage SCCM 2012 clients in DMZ (OS Deploy, Windows updates) via DP/MP

    Hi,
    We ’d like to manage (=OS Deploy, Packages,Windows updates) Windows clients (Windows 2008/2012 R2 servers for now, about 20 of them) in a DMZ (= different domain).
    There is this article
    https://nikifoster.wordpress.com/2011/01/31/installing-configmgr-clients-on-servers-in-a-dmz/ which explains what to do … in 2011. Since then lots of things are changed I guess
    Before I dive in, I’d need to have an overview + do some administrative tasks (like asking for firewall accesses).
    Current setup DMZ:
    Our SCCM 2012 R2 server is on a Windows 2008 R2 OS
    Client communication is done via HTTP (not HTTPS)
    An extra physical Distribution point is setup (only DP, nothing more) in our current domain
    A new Windows 2012 server is setup in the DMZ which should host the DP and probably management point (since it should manage the clients over there)
    There are clients in DMZ that are currenlty managed by SCCM 2007 but 
    this server will be phased out, these client have:
    Correct sccm functionality
    Correct DNS resolution
    My steps/questions, please comment:
    Add the DMZ ip range to SCCM 2012 boundary as “DMZ”
    Add the network access account to be able to deploy as well clients as distribution point in DMZ
    In the DMZ accesses on firewall for server VLAN have to be asked
    When we have a distribution point and communication is “HTTP only” then http (port 80) from DMZ to sccm server should suffice, correct? Or are
     extra firewall openings needed for management point access/packages and windows updates sync?
    Now the sccm clients will be deployed to the servers in DMZ: deploy SCCM clients to hosts in DMZ, how this should be done: we connect a console to the SCCM-server in the DMZ then deploy the discovered clients?
    OS Deploy should be made available, but no dhcp is available in DMZ and it is not an option either, therefore we would boot from an ISO then enter an ip (or pre-enter it so there is already filled in an ip?). So tasksequences/deployments
    for servers in DMZ, where are they configured/deployed then? Via console access on DMZ management point or can we deploy on our domain SCCM management point (not in DMZ) and it will be synced to the DMZ management point? Not clear
    Selective sync of software to this distribution point (howto? not sure), we don’t need any Windows 8 software/drivers to be synced.
    Thanks for your input!
    J.
    Jan Hoedt

    No comment;
    I think you mean the client push installation account and the site system installation account;
    More ports are required, see site server > distribution point and distribution point > management point from the provided link;
    The console will always be connected to your primary site server. The client will be pushed from the primary site server and it will provide the initial files. The other files will be downloaded from the local distribution point;
    The task sequence deployment will be just like a normal taks sequence deployment. The only difference is the location of the server;
    Only the content that's distributed to the distribution point in the DMZ will be available on that distribution point.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Exchange 2013 server DMZ..... Bad idea!

    Hello and good day to all.
    I am doing an exchange 2013 lab (Novice), and in doing my research, I found that placing your server in a DMZ is a very bad idea.... Can so one please explain? and what would be the best practices in insuring that your exchange server is not attacked by
    any malicious user out there. 
    Regards 
    Matt

    Hi Matthew,
    Please consider reading this http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx
    unlike Exchange2003 all other versions higher than Exchange2003 doesn't support DMZ due to tight integration with Active Directory. Only you can install Edge servers in DMZ.
    Few ports are opened e.g 443,80 and 25 
    110 and 143 if using IMAP and POP (Assuming your have a firewall).
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Maybe you are looking for