Remote Command Limitations

Only non-MS-DOS programs using STDIN/STDOUT/STDERR for input/output will function redirected across the network. Programs that use the Win32 Console API will not work correctly. MS-DOS programs will not work. Generally, any programs that use on-screen character mode windows or cursor manipulation (such as screen-mode editors) will not work.
It is not possible to connect with the user's credentials, from the remote shell, to file resources remote to the target computer. The only way to connect is to specify a user name and password with the NET USE command (see NET USE help). Due to the way the NET USE command works, it is not possible to be prompted for the password; it must be entered on the command line, and, in any case, is then sent in clear text across the network.
Executing START on the remote computer will result in starting detached processes. These processes are not "connected" (that is, no input or output is possible), and will not be stopped when you exit the remote command shell. This wastes resources on the remote computer.
The standard users environment is not set up in the remote command shell. Any environment must be set up explicitly during the command session.