In article , hoser wrote: :I am having a problem with the syslog which is reporting:
:"No translation group found for udp src inside:169.254.126.114/500 dst :outside:192.168.100.2/500"
:As far as i know 169.254.126.114 is a MS proprietory IP, and i dont :know why this address is requesting a translation.
169.254/16 is the network number that Microsoft and Mac OS X hosts uses when they attempt to DHCP and [for whatever reason] do not receive an answer; also, they may use it on rare occasions if static IP address configuration fails. Windows boxes have a tendancy to DHCP unexpectedly -- we get a noticable number of incidents in which Windows boxes with static IPs DHCP anyhow.
Thus, what is -likely- happening is that some Windows host on your network was unable to get an IP and so assigned itself a random IP in the 169.254/16 range. Now the host is trying to form a VPN connection to 192.168.100.2.
Likely your 'nat (inside)' statement lists only your real IP ranges instead of the (all too common) nat (inside) 1 0.0.0.0 0.0.0.0 that people have a tendacy to use. Since the IP does not match any of your nat or static statements, the PIX refuses to let the packet out [which is what you want in this case!] It sounds like you have configured properly and that your PIX has reacted properly.