You can ping any IP address anywhere that network routing and firewalls allow, but that doesn't mean it's connected to your computer and so won't show up in netstat.
Netstat shows which TCP ports have got active connections (i.e. machines connected, not just machines which might or which used to connect). Ping uses ICMP (sometimes UDP) and doesn't rely on TCP ports.
In your case, it sounds like the application is not connecting but the operating system is still up and running, so you can ping the machine (because that's the OS responding), but the application can't connect to your server either because it's not running, or because it's got other issues.
If you can't connect back to it remotely and log in to check the app you'll need to send someone to it.
You also asked,
I have another question. If the outstation comes online but does not
bind to the port 6102 will it not be shown in netstat? I think I know
the answer here.
We don't know what OS or application this 'outstation' is running, but it's applications which connect to ports, and yet it's operating systems (or rather, components of those operating systems) which bring up and manage the network. So if you application connects, yes you'll see it. But if the outstation boots and brings up the network it won't do anything until the running application tries to do anything, if it crashes, then you'll see nothing at your end. Network and application are separate.
Last example, assuming your computer can connect to the internet, you can ping www.google.com but it doesn't mean www.google.com has ever tried to connect to your computer.
Best Answer
Presumably the error message indicates that some of the calls that
netstatwas making togetnameinfo(3) failed.Ie, when
getnameinfowas trying to look up the hostname corresponding to an IP address or the service name corresponding to a port number something failed in an unexpected manner.(By default
netstatshows names for both addresses and ports, also see the-noption)If you care to try to track down what specifically is happening, it may be more helpful to see the errors in context (ie, drop the rest of the pipeline).