Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: Routing failed to locate next hop for UDP from NP Identity

Routing failed to locate next hop for UDP from NP Identity 7 years 11 months ago #28478

  • gardocki
  • gardocki's Avatar
  • Offline
  • New Member
  • Posts: 2
  • Karma: 0
I get the following message when I try to connect a remote VPN client to the Cisco ASA 5505 FW:

Routing failed to locate next hop for udp from NP Identity Ifc: a.b.c.d/xyz to outside:192.168.1.141/xyz

The 192.168.1.141 is my inside IP address of the client machine. That machine is connected to the internet via a DSL router. The a.b.c.d IP address is the address of the outside interface of my host end firewall. I am statically routing on the ASA. When I debug the crypto isakmp, I get landed on the tunnel_group correctly. It is as if the response packet from the ASA can not get back to the client.

Gardocki
The administrator has disabled public write access.

Re: Routing failed to locate next hop for UDP from NP Identity 7 years 11 months ago #28481

  • gardocki
  • gardocki's Avatar
  • Offline
  • New Member
  • Posts: 2
  • Karma: 0
Got it...I had the crypto pointing to the wrong interface.
The administrator has disabled public write access.

Same error: Routing failed to locate next hop... 7 years 4 months ago #31107

  • PJ
  • PJ's Avatar
  • Offline
  • New Member
  • Posts: 1
  • Karma: 0
I got the same error Routing failed to locate next hop for udp from NP Identity and saw this post. I had made significant interfaces changes, including a change to the management interface which caused the error to show up. I had to create a new self-signed certificate, but still saw the error. I started to follow the Cisco recommended course of collecting the "show asp table routing" in preparation for opening up a ticket with TAC. I decided to first search the configuration for the IP address listed in the error, but came up with nothing. I then searched for the first 3 octets of the address in the config and discovered an ntp server command that used an ntp server located on the network reported in the error message and configured to use the Management interface. I updated the ntp command with the correct settings and the error stopped.
The administrator has disabled public write access.
Time to create page: 0.073 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup