comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDL licenses thru a tunnel?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL licenses thru a tunnel? [message #34431 is a reply to message #34388] Mon, 17 March 2003 18:49 Go to previous messageGo to previous message
Craig Markwardt is currently offline  Craig Markwardt
Messages: 1869
Registered: November 1996
Senior Member
Randall Skelton <rhskelto@atm.ox.ac.uk> writes:
> The second port I tunnel seems to be required for the information being
> passed back from the IDL license server. I basically sniffed packets
> while in my office to and learned that IDL was routing packets back on
> 4100 and not 1700. I have no idea how standard this is but it is
> definitely required for my setup.

I am following up on this, since I suddenly do have a need to tunnel
to a license server from a remote location.

I found out that it most definitely was *not* working for me, the way
I said it was. I was experimenting on a local machine that was within
the firewall, and that was not a good enough test.

Randall is right, you need to add another port to be forwarded, but
for me it was not 4100, it was 32769. I am not sure if this is
random, or if it is built into the license server. [ but neither 4100
nor 32769 seems random. ] This second port appears to be a another
layer of the licensing transaction that is required to let you run
IDL.



> Change your license.dat file to point to localhost rather than your usual
> license server.
>
> i.e.
> SERVER idl_license_server.domain 0#50##ae6#cf 1700
> becomes
> SERVER localhost 0#50##ae6#cf 1700

This still did not work for me. The reason is that at the second
layer of the transaction, the license file at the *server* is
consulted, not the local license file. So if the server is named
foobar.domain, it would have a license server file like:

SERVER foobar.domain XXXXXXXXXXXXXX 1700

The license server somehow reports the foobar.domain hostname back to
the IDL client, and unfortunately you are then in a world of hurt.
The local machine tries to connect to foobar.domain:32769 (in my
case), which is also blocked by the firewall.

The solution was indeed to mangle with the hosts table, and after that
things seemed to work alright.

Summary:
* port redirect 1700
* port redirect 4100 or 32769 or whatever, use netstat to find out
* setenv LM_LICENSE_FILE 1700@localhost (allows first level transaction)
* mangle "/etc/hosts" so that *server* license.dat server name is
aliased to 127.0.0.1 (allows second level transaction)

Now, wasn't that easy? How wonderfully useful IDL licensing is...
Harumphhh.

Craig

--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: "broken" scale in IDL plot
Next Topic: Using multiple top level bases created with GUIBuilder

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:43:15 PDT 2025

Total time taken to generate the page: 0.00460 seconds