Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Could someone explain what "Deny inbound (No xlate)

Status
Not open for further replies.

ajinc

MIS
Aug 7, 2004
73
US
Hello All,
First Thank You for all the help you have given in the past it is greatly appreciated.

Could someone explain what

"Deny inbound (No xlate) tcp src inside:192.169.2.10 dst inside:10.10.10.1 means.

The 192 ip is my internal lan, and the 10. ip is the network on the vpn side that I am connecting to.

I have a pix on my network, and when I try to use the safenet vpn client to connect to a dlink vpn endpoint the syslog has this message in it, and my connection fails. If I take the pix off my network the safenet vpn client connects fine.

I am just going thru the PIX to get to the internet.

I have sysopt connection permit-ipsec enabled, I thought that would just pass ipsec traffic thru the pix.

For some reason the pix is blocking my outbound ipsec client connection, and I can't figure out why but I think this "deny" message in the syslog is the root of the problem.

Any help is greatly appreciated
 
sysopt connection permit-ipsec" only deals with IPSec traffic that is connecting to the PIX. That does not allow "pass-through".

As a simple question, why are you using a DLink as the endpoint of the VPN instead of the PIX? Secondly, the error message simply means that there is no VPN setup to allow connections.

Go ahead and post your config, and also post the IP of the DLink Endpoint you wish to use for VPN.

Computer/Network Technician
CCNA
 
LloydSev,
I have the PIX at my site as an endpoint, there is another site that uses the dlink 808hv as a vpn endpoint. I use the safenet client to connect to that network to perform network / system admin work for them. This worked fine until I put the pix on my network (purchased for the security factor)then I can't connect to the other sites dlink vpn endpoint.
The PIX is used at my site as a vpn endpoint, byt alas the safenet client connects to it, but I can't ping anything except the inside interface 192.169.2.1.
Everything works when I use the cisco client, but i need to get the safenet client to work with this device also.

Tahnks for any ideas!

Below is my config, and the dlink ip is 151.196.142.42

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100

hostname pixfirewall
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 pptp 1723
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
names
access-list OUTSIDE_IN permit icmp any any
access-list outside_cryptomap_dyn_10 permit ip any 10.10.10.0 255.255.255.0
access-list split permit ip 192.169.2.0 255.255.255.0 10.10.10.0 255.255.255.0
access-list inside_outbound_nat0_acl permit ip any 10.10.10.0 255.255.255.0
pager lines 24
logging on
logging timestamp
logging trap informational
logging host inside 192.169.2.2
icmp permit any outside
mtu outside 1500
mtu inside 1500
ip address outside pppoe setroute
ip address inside 192.169.2.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm
ip local pool kgcpa 10.10.10.1-10.10.10.10
pdm location 192.169.2.0 255.255.255.0 inside
pdm location 10.10.10.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 inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group OUTSIDE_IN in interface outside
route inside 10.10.10.0 255.255.255.0 192.169.2.0 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
ntp server 129.6.15.28 source outside prefer
http server enable
http 192.169.2.0 255.255.255.0 inside
http 10.10.10.0 255.255.255.255 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
sysopt connection permit-l2tp
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 10 set pfs group2
crypto dynamic-map outside_dyn_map 10 set transform-set ESP-3DES-MD5
crypto dynamic-map outside_dyn_map 10 set security-association lifetime seconds 86400 kilobytes 4608000
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client configuration address initiate
crypto map outside_map interface outside
crypto map inside_map client configuration address initiate
crypto map inside_map interface inside
isakmp enable outside
isakmp key ******** address 0.0.0.0 netmask 0.0.0.0 no-xauth
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 kgcpaipsec address-pool kgcpa
vpngroup kgcpaipsec dns-server 192.169.2.2 151.196.0.38
vpngroup kgcpaipsec default-domain ajinc.local
vpngroup kgcpaipsec split-tunnel split
vpngroup kgcpaipsec pfs
vpngroup kgcpaipsec idle-time 1800
vpngroup kgcpaipsec max-time 86400
vpngroup kgcpaipsec password ********
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
vpdn group pppoe_group request dialout pppoe
vpdn group pppoe_group localname locxy2q563
vpdn group pppoe_group ppp authentication pap
vpdn username locxy2q563 password *********
dhcpd address 192.169.2.10-192.169.2.41 inside
dhcpd dns 192.169.2.2 151.196.0.38
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain ajinc.local
dhcpd auto_config outside
dhcpd enable inside

terminal width
 
LloydSev,

Here is some additional info from my pix syslog when I try to use it to access the internet to get connect to my dlink endpoint

192.169.X.X - LAN
151.196.234.118 - PIX ouside interface
151.196.142.42 - DLINK

05-19-2005 16:55:48 Local4.Info 192.169.2.1 May 19 2005 16:53:35: %PIX-6-305012: Teardown dynamic TCP translation from inside:192.169.2.3/35122 to outside:151.196.234.118/13745 duration 0:00:31
05-19-2005 16:55:38 Local4.Info 192.169.2.1 May 19 2005 16:53:25: %PIX-6-305012: Teardown dynamic UDP translation from inside:192.169.2.2/1145 to outside:151.196.234.118/2130 duration 0:00:49
05-19-2005 16:55:32 Local4.Info 192.169.2.1 May 19 2005 16:53:19: %PIX-6-302015: Built outbound UDP connection 54343 for outside:151.196.142.42/500 (151.196.142.42/500) to inside:192.169.2.12/500 (151.196.234.118/4)
05-19-2005 16:55:32 Local4.Info 192.169.2.1 May 19 2005 16:53:19: %PIX-6-305011: Built dynamic UDP translation from inside:192.169.2.12/500 to outside:151.196.234.118/4

