Installation & Licensing
Welcome to Autodesk’s Installation and Licensing Forums. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Inventor license server and client behind a NAT

18 REPLIES 18
Reply
Message 1 of 19
manu1107
2200 Views, 18 Replies

Inventor license server and client behind a NAT

Hello We have a license server for Inventor. It works fine for most clients, however, any client that is behind a NAT cannot get a license. Attached is a tcpdump trace gathered on the outer interface of the NAT. 192.0.2.96 is the NAT external IP address 192.0.2.64 is the inventor license server
18 REPLIES 18
Message 2 of 19
manu1107
in reply to: manu1107

It seems the tcpdump trace wes not included. Second try.
Message 3 of 19
manu1107
in reply to: manu1107

16:43:37.924592 IP 192.0.2.96 > 192.0.2.64: ICMP echo request, id 768, seq 23567, length 25
16:43:37.925814 IP 192.0.2.64 > 192.0.2.96: ICMP echo reply, id 768, seq 23567, length 25
16:44:29.160246 IP 192.0.2.96.47067 > 192.0.2.64.27000: S 611384859:611384859(0) win 65535
16:44:29.160326 IP 192.0.2.96.47938 > 192.0.2.64.27001: S 3672465152:3672465152(0) win 65535
16:44:29.160389 IP 192.0.2.96.52839 > 192.0.2.64.27002: S 2792601837:2792601837(0) win 65535
16:44:29.160488 IP 192.0.2.96.46835 > 192.0.2.64.27003: S 1547684253:1547684253(0) win 65535
16:44:29.160613 IP 192.0.2.96.48007 > 192.0.2.64.27004: S 577803324:577803324(0) win 65535
16:44:29.160740 IP 192.0.2.96.51105 > 192.0.2.64.27005: S 342466115:342466115(0) win 65535
16:44:29.160881 IP 192.0.2.96.45055 > 192.0.2.64.27006: S 3837643983:3837643983(0) win 65535
16:44:29.161008 IP 192.0.2.96.54521 > 192.0.2.64.27007: S 782356508:782356508(0) win 65535
16:44:29.161143 IP 192.0.2.96.55762 > 192.0.2.64.27008: S 1385349619:1385349619(0) win 65535
16:44:29.161275 IP 192.0.2.96.50275 > 192.0.2.64.27009: S 2075883013:2075883013(0) win 65535
16:44:29.162227 IP 192.0.2.64.27000 > 192.0.2.96.47067: S 1484429029:1484429029(0) ack 611384860 win 8192
16:44:29.162237 IP 192.0.2.64.27001 > 192.0.2.96.47938: R 0:0(0) ack 3672465153 win 0
16:44:29.162261 IP 192.0.2.64.27002 > 192.0.2.96.52839: R 0:0(0) ack 2792601838 win 0
16:44:29.162271 IP 192.0.2.64.27003 > 192.0.2.96.46835: R 0:0(0) ack 1547684254 win 0
16:44:29.162280 IP 192.0.2.64.27004 > 192.0.2.96.48007: R 0:0(0) ack 577803325 win 0
16:44:29.162289 IP 192.0.2.64.27005 > 192.0.2.96.51105: R 0:0(0) ack 342466116 win 0
16:44:29.162298 IP 192.0.2.64.27006 > 192.0.2.96.45055: R 0:0(0) ack 3837643984 win 0
16:44:29.162307 IP 192.0.2.64.27007 > 192.0.2.96.54521: R 0:0(0) ack 782356509 win 0
16:44:29.162316 IP 192.0.2.64.27008 > 192.0.2.96.55762: R 0:0(0) ack 1385349620 win 0
16:44:29.162325 IP 192.0.2.64.27009 > 192.0.2.96.50275: R 0:0(0) ack 2075883014 win 0
16:44:29.162822 IP 192.0.2.96.47067 > 192.0.2.64.27000: . ack 1 win 65535
16:44:29.162970 IP 192.0.2.96.47067 > 192.0.2.64.27000: P 1:148(147) ack 1 win 65535
16:44:29.163836 IP 192.0.2.64.27000 > 192.0.2.96.47067: P 1:41(40) ack 148 win 64240
16:44:29.164431 IP 192.0.2.96.47067 > 192.0.2.64.27000: R 148:148(0) ack 41 win 0
16:44:29.186645 IP 192.0.2.96.58638 > 192.0.2.64.2080: S 1967694619:1967694619(0) win 65535
16:44:29.187529 IP 192.0.2.64.2080 > 192.0.2.96.58638: S 2112714379:2112714379(0) ack 1967694620 win 8192
16:44:29.188036 IP 192.0.2.96.58638 > 192.0.2.64.2080: . ack 1 win 65535
16:44:29.188159 IP 192.0.2.96.58638 > 192.0.2.64.2080: P 1:148(147) ack 1 win 65535
16:44:29.189152 IP 192.0.2.64.2080 > 192.0.2.96.58638: P 1:40(39) ack 148 win 64240
16:44:29.189808 IP 192.0.2.96.58638 > 192.0.2.64.2080: P 148:295(147) ack 40 win 65496
16:44:29.192130 IP 192.0.2.64.2080 > 192.0.2.96.58638: P 40:187(147) ack 295 win 64093
16:44:29.192772 IP 192.0.2.96.58638 > 192.0.2.64.2080: P 295:442(147) ack 187 win 65349
16:44:29.194862 IP 192.0.2.64.2080 > 192.0.2.96.58638: P 187:334(147) ack 442 win 63946
16:44:29.195983 IP 192.0.2.96.58638 > 192.0.2.64.2080: P 442:527(85) ack 334 win 65202
16:44:29.197202 IP 192.0.2.64.2080 > 192.0.2.96.58638: P 334:481(147) ack 527 win 63861
16:44:29.197893 IP 192.0.2.96.58638 > 192.0.2.64.2080: R 527:527(0) ack 481 win 0
Message 4 of 19
TravisNave
in reply to: manu1107

