PIX 501 VPN, Able to access LAN through vpn but can't browse?

[ixleplix]

I can open the VPN session using the 3.6.3 client set for pre-shared secret. Once it's open however weird things happen. Most of the time I can ping a host on my LAN by Netbios name, FQDN or by IP address. When I try to map a drive though, it only works if I use the IP of the host \\x.x.x.x\sharename and then it’s sporadic. Sometimes I can’t even map that? I need help with this one. I need a stable VPN so I can configure the home machines and forget about it.

Thanks in advance for any help!
Here is a copy of my config.

PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ************************************ encrypted
passwd ******************************************** encrypted
hostname **********
domain-name my.domain
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
access-list 101 permit ip x.x.1.0 255.255.255.0 x.x.1.32 255.255.255.248
access-list 101 permit icmp any any echo-reply
access-list 101 permit icmp any any time-exceeded
access-list 101 permit icmp any any unreachable
pager lines 24
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside x.x.x.173 255.255.255.0
ip address inside x.x.1.5 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_pool x.x.1.32-x.x.1.36
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group 101 in interface outside
route outside 0.0.0.0 0.0.0.0 x.x.x.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 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 x.x.1.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-ipsec
no sysopt route dnat
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 interface outside
isakmp enable outside
isakmp identity address
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 *************************** address-pool vpn_pool
vpngroup *************************** dns-server x.x.1.1
vpngroup *************************** wins-server x.x.1.1
vpngroup *************************** default-domain my.domain
vpngroup *************************** split-tunnel 101
vpngroup *************************** pfs
vpngroup *************************** idle-time 1800
vpngroup *************************** password ********
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 60
ssh timeout 5
dhcpd address x.x.1.51-x.x.1.100 inside
dhcpd dns x.x.1.1
dhcpd wins x.x.1.1
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain my
dhcpd enable inside
terminal width 80
Cryptochecksum:******************************************

 

[gbiello]

I've seen this too. A lot determined on how the client was accessing the Internet. If it was via a corporate LAN, there was no trouble at all. If the client was dialing up via AOL, things sucked.

-gbiello

 

[yizhar]

HI.

***

> nat (inside) 0 access-list 101
> access-group 101 in interface outside
> vpngroup *************************** split-tunnel 101

I don't know if it is related to the problem, but you should not reuse same ACL bound to different things.

***

What is the workstation OS?
Your workstation might be using cached DNS entries for your domain name, and therefor might not use the DNS server provided by this line:
vpngroup *************************** dns-server x.x.1.1

I normally do not bother much about name resolution for VPN clients. I either setup a LMHOSTS/HOSTS file if access to single server is needed, or setup remote control over VPN (VNC/PCAW/TS...) and then the user can realy work as part of the network, eliminating both name resolution and bandwidth problems.

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[ixleplix]

Yizhar,
I've tested it on Win98 and XP Pro so far.

nat (inside) 0 access-list 101
access-group 101 in interface outside
vpngroup *************************** split-tunnel 101

These lines came out of the link

http://www.cisco.com/warp/public/110/pix3000.html

I'm kind of new with the high end routers, how do you suggest I configure that portion of it?

gbiello,
One The XP Pro is running AOL 7.0 and Cisco tech support says that this is a known issue, however the Win98 (A test machine outside of the firewall) has a direct high speed connection with a static IP.

ixleplix

 

[yizhar]

HI.

> I'm kind of new with the high end routers,
> how do you suggest I configure that portion of it?
Option 1: Use GUI like PDM or pixcript.

Options 2:
Simply don't reuse the same ACL for totaly different tasks.
Here is an example based on your config:
access-list nonat permit ip x.x.1.0 255.255.255.0 x.x.1.32 255.255.255.248
access-list split permit ip x.x.1.0 255.255.255.0 x.x.1.32 255.255.255.248
access-list 101 permit icmp any any echo-reply
access-list 101 permit icmp any any time-exceeded
access-list 101 permit icmp any any unreachable
access-group 101 in interface outside
nat (inside) 0 access-list nonat
vpngroup *************************** split-tunnel split

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[ixleplix]

Yizhar,
Thanks for the help. I changed it to read like this and will test it today.


access-list 101 permit ip x.x.1.0 255.255.255.0 x.x.1.32 255.255.255.248
access-list 102 permit ip x.x.1.0 255.255.255.0 x.x.1.32 255.255.255.248
access-list 103 permit icmp any any echo-reply
access-list 103 permit icmp any any time-exceeded
access-list 103 permit icmp any any unreachable
access-group 103 in interface outside
nat (inside) 0 access-list 102
vpngroup *************************** split-tunnel 101

ixleplix

 

[ixleplix]

I did get a resolution by doing a few things.

1. I removed the split-tunnel 101 from the vpngroup
2. I changed the Isp from AOL to MSN
3. On the 98 machine I had to manually add the IP of the WINS server; on the Win2000 it pulled the info automatically.

Once those were done, I was able to connect, browse, and map a drive by \\compname\share or \\IP\share.

Again I appreciate all of the help.

ixleplix