You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After research, it seems that this issue is caused by Azure's ban on ICMP packets. The usage of System.Net.NetworkInformation.Ping class implies using ICMP protocol, therefore every ping will be timed out before it even reaches its destination.
Current state of the problem implies a redesign of the PingModule class.
Command ==ping is not working under these scenarios :
By implying valid, supplying an invalid Hostname will work (per the prior use of IP Resolver when supplying a Hostname).
The text was updated successfully, but these errors were encountered: