This problem still occurs with one machine when IPv6 is off. It happens to be my main workstation.
The current issue is the Thunderbolt cable connecting my workstation and the FM Servers to allow for TDM administration. OSX is assigning an IP address to the Thunderbolt connection as well. So I actually had Ethernet IPv4 + IPv6, and Thunderbolt IPv4 addresses for the same FM client machine. I could also have IPv6 for the Thunderbolt connection as well.
The issue is that FMP14 will not regularly use the same IP address in the launch center so this is causing the license conflicts. The launch center still has some issues with connecting by either Ethernet IPv4, IPv6 or TBolt depending on what mood it is in. If you opened a file using the Ethernet IPv4 address and then the next time you go to the launch center it decides to use the TBolt IPv4 or Ethernet IPv6 address you are pretty stuck unless you go into to favorites and add a primary one and only use that connection. FMP/FMPA should be consistently looking for the server at the same IP address to eliminate these license conflict problems. This seems like a bit much to have to work around and the conflict shutdowns are not graceful in any way.
Thank you for your posts and link.
Our Development and Testing departments are aware of this issue with mixing and matching IPv4 and IPv6 addresses being recognized as different machines. I have attached both forum threads to the original report. When more information becomes available, I will post again.
It is good to hear you guys are working on it. I actually reported this issue along side a different launch center problem during ETS testing and it was dismissed at that time. I hope this gets worked out soon. If you have a headless Mac server using TDM it swaps the IPv4 addresses back and forth.
Turning off IPv6 on the server fixes the IPv6 mixup but not the IPv4 one.