The port setting (non-SSL) explicitly states "TCP Port"
SSL would be TCP as well.
Thanks for pointing that out (
Options > Media Network > Advanced). I believe this port would have to be set for Port Forwarding in the router firewall as well, in order to access the MC server from outside the LAN.
Example (attached below): For McAfee Total Protection, the five Firewall ports listed by Media Network are opened to two MC services. While I don't know if this is the minimum required set (can someone else answer that?)...
Answering my own question: For MC Remotes and clients within the LAN, the minimum required set of requested firewall open ports = THE EMPTY SET (except maybe UDP 1900, which is a UPNP port commonly used by other processes anyway).
That is, the McAfee settings shown in the OP are NOT required in my environment. I unchecked those McAfee firewall boxes, rebooted, confirmed they remain unchecked, and my MC remote apps and clients all continue to work just fine as of today!
Nevertheless, those five ports are in fact available to MC, as shown in MC's Media Network display window. As an independent confirmation, I run
netstat commands such as the following in an elevated Windows Command Window on the MC server:
netstat -ano | find "1900"
netstat -qbn -p TCP
Their output confirms (after decoding numerical PIDs with Task Manager if necessary): 1900 is UDP used by MC, and the other four ports are TCP used by MC. But as an end user, I don't have to setup my firewall to make it all work locally.
So far, a long-winded breath of fresh air for me