"no translation group found"

[Frylock]

VPN clients cannot access network resources when connected through VPN. They get an error that the either the network resource could not be found or that they do not have permission to access them.

We are using a PIX 501.
The log shows repeated entries similar to this:
305005: No translation group found for udp src outside: 192.168.0.191/1071...

PIX config:
PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password V4mjwuaoG2IOiI.4 encrypted
passwd V4mjwuaoG2IOiI.4 encrypted
hostname UMDF-PIX
domain-name umdf.local
clock timezone EST -5
clock summer-time EDT recurring
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 acl_out permit icmp any any
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq smtp
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq www
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq pop3
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq 1733
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq www
access-list acl_out permit tcp any host xxx.xxx.xxx.xxx eq ssh
access-list acl_in permit icmp any any
access-list acl_in permit ip any any
access-list 100 permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list 100 permit ip any 192.168.1.0 255.255.255.240
pager lines 24
logging on
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.xxx 255.255.255.224
ip address inside 192.168.0.254 255.255.255.0
ip verify reverse-path interface outside
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN 192.168.1.1-192.168.1.10
ip local pool UMDF_VPN 192.168.0.191-192.168.0.200
pdm location 192.168.0.1 255.255.255.255 inside
pdm location 192.168.0.102 255.255.255.255 inside
pdm location 66.219.161.192 255.255.255.240 outside
pdm location 192.168.1.0 255.255.255.0 outside
pdm location 192.168.0.101 255.255.255.255 inside
pdm logging errors 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 100
nat (inside) 1 192.168.0.0 255.255.255.0 0 0
static (inside,outside) 208.250.55.131 192.168.0.102 netmask 255.255.255.255 0 0
static (inside,outside) 208.250.55.132 192.168.0.1 netmask 255.255.255.255 0 0
static (inside,outside) 208.250.55.133 192.168.0.101 netmask 255.255.255.255 0 0
access-group acl_out in interface outside
access-group acl_in in interface inside
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.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 h323 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.0.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
sysopt connection permit-pptp
no sysopt route dnat
crypto ipsec transform-set VPNset esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto dynamic-map dynmap 10 set transform-set VPNset
crypto dynamic-map dynmap 30 set transform-set ESP-3DES-SHA
crypto dynamic-map inside_dyn_map 20 set transform-set ESP-3DES-SHA
crypto map VPNmap 10 ipsec-isakmp dynamic dynmap
crypto map VPNmap interface outside
crypto map inside_map 65535 ipsec-isakmp dynamic inside_dyn_map
crypto map inside_map interface inside
isakmp enable outside
isakmp enable inside
isakmp identity address
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
isakmp policy 30 authentication pre-share
isakmp policy 30 encryption 3des
isakmp policy 30 hash sha
isakmp policy 30 group 2
isakmp policy 30 lifetime 86400
vpngroup UMDF address-pool UMDF_VPN
vpngroup UMDF dns-server 192.168.0.1 205.171.3.65
vpngroup UMDF split-tunnel 100
vpngroup UMDF idle-time 7200
vpngroup UMDF password ********
vpngroup UMDF2 address-pool VPN
vpngroup UMDF2 dns-server 192.168.0.1 205.171.3.65
vpngroup UMDF2 default-domain umdf.local
vpngroup UMDF2 idle-time 1800
vpngroup UMDF2 password ********
telnet 192.168.0.0 255.255.255.0 inside
telnet timeout 5
ssh 66.219.161.192 255.255.255.240 outside
ssh timeout 5
terminal width 80
Cryptochecksum:3719c66c8494cfd2efb70372ac52ca0f
: end
[OK]


I have found posts that advise adding the command:
"isakmp nat-traversal"
But that command gives and error "not enough arguments"
If I add a lifetime to the command (isakmp nat-traversal 20" I get a usage list.

Clients are connecting using IPSec over UDP.
I have not tried using IPSec over TCP, but will try it tonight just in case.

 

[lgarner]

The 192.168.0 network is inside. Try using a different range for the vpn address pool and change the nat 0 ACL accordingly.

 

[Frylock]

The address pool had previously been 192.168.1.1 through 10
The address pool of 192.168.0.191 through 200 was added while trying to troubleshoot this problem.
I am fairly new to this, but I was under the impression that the clients should receive IP's that are on the internal network.
Anyway, clients had the same problem using either pool.
I have now removed the pool using internal addresses.
Also, how should the nat 0 ACL be modified?
Here is the current entry:
access-list 100 permit ip 192.168.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list 100 permit ip any 192.168.1.0 255.255.255.240

Some background: This problem started after our network connection was upgraded to a T1, a new router was installed and our external IP's were changed. VPN clients were updated with the new IP and could connect with no problem but could not access anything.

 

[lgarner]

It's better to have the users on a separate LAN. Pix likes to route, and doesn't know quite what to do with packets that are to & from the same network.

It should work with the UDMF2 vpngroup and VPN pool.

access-list 100 might not need changing. With the VPN pool range, you could remove the first line.

I think this is the source of the log messages. Try putting the VPN users on a different range and see if the messages change.

 

[Frylock]

Last night I conected using the non-internal IP pool and was still getting errors that the resources could not be found.

I checked the log this morning, it listed the error: 106011: Deny inbound (No xlate) udp src outside: 192.168.1.1...
I found this on info on the error:
"Somebody tried to open an inbound connection throgh an address which is used for outbound port address translation(PAT)."

You suggested using a different IP range, do you mean creating a whole new IP pool?
Also, since you didn't mention the NAT-traverse in you responses should I rule that out as a potential cause to the problem?