Again many thanks for your assistance!
 
I have yet to find anyone who can use the SafeNet client with the PIX.

This may change with the new OS, but it is not documented.

The PIX, on a site-2-site basis requires both ends to have the SAME ACL in order to function. I'm not sure if this is possible to work around with a DLink device. Possibly someone else with experience with it could help you, but I've never attempted using non-cisco equipment for VPN.

Computer/Network Technician
CCNA
 
LloydSev,
I appreciate all yor help.
Can I tap your thoughts just one more time on this issue.
I am trying to understand why the PIX would not allow my working vpn client (safenet softremote) connectivity to a dlink end point at another site.
If I place a linksys or netgear router on my network instead of the PIX the traffic would just flow thru to the endpoint that I tell it to hit.
I'm trying to understand why the pix would stop this traffic. It's just being used for internet access.
I guess I am stuck thinking that the pix would not even look at this traffic going out to another site, am I wrong in this assumption?
If so, then I must endevor to figure out why this is occurring.
Again thanks for any thoughts.
 
Deny inbound (No xlate) tcp src inside:192.169.2.10 dst inside:10.10.10.1 means.

your original question was what does that sentance mean, right?

Well it means that there is no NAT translation set up between those 2 ip address ranges. Probably because the PIX sees both of these IPs on your LAN. You have a routing issue and a config issue. Not a VPN issue. You may have one of those too, but that is not what the error message is telling you.

What I do not understand is this. why is the PIX denying inbound traffic from inside hosts? The only reason for that is usually becuase a VPN is terminated on the PIX, using the same IP ranges that you have on your LAN

sysopt connection permit-ipsec makes your PIX not push traffic the emerges from an IPSec tunnel through your OUTSIDE_IN Access-list.

eddie venus
 
eddie venus,

Thanks for your input.
I guess I have 2 problems, but I need to address this problem first

Here is the senario

At my site I have an asdl modem ==> pix ==> LAN

192.169.X.X - LAN
151.196.234.118 - PIX ouside interface


Presently my site's pix is allowing me access to the internet, and it has a vpn endpoint setup that the cisco client connects to with no problem.
I can map drives, and use remote desktop etc, so i figure my pix config is o.k.


At another site I have a dlink 808HV as a vpn endpoint.

151.196.142.42 - DLINK


At my site I have to use the safenet softremote client to connect to the dlink vpn endpoint.

At my site with the pix on the network (just using it for internet access to get to the dlink site)the outbound traffic from my pc with the safenet client can't connect to the dlink. My syslog has this info in it when I try to connect.


05-19-2005 16:55:48 Local4.Info 192.169.2.1 May 19 2005 16:53:35: %PIX-6-305012: Teardown dynamic TCP translation from inside:192.169.2.3/35122 to outside:151.196.234.118/13745 duration 0:00:31
05-19-2005 16:55:38 Local4.Info 192.169.2.1 May 19 2005 16:53:25: %PIX-6-305012: Teardown dynamic UDP translation from inside:192.169.2.2/1145 to outside:151.196.234.118/2130 duration 0:00:49
05-19-2005 16:55:32 Local4.Info 192.169.2.1 May 19 2005 16:53:19: %PIX-6-302015: Built outbound UDP connection 54343 for outside:151.196.142.42/500 (151.196.142.42/500) to inside:192.169.2.12/500 (151.196.234.118/4)
05-19-2005 16:55:32 Local4.Info 192.169.2.1 May 19 2005 16:53:19: %PIX-6-305011: Built dynamic UDP translation from inside:192.169.2.12/500 to outside:151.196.234.118/4

If I place a linksys or netgear router on my network instead of the PIX the traffic would just flow thru to the endpoint no problem.

I need to figure out why the pix is not allowing the safenet client to connect.
The safenet log state that
5-24: 08:41:14.427 Interface added: 192.169.2.12/255.255.255.0 on LAN "SiS 900 PCI Fast Ethernet Adapter".
5-24: 10:02:08.628
5-24: 10:02:08.638 My Connections\KGCPA at ODENTON - Initiating IKE Phase 1 (IP ADDR=151.196.142.42)
5-24: 10:02:08.638 My Connections\KGCPA at ODENTON - SENDING>>>> ISAKMP OAK MM (SA, VID 2x)
5-24: 10:02:24.391 My Connections\KGCPA at ODENTON - message not received! Retransmitting!
5-24: 10:02:24.391 My Connections\KGCPA at ODENTON - SENDING>>>> ISAKMP OAK MM (Retransmission)
5-24: 10:02:39.423 My Connections\KGCPA at ODENTON - message not received! Retransmitting!
5-24: 10:02:39.423 My Connections\KGCPA at ODENTON - SENDING>>>> ISAKMP OAK MM (Retransmission)
5-24: 10:02:54.454 My Connections\KGCPA at ODENTON - message not received! Retransmitting!
5-24: 10:02:54.454 My Connections\KGCPA at ODENTON - SENDING>>>> ISAKMP OAK MM (Retransmission)
5-24: 10:03:09.476 My Connections\KGCPA at ODENTON - Exceeded 3 IKE SA negotiation attempts

The safenet troubleshooting states that this message occurs whn packets are either not reaching the router, or can't route back.
Since I can ping the dlink vpn endpoint ip address I am assuming that the safenet client is reaching the dlink router, and they can route back when the pix if off my site's network, so I am assuming the pix is the culprit, but I can't figure out why the pix will not let this connection happen.
Any additional thoughts are greatly appreciated!



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top