I am running lmadmin and need to specify the daemon port so that it can be opened for the firewall. But when the port is specified (from Vendor Daemon Configuation Tab) ... upon reboot ... this happens ...
1. it appears that the specified port is ignored and a port is assigned (just as if the use default port is selected).
2. If one goes to Vendor Daemon Configuration tab one will see a port different than the specified.
3. If one adminiisters the daemon ... he will find it remembers the port which was selected.
4. No licenses will be available ...
So I am not sure if this is bug in lmadmin or something to do with the vendor daemon. If anyone has ever seen this and has a solution ... I would sure appreciate your guidance.
I am experiencing a similar problem. When I specify a port for a particular daemon (we serve multiple), it has no bearing on the actual port that gets used (thanks for playing). A random port is used and I have to manually change the port number for every machine that requires that license. Serious PITA.
In most cases, the client daemons have been updated with a Flexnet 11.xx compatible server. Unfortunately, one vendor which shall remain nameless (WR), doesn't fully support 11.xx. Their latest daemon version appears to be 9.5 compliant only.
To me, it is a problem that could be solved by either vendor. But it makes more sense on the part of the server vendor to make their future updates to be 'fully' compatible with legacy clients.
One solution would be to go back to an older license server for that one license.
