CATIA network license server & windows firewall 1

[tiuk]

Hello, I am trying to move a CATIA installation from a nodelocked license to concurrent. I have set up the network license server and central registry server on a Windows Server 2008 machine with the default ports (1515 for network and 10999 for central registry).

When I run the Basic License Tool on the client workstation (which I have configured as a network client with direct binding) it cannot see the license server on the network. I tried disabling the Windows Firewall on the server and the client was able to connect to the server.

The thing is, I have ports 1515 and 10999 forwarded on the firewall, so disabling it shouldn't have allowed it to work (it should have already). Are there any additional ports that CATIA may be using that I will have to forward? This is quite frustrating, and I know I'm close (probably missing something simple).

If anyone has any ideas I would love to hear them. Thanks

 

[PeterGuy]

You don't need central registry server unless you are using high availablity licencing and this is only supported if all the servers in the cluster are on the inside of a firewall. Your problem here is not reading the documentation, in order to make LUM work through a firewall you need to control the client port. In normal LUM communication the Client contacts the server on udp 1515, comunication in the other direction occurs on a dynamically allocated port so it is different every time. To control this you need to declare the IpAuthPort in the [iFOR/LS NCS-Server] section of the i4ls.ini file in both the client and server this will force the reverse communication to occur on the specified port (usually 1516). IpAuthPort cannot be set via the LUM configuration tool you have to do it directly in the ini file found here C:\Documents and Settings\All Users\Application Data\IBM\LUM on windows systems

 

[tiuk]

Thank you for your response, sounds like I should be able to get it up and running. I will give it a try tomorrow and post back with my results.

Thanks again!

 

[tiuk]

Sure enough, specifying an IpAuthPort and forwarding it solved the problem. Thanks again PeterGuy.