We have a client that has a need to configure a child beacon to communicate over a different port than standard. Trying to find out if anyone has done this before to share their experience before too many cycles are spent trying to prove this out. In addition to the child beacon to the parent, agents to the child beacon.
Nov 19, 2019 09:29 AM
Nov 21, 2019 02:48 PM
This would likely require that IIS on the inventory beacon be reconfigured to accept connections on a different port.
Nov 19, 2019 10:27 AM
Nov 19, 2019 05:45 PM
Nov 21, 2019 02:48 PM
Thanks all. We are working with a DoD customer that wanted to isolate traffic and wanted some official verbiage stating the directions of communication required for purpose of opening up the firewall. This forum helped. I changed the IIS bindings, and updated the config file on the child beacon to reflect the parent port change. After everything was restarted the child was reporting status to parent which to me meant a successful test.
Nov 21, 2019 02:55 PM
It sounds like you may have what you need now, but if you want something more formal in relation to the direction of connections, take a look at the following online help topic: Ports and URLs for Inventory Beacons
Nov 21, 2019 09:18 PM