06-15-2015 11:28 AM - edited 03-11-2019 11:07 PM
I have a CISCO ASA I currently have it NAT'd to allow FTP protocol access to my backup FTP server. This is fine until recently we've decided we want to utilize this in a network changeover for temporary internet access for our new DNS server/domain controller and the PC's that will be added to this new domain.
What do I need to do to get my workstations 192.168.0.x access to the internet without compromising my FTP NAT? Currently I cannot ping out via name, but I can ping by IP? Add via an access list? I think so. How?
Here is my configuration? Any ideas what I need?
Result of the command: "show running-config"
: Saved
:
ASA Version 8.2(5)
!
hostname ASA1
enable
passwd
names
!
interface Ethernet0/0
nameif External
security-level 0
ip address EXTERNALFIXED 255.255.255.0
!
interface Ethernet0/1
nameif Internal
security-level 100
ip address 192.168.X.INTERNAL 255.255.255.0
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
!
ftp mode passive
dns domain-lookup External
dns server-group DefaultDNS
name-server VERIZON PROVIDED DNS IP
name-server VERIZON PROVIDED DNS IP
object-group protocol TCPUDP
protocol-object udp
protocol-object tcp
access-list 100 extended permit tcp any host EXTERNALIP eq ftp
pager lines 24
logging enable
logging asdm informational
mtu External 1500
mtu Internal 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (External) 101 interface
nat (Internal) 101 0.0.0.0 0.0.0.0
static (Internal,External) tcp interface ftp 192.168.X.FTP ftp netmask 255.255.255.255
access-group 100 in interface External
route External 0.0.0.0 0.0.0.0 XTERNALNEXTHOPROUTERIP
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 management
http 192.168.0.0 255.255.255.0 Internal
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl encryption 3des-sha1 des-sha1 rc4-md5 aes128-sha1 aes256-sha1
webvpn
!
class-map INSPECTION_DEFAULT
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect icmp
!
service-policy global_policy global
prompt hostname context
call-home reporting anonymous
Cryptochecksum:55453015bdfb10764224067839a6d79d
: end
06-16-2015 05:17 AM
Hi,
I am not sure of how is this an ASA issue ?
Are you able to resolve domain names using the DNS server on your workstations ?
If not , I think the problem is there with the Workstations and the DNS server.
If you are , I think the pings should work as they are being allowed for the IP address also.
Thanks and Regards,
Vibhor Amrodia
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide