I am new to SysInternals tools, and I have a question whether there exists a workaround.
I need to launch an executable that is a command-line console to some network functions in target-LAN environment. It works fine until I issue the "online" command at that tool which basically connects it to a server.
From the remote administrative host, I use the PsExec to call that network tool locally. It gives me the initial output just fine. However, when I issue the "online" command, the PsExec console stops providing me any output, but I can clearly see the process is still running.
I assume that PsExec hooks up to a process and redirects output to the actual user. However if the target executable needs to interact with network on it's own, PsExec cannot handle such "nested" connection.
Am I correct about this assumption? Is PsExec working fine for you if you invoke a network-interactive tool?
Since the target software is proprietary, I am unable to share it with you. I hope you would be able to advise on that topic despite of this.
If not, let this thread die silently :-)
Best regards, Alex