They both behaved the same way but I'll show the command I used in the Cygwin case. I tried it using both PuTTY and the ssh client in Cygwin.
#Flexlm port windows
I'm using a Windows system so perhaps that makes a difference. It looks to me like you did your test using a Linux system to run the compiler. In this case, you need to do something like this on Machine B: Machine A (license manager) Machine C Machine B (running icc) 2) B can connect to C via SSH, and C can connect to A. In case that 1) Machine B can't connect to machine A via SSH.
#Flexlm port license
On machine A, I can see license was checked out and then checked in.ĩ:53:02 (INTEL) OUT: "ID8CBD2CF" machineBĩ:53:02 (INTEL) IN: "ID8CBD2CF" machineB Intel(R) C Intel(R) 64 Compiler XE for applications running on Intel(R) 64, Version 13.1.3.192 Build 20130607Ĭopyright (C) 1985-2013 Intel Corporation. I set up a port forwarding on Machine B with the following command: Should I open a different thread about this? How does that work? In my situation that would be a feasible solution as we have enough licenses to cover the on campus students and only a couple of students for whom the off campus access is essential. In any case I'd be interested to hear more about this "borrowing" of a license.
I have heard (not sure if it's true) that SSH tunnels can't forward UDP traffic but it sounds like that's not an issue. but it's a general mechanism that applies, as far as I know, to any TCP connection.Īlso the fact that flexlm uses TCP is a good thing. I use this routinely to access web servers from off campus that are not visible through the firewall. Any process that connects to localhost on that port has its traffic forwarded over the SSH connection (encrypted) and from there to the final endpoint via the Linux system. In the meantime on my system, off campus, a local port is opened that represents the remote connection. The Linux system establishes a connection with the host behind the firewall, in this case the license manager. Could that be an issue? Perhaps there is some other, nicer way to accomplish what I'm trying to do.įirst I want to point out that getting the remote Linux machine to forward packets is exactly what an SSH tunnel does. Is what I'm doing possible? I've heard that the SSH protocol does not support forwarding of UDP traffic. I would have expected (was hoping) that USE_SERVER-tunnel.lic as above would have worked when I'm off campus, with the tunnel running of course. The file USE_SERVER.lic is the "regular" file that specifies the server directly. C:\Program Files\Common Files\Intel\Licensesġ> 5. C:\Program Files (x86)\Common Files\Intel\Licenses\USE_SERVER.licġ> 4. C:\Program Files (x86)\Common Files\Intel\Licenses\USE_SERVER-tunnel.licġ> 3. License file(s) used were (in this order):ġ> 2. The error message goes on to list the license files it attempted to use: However when I attempt to use any of the Parallel Studio components I am told, for example, "Error: A license for CCompW is not available now (-96,7,11001)." (This was an attempted compile with the Intel C++ compiler). I also tried using LOCALHOST for the host name. lic file in "C:\Program Files (x86)\Common Files\Intel\Licenses" named USE_SERVER-tunnel.lic. From what I can tell the tunnel itself appears to be fine.
My attempts to set this configuration up on my own machine have so far failed. My hope was that they could use an SSH tunnel to allow their local installation of Parallel Studio to access the campus license server (the license server is not directly visible through the college's external firewall). They do, however, have accounts on a Linux system maintained by my department. Some of my students spend a considerable amount of time off campus and two of them, in fact, basically can't physically reach campus at all. Accordingly I have a license grant and I have set up a license server on campus that works fine. I'm teaching a course in parallel programming and I hope to use Intel Parallel Studio for Windows as part of my course.
0 kommentar(er)