NAT should work fine.  Can you PING the server from behind the NAT?  You need to allow ports 2080 and 27000 thru the NAT forwarded to the NLM server.  No other protocols should be using this ports anyway.  You can either point to the NAT and port forward or open the ports and access to the server thru the NAT.  You might need to increase the FLEXLM_TIMEOUT system variable with the extra hops.

 

Let me know what errors or problems you are getting. 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 5 of 19
manu1107
in reply to: TravisNave

Thank you for your reply The tcpdump trace I posted shows that the client can ping the server, and then establish connections on TCP ports 27000 and 2080. The server drops the connections after a few packets have been exchanged. About FLEXLM_TIMEOUT, is it relevant for intra-LAN usage? There are 3 routers in between client and server, but ping reports that latency does not exceeds 3 ms.
Message 6 of 19
TravisNave
in reply to: manu1107

It certainly wouldn't hurt to set the variable.  You can at least try it as a test. 

 

You can also check port connectivity from the client to the server by using Internet Explorer (not 3rd party browsers.)

 

Simply open IE and go to the following address ports:

 

http://servername:27000 - LMGRD Master Daemon

http://servername:2080 - ADSKFLEX Vendor Daemon

 

Just replace servername with the hostname or IP addres of your NLM server.  When you do so, you should receive a page with jargon that looks similar to this on both:

 

Wê-60Wê-60Wê-60Wê-60Wê-60Wê-60Wê-60

 

This will at least verify that there is no connectivity, firewall, or other problem impeding your path.  If you get a 'page cannot be displayed' error, then you should probably look into it. 

 

Assuming this works, try setting the FLEXLM_TIMEOUT system environment variable to 1000000 and give it another test. 

 

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=7574782&linkID=9240617

 

Are you getting any specific error at the client?



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 7 of 19
manu1107
in reply to: TravisNave

The tests on http://server:2080 and http://server:27000 are fine, we get binary data.

Setting FLEXLM_TIMEOUT as suggested does not change anything.

When the client tries to get a license, it gets an error saying network licence manager could not obtain a valid license. It reports error -15.570.10035 (sorry I should have reported that at once)

