Categories
Azure

App Service: Unable to contact IP driver

I had to debug an Azure App Service and was running a ping command on the Kudu PowerShell Console. When running a ping command, it returns ‘Unable to contact IP driver. General failure.’, which could lead you to believe there is a problem in the app service networking in general. However, this is not the case.


Kudu Remote Execution Console
Type 'exit' then hit 'enter' to get a new powershell process.
Type 'cls' to clear the console

PS C:\home> ping google.com
ping google.com
Unable to contact IP driver. General failure. 

ICMP ping is simply not supported, and TCP should be used instead.

This is an example of using tcpping instead of ping for an Azure App Service.

PS C:\home> tcpping google.com
tcpping google.com
Connected to google.com:80, time taken: 171ms
Connected to google.com:80, time taken: <1ms
Connected to google.com:80, time taken: <1ms
Connected to google.com:80, time taken: <1ms
Complete: 4/4 successful attempts (100%). Average success time: 42.75ms

Other debugging tools, such as nslookup, are regularly available.

nslookup google.com
Non-authoritative answer:
Server:  UnKnown
Address:  168.63.129.16
Name:    google.com
Addresses:  2a00:1450:400e:805::200e
  142.251.36.14

Alternatively, the nameresolver can also be used to observe how DNS resolves and to which IP address.

PS C:\home> nameresolver google.com
nameresolver google.com
Server: 168.63.129.16
Non-authoritative answer:
Name: google.com
Addresses: 
	142.250.179.174