simple remote access & file sharing for PIX 501

I have a Cisco PIX 501 that I have been trying to set up without success.  It will be used for our customers to access a portion of our network. This will be controlled by changing the inside address as necessary. As of now, I can't get connect to it using http or ssh. Config is below. Any help would be appreciated.

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password P5i20ljmvOS5P0cF encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname ****Members
domain-name ***.com
clock timezone est -5
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 pptp 1723
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
name 10.99.99.181 members
name *.*.*.67 EXmembers
access-list outsidein permit gre any host EXmembers
access-list outsidein permit tcp any host EXmembers eq pptp
pager lines 24
logging on
logging console debugging
mtu outside 1500
mtu inside 1500
ip address outside *.*.*.66 255.255.255.224
ip address inside 10.99.99.102 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 10.99.99.0 255.255.255.0 0 0
static (inside,outside) *.*.*.65 members netmask 255.255.255.255 0 0
route outside 0.0.0.0 0.0.0.0 *.*.*.0
timeout xlate 3:00: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 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
ntp server 128.4.40.12 source outside
ntp server 204.34.198.40 source outside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 10.99.99.0 255.255.255.0 inside
telnet timeout 5
ssh *.*.*.18 255.255.255.255 outside
ssh *.*.*.65 255.255.255.255 outside
ssh timeout 5
console timeout 0
dhcpd dns *.*.*.* *.*.*.*
terminal width 80
Cryptochecksum:29e2d0ffaea0682399032afe3dcaaead
: end
stukatAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cstosgaleCommented:
Hi,

This will probably be because you have not generated te RSH keys.

See this article of details of how to do this: http://www.ciscopress.com/articles/article.asp?p=25342&seqNum=3
0
stukatAuthor Commented:
OK. RSH keys have been generated and saved to flash but I still can't connect using SSH or http.
The *.*.*.65 is the default gatway of the range of addresses while the *.*.*.66 is the outside address associated with the PIX. I also have been unable to create a VPN from my Windows XP Pro computer to this PIX. If I try to connect to the PIX using Tereterm with an IP address I get the following error:

402106: Rec'd packet not an IPSEC packet. (ip) dest_addr= *.*.29.66, src_addr
= *.*.28.5, prot= tcp
0
cstosgaleCommented:
Ah, i think i see your problem.

The SSH command specifies which source address can connect to the pix via SSH. You have specified the default gateway address in here but not any source addresses for external hosts.

so for example, if you were on your ADSL connection at home, and whilst on this connection, your IP address when you go to www.whatismyip.com is 1.2.3.4, you will need a line in your pix config that says ssh 1.2.3.4 outside

Equally to connect ia http or https you will need a command that says "http 1.2.3.4 outside" or "https 1.2.3.4 outside"

With regards to you not being able to connect the vpn, you will need to allow the traffic through the outside access list (permit udp 500 and 4500 and protocol esp) and add the command: sysopt ipsec pl-compatible which should allow vpn traffic through the access-lists.

I would recommend using putty by the way for SSH connections.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IT Degree with Certifications Included

Aspire to become a network administrator, network security analyst, or computer and information systems manager? Make the most of your experience as an IT professional by earning your B.S. in Network Operations and Security.

stukatAuthor Commented:
OK. I can now SSH into the PIX. Thank you. VPN still not working. Not sure what to change the access-list to but I tried....
revised config below:

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ********************** encrypted
passwd ********************* encrypted
hostname **************Members
domain-name *******.com
clock timezone est -5
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 pptp 1723
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
name 10.99.99.181 members
name *.*.29.67 EXmembers
access-list outside_access_in permit tcp any host *.*.29.66
pager lines 24
logging on
logging console debugging
mtu outside 1500
mtu inside 1500
ip address outside *.*.29.66 255.255.255.224
ip address inside 10.99.99.102 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 10.99.99.0 255.255.255.0 0 0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 *.*.29.65 1
timeout xlate 3:00: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 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
ntp server 128.4.40.12 source outside
ntp server 204.34.198.40 source outside
http *.*.28.5 255.255.255.255 outside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt ipsec pl-compatible
telnet 10.99.99.0 255.255.255.0 inside
telnet timeout 5
ssh *.*.28.18 255.255.255.255 outside
ssh *.*.29.65 255.255.255.255 outside
ssh *.*.29.70 255.255.255.255 outside
ssh *.*.28.5 255.255.255.255 outside
ssh 10.99.99.69 255.255.255.255 inside
ssh timeout 5
console timeout 0
dhcpd dns 208.39.158.2 208.39.140.42
terminal width 80
Cryptochecksum:fbfbd3924dd880abec33d849271dc41e
: end
0
stukatAuthor Commented:
I think I'm over my head. I want to create a VPN tunnel from Windows XP (outside my building) to the PIX 501. If this isn't possible I can use the Cisco VPN Client (but would prefer not to). The PIX is 3DES but it's not currently configured. I want all remote users to connect to a specific server (10.99.99.181) to authenticate. I played with the code (again) so I have listed the revised config below. As always, your help is appreciated.

:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ############ encrypted
passwd ############### encrypted
hostname ######Members
domain-name #####.com
clock timezone est -5
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 pptp 1723
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
name 10.99.99.181 members
name 66.240.29.67 EXmembers
access-list outside_access_in permit tcp any host EXmembers eq pptp
access-list outside_access_in permit gre any host EXmembers
access-list outside_access_in permit tcp any host EXmembers eq https
access-list outside_access_in permit tcp any host EXmembers eq www
access-list outside_access_in permit udp any host EXmembers eq 4500
access-list outside_access_in permit udp any host EXmembers eq isakmp
access-list outside_access_in permit esp any host EXmembers
pager lines 24
logging on
logging console debugging
mtu outside 1500
mtu inside 1500
ip address outside 66.240.29.66 255.255.255.224
ip address inside 10.99.99.102 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list outside_access_in
nat (inside) 1 10.99.99.0 255.255.255.0 0 0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) EXmembers members netmask 255.255.255.255 0 0
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 66.240.29.65 1
timeout xlate 3:00: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 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
ntp server 128.4.40.12 source outside
ntp server 204.34.198.40 source outside
http 66.240.28.5 255.255.255.255 outside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt ipsec pl-compatible
telnet 10.99.99.0 255.255.255.0 inside
telnet timeout 5
ssh 66.240.28.18 255.255.255.255 outside
ssh 66.240.29.65 255.255.255.255 outside
ssh 66.240.29.70 255.255.255.255 outside
ssh 66.240.28.5 255.255.255.255 outside
ssh 10.99.99.69 255.255.255.255 inside
ssh timeout 5
console timeout 0
dhcpd dns 208.39.158.2 208.39.140.42
terminal width 80
Cryptochecksum:986f6c6c24a30f993e2797bd4d1cb051

Once again, thanks for your help.
0
cstosgaleCommented:
No problem, it is possible to create an L2TP over IPSec connection to the pix without the VPN client (which uses straight forward IPSEC), but you'll need to open a new question as to how to do that :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cisco

From novice to tech pro — start learning today.