If the program you are running under FireDaemon Pro control binds to a socket, is relatively straight forward to determine what what protocol, address or port the program is listening on. First off, you need to obtain the Process ID (PID) of the service in question. Please consult this article to determine how to obtain the PID of a specific service.
Once you've obtained the PID, open an elevated command prompt and type:
netstat -ano | find "LISTEN" | more
The output will look similar to below. The first column is the protocol, second column is the binding, and last column is the PID. Scroll through the lines in the state LISTENING and match the PID. Note, this only works if you program is listening on a TCP port.
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1288 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:902 0.0.0.0:0 LISTENING 5952 TCP 0.0.0.0:912 0.0.0.0:0 LISTENING 5952 TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING 10244 TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:7680 0.0.0.0:0 LISTENING 3800 TCP 0.0.0.0:20604 0.0.0.0:0 LISTENING 5076 TCP 0.0.0.0:20604 0.0.0.0:0 LISTENING 5076 TCP 0.0.0.0:27036 0.0.0.0:0 LISTENING 16916 TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING 960 TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING 616 TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING 1640 TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING 1680 TCP 0.0.0.0:49668 0.0.0.0:0 LISTENING 4368 TCP 0.0.0.0:49673 0.0.0.0:0 LISTENING 936 TCP 127.0.0.1:3766 0.0.0.0:0 LISTENING 9400 TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING 4640 TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING 5984 TCP 127.0.0.1:6379 0.0.0.0:0 LISTENING 5548 TCP 127.0.0.1:9080 0.0.0.0:0 LISTENING 5468 TCP 127.0.0.1:9089 0.0.0.0:0 LISTENING 5420 TCP 127.0.0.1:27060 0.0.0.0:0 LISTENING 16916
Alternately you can type:
netstat -ano | find "17252"
This will give you a listing for that PID only and TCP, UDP, IPv4, IPv6 protocols, and ports. For example:
UDP 0.0.0.0:25001 *:* 17252 UDP 0.0.0.0:27015 *:* 17252 UDP 0.0.0.0:51980 *:* 17252 UDP [::]:25001 *:* 17252