-1

And provides the binding to processes. I know netstat does that, but I am interesting in COM so I can access this information remotely using DCOM, and set permissions effectively.

Ideally, I would use WMI. I inspected (almost?) all the tables and couldn't find one that contains this information.

Thanks.

user2679290
  • 144
  • 9

1 Answers1

0

You'd need to write a component that sits on each machine, and when launched through DCOM it would create a child console process but redirect its output to a pipe, then within that child process launch netstat. Then you could parse through the output in the pipe. I did something similar to capture console output for a legacy app running on a remote machine, so it is possible.

DCOM security is such a mess though that you may be better off making it a regular app that launches on startup, or a service that listens for activation commands using standard tcp/ip and sends the results back similarly.

kabekew
  • 16
  • 1
  • Thanks . But making an component is a possibility I want to avoid since it is required to be tested and deployed on different machines. Although , it is just a call to netstat. – user2679290 Apr 23 '15 at 15:36