Message 8 of 19
TravisNave
in reply to: manu1107

Try setting the LICPATH.LIC to the IP address of the server.  If you're getting -15 error, it is usually connectivity.  Since your ports to 2080 and 27000 are working, there is something else going on.  You can try increasing your FLEXLM_TIMEOUT by more as well.  Each million delays the timeout by one second. 

 

What do you get when you PING the server?  IPv4 of the NAT or the NLM Server?  Or do you get IPv6?



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 9 of 19
manu1107
in reply to: TravisNave

I have to correct a previous statement (I am not the end user, I forward back and forth, and sometime some information gets misquoted). The -15 error is a rare thing, and I am now convinced it happened some day the licence server was down.

 

However, it still does not work,it is just taht most of the time there is no error message. The user gets three FlexNet Licence Finder dialogs, one asking if a licence server IP or a licence file path is to be entered. The second dialogs asks for the licence server IP (setting LICPATH.LIC  does not alter that behaviour), and the third asks to clock the "finish" button. When we do that, we immediatly go back to the first dialog without any error reported.

 

Increasing FLEXLM_TIMEOUT does not change anything. If the licence server is down we get the -15 error.

 

When sending a ping to the licence server, we get a reply from the licence server itself, not from the NAT.

Message 10 of 19
TravisNave
in reply to: manu1107

It's good that you get a ping response from the NLM server.  That proves connectivity.  You might also set the ADSKFLEX_LICENSE_FILE variable with the @servername.  You can also use the IPv4 address here too. 

 

My NLM server is behind a NAT, so I know this works. 

 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 11 of 19
manu1107
in reply to: TravisNave

With your remark about the flexlm server behind a NAT makes me aware that my title was not wisely worded. My licence server is not behind a NAT. The client is behind a NAT. Perhaps the title should have been "Inventor license server, and client behind a NAT" (note the comma after server)
Message 12 of 19
TravisNave
in reply to: manu1107

Shouldn't really matter who is behind what.  So long as there is connectivity, it could be a NAT, Router, VPN, or a can and string.  If you can PING the NLM and have access to ports 2080 and 27000, then you should be able to get a license.  Most often the problem is either Firewall or timeout. 

 

 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 13 of 19
manu1107
in reply to: TravisNave

 
Message 14 of 19
manu1107
in reply to: TravisNave

For some reaseon I have trouble to grasp, my message is displayed without content. Here is it again.

 

It is nice to know it should be working, but it would be even nicer to have this actually working.

 

We know that ping, TCP 2080 and TCP 27000 connectivity is fine. However, the client still cannot get a licence, it just loops on the dialogs about selecting a licence server/file. ADSKFLEX_PATH did not help.

Message 15 of 19
TravisNave
in reply to: manu1107

Double check the client and make sure that the system environment variables are set correctly for FLEXLM_TIMEOUT and for ADSKFLEX_LICENSE_FILE

 

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=7574782&linkID=9240617

 

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=8385605&linkID=9240617

 

ADSKFLEX_LICENSE_FILE.JPG

 

Make sure @SERVERNAME is the hostname of your NLM server.  These two variables solve the license finder box almost 99% of the time based on your description.

 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 16 of 19
manu1107
in reply to: TravisNave

Just to make sure: once the variable are set, I should not see the three dialogs of licence finder anymore, right? If I still have them, it means the variable is not set or is  not taken into account?

Message 17 of 19
TravisNave
in reply to: manu1107

If correctly set on the client, your problem should be resolved if connectivity is indeed working. 



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files
Message 18 of 19
manu1107
in reply to: TravisNave

Sure, but will setting the variable make the licnece finder windows disapear?

Message 19 of 19
TravisNave
in reply to: manu1107

That's the hope!  Smiley Very Happy



Travis Nave Send TravisNave a Private Message                                             Need help in your post? Mention me with @TravisNave



My Expert Contributions to the
Autodesk Forums:
FLEXnet License Admin | MSI Cleanup Utility | .NET Framework Cleanup Tool | IPv6 NLM Fix | adskflex.opt Options File | Combine .LIC Files

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report