Flexera Community Forums - FlexNet Licensinghttps://community.flexerasoftware.com/
enTue, 14 Aug 2018 21:41:14 GMTvBulletin60https://community.flexerasoftware.com/images/misc/rss.pngFlexera Community Forums - FlexNet Licensinghttps://community.flexerasoftware.com/
Strange issue with FLEXnet DChttps://community.flexerasoftware.com/showthread.php?226406-Strange-issue-with-FLEXnet-DC&goto=newpost
Mon, 06 Aug 2018 14:00:01 GMTHello,
So I have had all my new outback stuff installed for about 2 weeks now. Yesterday I woke up and my mate 3 display was blank (off-no power). Strange since it had been working fine for 2 weeks and was ok when I went to sleep. After doing a bunch of troubleshooting, I figured out that if i...Hello,

So I have had all my new outback stuff installed for about 2 weeks now. Yesterday I woke up and my mate 3 display was blank (off-no power). Strange since it had been working fine for 2 weeks and was ok when I went to sleep. After doing a bunch of troubleshooting, I figured out that if i disconnected the CAT5 cable from the "FLEXNET-DC" it came back on and everything was fine. Furthermore, if I put the cat5 cable back into the FLEXNET, the moment I click in the cable, the FM80 resets itself. Obviously there is something seriously wrong with it. It scares me to think that a bad flexnet could effect the FM80 in some way. Has anyone seen this before? Thoughts?

I'm running a CAD application that has a license tied to a MAC address on a NIC that I use solely as a hardware dongle. Now that I rebuilt my CAD station, the installation procedure for the license manager FLEXnet insists on demanding a license for the ethernet-connected NIC rather than the "dongle".
I could of course remove the NIC that is connected to the network and use the "dongle" NIC for that instead, or I could ask for a new license file referring to my network NIC (I'm not sure they allow that), or I could probably find a crack for bloody license manager to be done with it - but I would highly prefer to get it to work properly as it is intended instead. Is there some way I can assign which NIC is "primary" and which is "secondary" in Windows 2000? Because it seems as if the blasted license manager just takes a quick gander at the PCI bus and settles for the first thing it sees.

Thank you.
]]>FlexNet Licensingricardobrookshttps://community.flexerasoftware.com/showthread.php?226405-FLEXnet-config-with-dual-NIcsUndocumented Result Codehttps://community.flexerasoftware.com/showthread.php?226404-Undocumented-Result-Code&goto=newpost
Mon, 06 Aug 2018 13:46:48 GMTI think given the nature of this being 'Undocumented' I suspect I am chasing my tail but has anyone come across a Undocumented Result code 51315 and if so how did you fix it?
]]>FlexNet LicensingConnorhttps://community.flexerasoftware.com/showthread.php?226404-Undocumented-Result-CodeChecking out licenses from vendor deamon tcp porthttps://community.flexerasoftware.com/showthread.php?226383-Checking-out-licenses-from-vendor-deamon-tcp-port&goto=newpost
Thu, 26 Jul 2018 05:45:09 GMTI'm running lmgrd and a vendor daemon and can check out licenses from a tcp port specified on SERVER line (e.g. 27000).
But I can also check out licenses from vendor tcp port which is chosen by OS by default on starting the license daemon.
Here a question. Is this an expected behavior?
If it is an expected one then can we avoid this feature rather than closing the port by firewall?
The version is Windows v11.13.
]]>FlexNet Licensingnsr250sehttps://community.flexerasoftware.com/showthread.php?226383-Checking-out-licenses-from-vendor-deamon-tcp-port