6 Replies Latest reply on May 20, 2011 6:58 AM by b1tm4p

    Getting External Process to work with plink.exe

    b1tm4p

      I have been successful in configuring ipMonitor to use psexec.exe on Windows servers to start a remote program and get the result back to ipMonitor.

      In the manual I read the same should be possible on Linux servers using the plink.exe utility. I installed plink on the ipMonitor server and from the commandline on the server it is working fine like this:

      plink.exe USER@SERVER -pw PASS -ssh ./test.sh

      But when I configure ipMonitor like this:

      Monitor Name: External Linux Process
      Executable Name: plink.exe
      Directory: C:\Windows\System32
      Command Line Parameters: USER@SERVER -pw PASS -ssh ./test.sh
      Startup Directory: C:\
      Credential for Monitoring: Administrator Credential

      This does not work, the error is: Last Result:Access rights are insufficient

      Any advice, would be welcome,

      Thanx,

      Martijn

        • Re: Getting External Process to work with plink.exe
          Fodome

          Hi Martijn,

          When you run the following command, what directory do you run it from:

          plink.exe USER@SERVER -pw PASS -ssh ./test.sh

          What directory is plink.exe located in?

          Thanks,

          Chris Foley | Support Specialist
          SolarWinds | IT Management, Inspired By You
          Support:866.530.8040 || Fax:512.857.0125

            • Re: Getting External Process to work with plink.exe
              b1tm4p

              Hi Chris,

              As stated in the manual I put plink.exe in C:\Windows\System32

              Directly called from the commandline on the server (logged in as administrator) it is working. It is a Windows 2008 Server.

                • Re: Getting External Process to work with plink.exe
                  Fodome

                  Martijn,

                  Is ipMonitor hosted on Windows 2008 64-bit or 32-bit?  If it is 64-bit, plink.exe will need to be copied to c:\windows\syswow64\ as all calls to c:\windows\system32\ by 32-bit applications are redirected to syswow64.

                  It is worth noting here that ipMonitor is currently unsupported on 64-bit operating systems.

                  Sincerely,

                  Chris Foley | Support Specialist
                  SolarWinds | IT Management, Inspired By You
                  Support:866.530.8040 || Fax:512.857.0125

                  1 of 1 people found this helpful
                    • Re: Getting External Process to work with plink.exe
                      b1tm4p

                      Hi Chris,

                      Thanks, after moving plink.exe to the syswow64 folder it is working now! So issue is solved. Good you mentioned that 64 bit is unsupported, we were not aware of that.

                      For me it's somewhat of a limitation that IPmonitor can only handle exit codes. Are there plans for the future that make it possible to return an environent variable from an external proces on an external host? Would be a nice feature.

                      • Re: Getting External Process to work with plink.exe
                        b1tm4p

                        I might have celebrated to early, because after the metric was working fine for 10 minutes (I got the response I expected) It has now stopped working with error: The remote device timed out before sending a response

                        However if I call my script from the server directly, it is still responding fine. Any idea what could be the cause of this?