Solved

How do I open ports and ping on Cisco Pix 501?

Posted on 2008-10-24
4
771 Views
Last Modified: 2013-11-16
I'm trying to establish a Quick VPN connection to  Linksys 4400N VPN router from a computer behind a Cisco Pix 501.  The ports that need to be allowed on the Pix are 443 and 60443.  Also ping needs to be allows through the Pix.  Linksys logs show a connection is establish but the connection fails with error "Failed to ping the remote VPN router - Ping was blocked, which can cause an unexpected disconnect."  I also have another error on the Linksys router that says the Pix did not respond.
Attached is my config file.
Thanks for any help!

: Saved
: Written by enable_15 at 10:35:43.193 UTC Thu Oct 23 2008
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password JhWJqVWL3fjhb2s7 encrypted
passwd JhWJqVWL3fjhb2s7 encrypted
hostname AE
domain-name AE
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list outside_access_in permit tcp any interface outside eq 3389
access-list outside_access_in permit tcp any any eq https
access-list outside_access_in permit tcp any any eq 60443
access-list inside_access_out permit icmp any any log
access-list inside_access_in permit icmp any any log
pager lines 24
logging on
icmp permit host 70.105.62.63 echo-reply outside
mtu outside 1500
mtu inside 1500
ip address outside 70.105.60.179 255.255.255.0
ip address inside 192.168.10.254 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.10.2 255.255.255.255 inside
pdm location 192.168.10.0 255.255.255.0 inside
pdm location 67.62.211.177 255.255.255.255 outside
pdm location 192.168.1.0 255.255.255.0 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface 3389 192.168.10.2 3389 netmask 255.255.2
.255 0 0
static (inside,outside) tcp interface 6905 192.168.10.2 6905 netmask 255.255.2
.255 0 0
static (inside,outside) tcp interface https 192.168.10.113 https netmask 255.2
.255.255 0 0
static (inside,outside) tcp interface 60443 192.168.10.113 60443 netmask 255.2
.255.255 0 0
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 70.105.60.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 67.62.211.177 255.255.255.255 outside
http 192.168.10.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.10.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
terminal width 80
Cryptochecksum:56f056fdd4125f36fb01e768bdbd5797
0
Comment
Question by:cjdye
  • 2
  • 2
4 Comments
 
LVL 77

Expert Comment

by:arnold
ID: 22795863
For opening ports to an IP, you should use 255.255.255.255 as the netmask.
You seem to have an error for the 3389 and the 6905 ports:
static (inside,outside) tcp interface 3389 192.168.10.2 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 6905 192.168.10.2 6905 netmask 255.255.255.255 0 0

Currently you are only permitting ping/icmp reply from an external host.
I.e. if you ping from the pix to 72.105.60.62, I think you'll get a response.
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094e8a.shtml


Another option is to disable the ping check on the linksys VPN configuration.  Assume the host is up.
0
 

Author Comment

by:cjdye
ID: 22796473
Thanks for the info,
I can connect in through port 3389 with no problem when using RDP.  
Can I open the 443 and 60443 ports for use by all clients behind the Pix or do I need to have a command that routes this traffic to a specific internel IP?
I beleive the Pix needs to accept a ping request from the Linksys and respond to it.

Thanks for the input!
0
 
LVL 77

Expert Comment

by:arnold
ID: 22796686
Usually clients behind the PIX can access anything outside unless you have setup access lists to limit that.

You do not have any access list that prevents LAN systems from accessing any resources on the internet.

I do not see any VPN configuration on your PIX. So when the linksys attempts to establish a VPN, it gets no response back.
you would likely need to add to the pix configuration a
nat (inside) 0 to allow VPN Ips from the remote location to get to your LAN side and vice versa.
You should look at the cisco site www.cisco.com for VPN on PIX.  They have many examples there.
0
 

Accepted Solution

by:
cjdye earned 0 total points
ID: 22798080
Thanks, I will check that out.
Joey
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
AWS Design\Cisco Meraki 4 34
Setting up L2TP/IPsec in RRAS 5 40
Cisco IPSec lan to lan tunnel - encryption domain. 3 36
Cisco ASA VPN Client Routing 8 41
Secure VPN Connection terminated locally by the Client.  Reason 442: Failed to enable Virtual Adapter. If you receive this error on Windows 8 or Windows 8.1 while trying to connect with the Cisco VPN Client then the solution is a simple registry f…
Quality of Service (QoS) options are nearly endless when it comes to networks today. This article is merely one example of how it can be handled in a hub-n-spoke design using a 3-tier configuration.
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question