Re: IDL licenses thru a tunnel? [message #34457 is a reply to message #34388] |
Fri, 14 March 2003 08:41   |
Anthony J. Ferro
Messages: 6 Registered: February 2002
|
Junior Member |
|
|
Craig Markwardt wrote:
> "Anthony J. Ferro" <tferro@as.arizona.edu> writes:
>
>
>> I'm trying to figure out a way to provide access to my IDL license
>> server for our folks outside of our building's firewall (other
>> buildings/classrooms on campus, home, other institutions, etc).
>> I don't want to poke a generic hole in our firewall because of
>> a) the security risk of another hole, and b) I don't really want
>> to provide IDL to everyone on the internet (sorry). What I've
>> been trying is to set up an ssh tunnel using something like:
>>
>> ssh -f -N -L 1700:localhost:1700 username@idlserver
>>
>> This _almost_ works. There is some communication going on
>> between the client and the server, but the license request
>> fails. I can tell that some communication occurs because the
>> error message includes the name of the server (the client
>> license file has "localhost").
>
>
> That's a pretty neat idea, and it works for me! Of course, on the
> client, you need to set the license server:
>
> setenv LM_LICENSE_FILE 1700@localhost
>
> Craig
>
Hmmm, I hadn't tried that, but it doesn't work for
me either. The problem seems to be that my server returns
it's own name (eg. idlserver) instead of "localhost" and
things fail at that point. Maybe if I get creative with
my "/etc/hosts" file.....
- Tony Ferro
|
|
|