- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Forum
- :
- FNMS Beacon/Agent Port change
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you need further clarification please post back and I’ll see if we have some screenshots available.
If the solution provided has helped, please mark it as such as this helps everyone to know what works.
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This would likely require that IIS on the inventory beacon be reconfigured to accept connections on a different port.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you need further clarification please post back and I’ll see if we have some screenshots available.
If the solution provided has helped, please mark it as such as this helps everyone to know what works.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
