Hey,
I'm having issues connecting to endpoints using the .Net method System.Net.NetworkInformation.Ping to ping an endpoint. It started out as me just trying to ping internal endpoints within our VPN network, but I can't seem to even be able to even ping the standard 8.8.8.8 right now. In my console application on prem I have no issues doing anything.
On my PC (console application)
Code executed
Response
.Net Extension
As we don't seem to have any issues with the VPN as we've been connecting to various endpoints within this network without any issues, I don't think there is any missing setup for the VPN, unless there is something that needs to be done specifically for .Net extensions..?
Am I missing something in this setup? I get the feeling that there is some sort of firewall on the server that is blocking my requests? I'm not even sure where to look anymore and hope someone has some insights into how these things work or can see what I did wrong. At this point any help is better than no help! :D
For quick context, I have to build a tool where I access various internal endpoints, but at the moment, those actions respond with not being able to resolve the endpoints given, so I opted into the most basic action (ping) to establish connection from my extension to an endpoint, which seems to be where the problem lies.
Br. Viktor
How does your tool normally access those endpoints? (e.g. REST/SOAP?)Are you using OutSystems public cloud or on-prem/private cloud?
Based on your current story my first guess would actually be a faulty VPN configuration, but without a more thorough understanding of your setup this sounds like a difficult to diagnose issue.
Since you are able to reach the endpoint from your local pc, I personally doubt the issue is with the endpoint itself here.
Edit: out of curiosity, I wrote my own .Net extension to replicate your attempt and I did receive a successful response when pinging 8.8.8.8 from my personal OutSystems environment. So I think it's safe to assume that on a default OutSystems configuration, pinging should not be blocked. Is it possible that you're running a on-prem/private cloud OutSystems instance and some configuration that your company made is blocking the ping attempt?
Thanks, that is really helpful information, I'll reach out to the support and ask if there is anything that could be blocking my pings.
Previous tools that have succeeded with a connection has been through regular rest requests from non-extension modules. I'm trying to set up a new tool to access shared printers within my network, which should just access them normally as there aren't even any authorization required for these specific printers.
I'll try to keep this post updated if the support finds any issues in case someone stumble upon this in the future