from: "Monnier, Gary" <Gary.Monnier@xxxxxxxxx>
subject: RE: Help setting up RUNRMTCMD...
Is the remote command (REXEC) server running on the target system? A number of companies do not start REXEC for security reasons.
Newer versions of Windows don't even ship with a REXEC daemon, XP is the last one that did AFAIK. Luckily there is one included with Client Access, but it is an optional component that may not have been installed with the rest.
Default firewall rules will interere, as will any command that can try to prompt a user for anything, like needing a security confirmation before writing to a particular directory (even if it's jsut some default logging), etc. RUNRMTCMD can be a PITA to debug.
This message may contain confidential information and is intended only for the individual or individuals named. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message
is provided for informational purposes only.