| Re: IDL licenses thru a tunnel? [message #34422 is a reply to message #34388] |
Tue, 18 March 2003 06:53   |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
h_chapman@fastmail.fm (Henry) writes:
>
> Another interesting thing I learned from the globetrotter site is that
> if you set the SERVER port to 27000 instead of idl's usual 1700, then
> you only need @hostname instead of 1700@hostname for your
> LM_LICENSE_FILE. 27000 is the default. So one of many ways of
> tunnelling (this works for me) is:
>
> export LM_LICENSE_FILE=@localhost
> ssh -f -NL 27000:localhost:1700 myserver.com
> ssh -f -NL 59000:localhost:59000 myserver.com
> idl
>
> type everything as written, except for myserver.com, which is the
> remote machine running the license server.
Hmmm, I still find that this give the same kind of server lookup error
that the original poster was reporting.
Because the *server*'s configuration file contains the name
myserver.com, and reports that back to the client, the client will
attempt to make a connection to myserver.com no matter what, and this
will be blocked by the firewall. That's why I had to fiddle with the
/etc/hosts table.
Craig
--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
