PIX 501 VPN Unable to access internal network

I have a PIX 501 VPN setup and am able to connect to the VPN but not to the internal network.
Below is my configuration file.

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password F5UEMk//eGWA47uK encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname borlandpix
domain-name borland.com
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
access-list inside_outbound_nat0_acl permit ip any
access-list outside_cryptomap_dyn_20 permit ip any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_pool
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 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
http server enable
http inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client authentication LOCAL
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup Borland address-pool vpn_pool
vpngroup Borland idle-time 1800
vpngroup Borland password ********
telnet inside
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group isp request dialout pppoe
vpdn group isp localname xxxxxxxx
vpdn group isp ppp encapsulation pap
vpdn username xxxxxxx.net  password xxxxxxx
dhcpd address inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
username dena password Bbv/hpk/k1rYQnMJ encrypted privilege 2
terminal width 80
: end
Who is Participating?
lrmooreConnect With a Mentor Commented:
It shouldn't be a security issue, so if it works, as bizzar as it is, leave it as is.
Are you trying to connect from a Comcast network.  I have a number of VPNs that work from elsewhere, but not on Comcast.  I can take the laptops to any other network and they work fine.  Comcast is blocking a number of protocols and not admitting it - althought there have been a number of news reports about it.  Anyway, are you on Comcast?
I forgot to mention - I have setup a number of PIX VPNs and people on about five of them all lost connectivity the same week.  They were all serviced by Comcast in the same county and no one else lost the ability to browse.  By the wya, they can all still complete the VPN login, but none of them can browse the internal network.  Sure they're not blocking protocols!
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

Add this command:

isakmp nat-traversal 20

Open in new window

>ip address inside
Also, make sure your VPN Client home network is not the same as the inside of the PIX
jlgray48Author Commented:
Added both statements still no internal network.
Try adding this acl. Then post results of "show access-list" while your client is connected. Also make sure your VPN client is set to use UDP transparent nat in the transport tab.

access-list SPLIT_TUNNEL_ACL permit ip
vpngroup Borland split-tunnel SPLIT_TUNNEL_ACL

Open in new window

jlgray48Author Commented:

I added the following to my config and I can now ping and access by ip but wins is not resolving to host names.

outside router (outside interface ip) 255


That route statement makes no sense.  You never add a route to your own interface ip.
Add the wins-server config to the vpn configuration.

vpngroup Borland wins-server 192.168.1.x
jlgray48Author Commented:
It seems odd to me as well but I wonder if the reason I have to have that is because I have a bridged dsl modem between the pix and the outside. Is there a security issue with having it setup that way?

I've taken it out and I can't access the internal network. When I add it back it starts working again.

Any ideas?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.