dsl77
asked on
Unable to access the web when connected to VPN
When connected to VPN I can access my Outlook and network shares but unable to browse the Internet – why?
My VPN connections is assigned their own DHCP IP scope 192.168.228.100-200
The PIX is located on 192.168.227.1
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password b4YMiQWlhCQP5KZD encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname vatican
domain-name thepope
clock timezone CEST 1
clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00
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 outside_in permit tcp any interface outside eq smtp
access-list outside_in permit tcp any interface outside eq www
access-list outside_in permit tcp any interface outside eq ftp
access-list outside_in permit tcp any interface outside eq ftp-data
access-list outside_in permit tcp any interface outside eq 3389
access-list outside_in permit tcp any interface outside eq 4899
access-list no_nat_VPN permit ip 192.168.227.0 255.255.255.0 192.168.228.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 195.184.116.xxx 255.255.255.252
ip address inside 192.168.227.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN_Pool 192.168.228.100-192.168.22
pdm location 192.168.227.0 255.255.255.0 inside
pdm location 192.168.227.210 255.255.255.255 inside
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) 0 access-list no_nat_VPN
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface smtp 192.168.227.210 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp interface www 192.168.227.210 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ftp 192.168.227.210 ftp netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ftp-data 192.168.227.210 ftp-data netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 3389 192.168.227.210 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 4899 192.168.227.210 4899 netmask 255.255.255.255 0 0
access-group outside_in in interface outside
route outside 0.0.0.0 0.0.0.0 195.184.116.xxx 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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.227.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
sysopt connection permit-pptp
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group PPTP accept dialin pptp
vpdn group PPTP ppp authentication pap
vpdn group PPTP ppp authentication chap
vpdn group PPTP ppp authentication mschap
vpdn group PPTP ppp encryption mppe auto
vpdn group PPTP client configuration address local VPN_Pool
vpdn group PPTP client configuration dns 192.168.227.210 192.168.227.211
vpdn group PPTP pptp echo 60
vpdn group PPTP client authentication local
vpdn username dsl77 password *********
vpdn enable outside
dhcpd auto_config outside
terminal width 80
Cryptochecksum:cae4d746195
I already looked at this article: http://www.expertsexchange.com/Networking/Q_20436866.html but without luck!
Thanks!
My VPN connections is assigned their own DHCP IP scope 192.168.228.100-200
The PIX is located on 192.168.227.1
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password b4YMiQWlhCQP5KZD encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname vatican
domain-name thepope
clock timezone CEST 1
clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00
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 outside_in permit tcp any interface outside eq smtp
access-list outside_in permit tcp any interface outside eq www
access-list outside_in permit tcp any interface outside eq ftp
access-list outside_in permit tcp any interface outside eq ftp-data
access-list outside_in permit tcp any interface outside eq 3389
access-list outside_in permit tcp any interface outside eq 4899
access-list no_nat_VPN permit ip 192.168.227.0 255.255.255.0 192.168.228.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 195.184.116.xxx 255.255.255.252
ip address inside 192.168.227.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN_Pool 192.168.228.100-192.168.22
pdm location 192.168.227.0 255.255.255.0 inside
pdm location 192.168.227.210 255.255.255.255 inside
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) 0 access-list no_nat_VPN
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface smtp 192.168.227.210 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp interface www 192.168.227.210 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ftp 192.168.227.210 ftp netmask 255.255.255.255 0 0
static (inside,outside) tcp interface ftp-data 192.168.227.210 ftp-data netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 3389 192.168.227.210 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 4899 192.168.227.210 4899 netmask 255.255.255.255 0 0
access-group outside_in in interface outside
route outside 0.0.0.0 0.0.0.0 195.184.116.xxx 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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.227.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
sysopt connection permit-pptp
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group PPTP accept dialin pptp
vpdn group PPTP ppp authentication pap
vpdn group PPTP ppp authentication chap
vpdn group PPTP ppp authentication mschap
vpdn group PPTP ppp encryption mppe auto
vpdn group PPTP client configuration address local VPN_Pool
vpdn group PPTP client configuration dns 192.168.227.210 192.168.227.211
vpdn group PPTP pptp echo 60
vpdn group PPTP client authentication local
vpdn username dsl77 password *********
vpdn enable outside
dhcpd auto_config outside
terminal width 80
Cryptochecksum:cae4d746195
I already looked at this article: http://www.expertsexchange.com/Networking/Q_20436866.html but without luck!
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
One thing i don’t understand is, my old setup I had my gateway on 192.168.0.1 and my vpn pool started at 192.168.101.xxx – and that worked fine!?
What I can read from the replies, there is no complete-easy-to-follow-an
Does Cisco have PPTP client that solves this issue? Or do I need to look for another VPN solution such as IPSec?
Any help is most appreciated – thanks! :)
What I can read from the replies, there is no complete-easy-to-follow-an
Does Cisco have PPTP client that solves this issue? Or do I need to look for another VPN solution such as IPSec?
Any help is most appreciated – thanks! :)
The issue is discussed at length in the links I posted above.
There is a complete and easy to follow solution for MS PPTP. The limitation is that the PIX cannot interact with the client.
Cisco has their own IPSEC client that is extremely easy to setup and use. It solves this issue with "split-tunneling" and full control of the client from the PIX.
There is a complete and easy to follow solution for MS PPTP. The limitation is that the PIX cannot interact with the client.
Cisco has their own IPSEC client that is extremely easy to setup and use. It solves this issue with "split-tunneling" and full control of the client from the PIX.
ASKER
Hi lrmoore..
Is it possible to add ‘split tunnelling’ to my Easy VPN installation – making is possible to access the web from a VPN connection. But as I understand that requires a concentrator to perform!?
Can I have IPSEC and PPTP running at the same time? If yes, can someone please post the IPSEC config I am missing according to the above config?
Is it possible to add ‘split tunnelling’ to my Easy VPN installation – making is possible to access the web from a VPN connection. But as I understand that requires a concentrator to perform!?
Can I have IPSEC and PPTP running at the same time? If yes, can someone please post the IPSEC config I am missing according to the above config?
Yes, you can use both IPSEC and PPTP at the same time. Use this example to configure for the IPSEC client
http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a008009442e.shtml
http://www.cisco.com/en/US/tech/tk583/tk372/technologies_configuration_example09186a008009442e.shtml
Here's an example that puts it all together for you for both clients:
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a0080093f89.shtml
Easy VPN with split-tunneling:
http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns27/networking_solutions_white_paper09186a008018914d.shtml
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a0080093f89.shtml
Easy VPN with split-tunneling:
http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns27/networking_solutions_white_paper09186a008018914d.shtml
One more great reference for managing VPN's on PIX
http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172787.html
http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a0080172787.html
ASKER
Thanks lrmoore..
The big picture is finally getting through my thick forehead…. That the way to go for me is IPSec!
One thing I was wondering about when reading through IPSec configuration examples, was that all refers to a vpngroup rather then a vpnd username as in PPTP?
Can I create separate IPSec clients accounts such as vpnuser 1, vpnuser2 etc when using IPSec?
Thanks a hole lot.. :)
The big picture is finally getting through my thick forehead…. That the way to go for me is IPSec!
One thing I was wondering about when reading through IPSec configuration examples, was that all refers to a vpngroup rather then a vpnd username as in PPTP?
Can I create separate IPSec clients accounts such as vpnuser 1, vpnuser2 etc when using IPSec?
Thanks a hole lot.. :)
Sure, you can create multiple groups, or have one common group with multiple username/passwords, or on common group with MS Radius authentication..
ASKER
Do you have an example on that somewhere…?
I’m up and running with IPSec at the moment one account ‘vpn3000’. One thing that I was wondering about is when conneted to the VPN I open the statistics on the VPN client and under ‘Tunnel details’ I can see my client address 192.168.228.104 but under ‘Route details’ I only have the 192.168.227.0 as secured routes – is that good enough?
I’m up and running with IPSec at the moment one account ‘vpn3000’. One thing that I was wondering about is when conneted to the VPN I open the statistics on the VPN client and under ‘Tunnel details’ I can see my client address 192.168.228.104 but under ‘Route details’ I only have the 192.168.227.0 as secured routes – is that good enough?
Yes, only the traffic to that nework will be encrypted. All the rest of the traffic goes out your normal internet connection..
This is the config I suggest, using Microsoft IAS RADIUS server. It's a snap to set up..
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800b6099.shtml
This is the config I suggest, using Microsoft IAS RADIUS server. It's a snap to set up..
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800b6099.shtml
ASKER
The RADIUS client that I am setting up under IAS, does it represent my VPN users or one static user?
I have registered IAS with AD thinking that users would get their logon credentials from AD!?
I have registered IAS with AD thinking that users would get their logon credentials from AD!?
ASKER
hehe.. the 'static' client is of cause the PIX itself - got it to work now, thanks lrmoore :)
https://www.experts-exchange.com/questions/21171526/Problems-with-PIX-VPN.html#12333554