Link to home
Start Free TrialLog in
Avatar of Manuel
ManuelFlag for United States of America

asked on

Allow VPN server access behind PIX

Hello,

          I am trying to allow inbound connection to a VPN server which is running on a Windows Server 2003 machine which is behind a PIX. I already put access-list and static's and I even reloaded the access-list, and nothing. I know is not the VPN server, because I connected to it using a internal client machine. The port which I am opening on the PIX is the Port for PPTP (Point-to-Point Tunneling Protocol) which is 1723 TCP. Below is a copy of my running-config.
 
                                               Thank You In Advance

PIX Version 6.3(5)
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxx encrypted
passwd xxxxxxxxxxx encrypted
hostname pixfirewall
domain-name xxxxx
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
no fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 101 permit ip 10.1.1.0 255.255.255.0 10.1.2.0 255.255.255.0
access-list allow_inbound permit tcp any interface outside eq www
access-list allow_inbound permit icmp any any source-quench
access-list allow_inbound permit tcp any interface outside eq ssh
access-list allow_inbound permit tcp any host 216.254.X.X eq www
access-list allow_inbound permit tcp any host 216.254.X.X eq ssh
access-list allow_inbound permit tcp any host 216.254.X.X eq h323
access-list allow_inbound permit tcp any host 216.254.X.X eq 5060
access-list allow_inbound permit tcp any interface outside eq pptp
access-list deny_outbound deny tcp any host 63.236.X.X eq https
access-list deny_outbound permit ip any any
access-list deny_outbound deny tcp any host 209.202.X.X eq https
access-list deny_outbound deny tcp any host 63.236.X.X eq www
no pager
logging on
logging timestamp
logging monitor debugging
logging trap notifications
logging queue 24
logging host inside 10.1.1.23
icmp deny any outside
mtu outside 1500
mtu inside 1500
ip address outside 216.254.X.X 255.255.255.0
ip address inside 10.1.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool ippool 10.1.2.1-10.1.2.254
pdm location 10.1.1.6 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 10.1.1.0 255.255.255.0 0 0
static (inside,outside) tcp interface www 10.1.1.6 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ssh 10.1.1.6 ssh netmask 255.255.255.255 0 0
static (inside,outside) tcp interface pptp 10.1.1.8 pptp netmask 255.255.255.255 0 0
static (inside,outside) 216.254.X.X 10.1.1.7 netmask 255.255.255.255 0 0
static (inside,outside) 216.254.X.X 10.1.1.24 netmask 255.255.255.255 0 0
access-group allow_inbound in interface outside
access-group deny_outbound in interface inside
route outside 0.0.0.0 0.0.0.0 216.254.X.X 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
aaa authentication ssh console LOCAL
http server enable
http 10.1.1.0 255.255.255.0 inside
snmp-server host inside 10.1.1.23
no snmp-server location
no snmp-server contact
snmp-server community nyc4u2me
snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client authentication LOCAL
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup vpn3000 address-pool ippool
vpngroup vpn3000 default-domain pix.com
vpngroup vpn3000 split-tunnel 101
vpngroup vpn3000 idle-time 1800
vpngroup vpn3000 password ********
vpngroup vmr2 address-pool ippool
vpngroup vmr2 default-domain pix.com
vpngroup vmr2 split-tunnel 101
vpngroup vmr2 idle-time 1800
vpngroup vmr2 password ********
vpngroup grace address-pool ippool
vpngroup grace default-domain XXXX
vpngroup grace split-tunnel 101
vpngroup grace idle-time 1800
vpngroup grace password ********
telnet timeout 30
ssh 10.1.1.0 255.255.255.0 inside
ssh timeout 60
console timeout 0
username vmr2 password XXXXXXXXXXXXXX encrypted privilege 15
username victor password XXXXXXXXXXXXXX encrypted privilege 3
privilege show level 15 command access-group
privilege clear level 15 command access-group
terminal width 80
banner login Hello, Victor!
banner motd Unauthorized access and use of this network/device will be prosecuted.
Cryptochecksum:83dadb3b861cb7cbe4f7ae32d426cc6f
: end


ASKER CERTIFIED SOLUTION
Avatar of calvinetter
calvinetter
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Manuel

ASKER

Hello calvinetter,


        Ok. I was able to connect to the VPN server however, when I try to ping machines which are in the same LAN as the VPN server I am not able to reach them or RDP into them? What could be the problem?


                                                                                                    Thank You
Oops, got in a hurry there...you also need to allow gre inbound:

access-list allow_inbound permit gre any interface outside
access-group allow_inbound in interface outside

cheers
Actually, you may not need gre inbound, as long as you have the "fixup protocol 1723" already configured.
You'll need to allow gre outbound, since you've got an ACL on the inside interface:

access-list deny_outbound permit gre any any
access-group deny_outbound in interface inside

cheers
Avatar of Keith Alabaster
agreed. The default when you do not have an acl applied to an interface is to allow all traffic to pass from a higher to lower interface. Because you have applied an outbound acl, you will have to have an explicit allow statement for anything you want to go out from now on.
Avatar of Manuel

ASKER

I added the lines that you told me calvinetter and it did not work, I am able to connect to the VPN Server, but when I try to ping the machines which are in the same LAN as the VPN server I am not able to?
Avatar of graemeboro
graemeboro

Are you pinging these devices from the outside interface?

I notice in the config you have icmp deny any outside rule enabled.  You may need to disable this rule.

Graeme
Avatar of Manuel

ASKER

Yes I am trying to ping them from the outside, yes I have that rule set, however even if I do not ping them I cannot even RDP into them from the outside?

                                                      Thanks
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Manuel

ASKER

Forget it, I found out what was the problem. The problem was that the client computer was using the same subnet as the VPN server, so there was a conflict with the IP address which led to the reason why I could not ping the VPN server's LAN.


                                            Thanks everyone for all your help
:) Well done