General Failure pinging host name while on VPN

[aknox]

Hello,

I'm running into a bit of an odd problem. One of my users who is primarily a remote worker cannot use one of his primary applications while connected to our ASA VPN using the AnyConnect client.

Apparently the application needs to be able to ping itself / resolve the local host name. In house it works fine. While he's on the VPN functionality breaks. In doing some testing, I've found that while connected to the VPN pinging the local host name / IP address results in a "General failure." message. In fact, I get this message when trying to ping any IP in the range handed out by the ASA. 

I'm fairly new at the company and my experience with ASA's / VPN's in general is fairly limited.

Any help would be greatly appreciated.

[Rahul Govindan]

Ping functionality itself should not be broken with Anyconnect VPN, unless you have some sort of filter applied for your VPN users. PC hostname resolution might not be possible if you assign ip addresses via the ASA local ip address pool - your dns/wins server has no information about this.

Are you able to ping a VPN client user from the ASA inside interface?

[aknox]

I am able to ping the IP of a vpn system using the ASA inside interface but not the host name. Is it possible to set up a client profile / group policy so it's using an address pool that the dns/wins server has access to?

[PeterLMSD]

Hi, just a heads up I posted a lengthy thread.

https://community.cisco.com/t5/vpn/general-failure-when-pinging-hostname-while-on-vpn/m-p/4871371

If you were trying on a newer model HP, the issue I found was built in wifi and ethernet / thunderbolt adapters caused me to get a general failure when trying to do a "ping *hostname* -4" making sure it was IPv4.

But if I used an external USB-A Ethernet (StarTech USB31000S) or Wireless (TP-Link TL-WN821N) adapter then it did work.

Working with HP but I do wonder if other hardware OEMs have the same problem with AnyConnect.