Remote Command Control  
 

Execute commands on a server or establish an interactive terminal session.

Reference

Control Information

Object Name RshClientCtl.RshClient
File Name CSRSHX10.OCX
Version 10.0.1468.2520
ProgID SocketTools.RshClient.10
ClassID 966D11BD-ABD2-40BA-8084-2DFC54713334
Threading Model Apartment
Help File CST10CTL.CHM
Dependencies None
Standards RFC 1282

Overview

The Remote Command control is used to execute a command on a server and return the output of that command to the client. This is most commonly used with UNIX based servers, although there are implementations of remote command servers for the Windows operating system. The control supports both the rcmd and rshell remote execution protocols and provides functions which can be used to search the data stream for specific sequences of characters. This makes it extremely easy to write Windows applications which serve as light-weight client interfaces to commands being executed on a UNIX server or another Windows system. The control can also be used to establish a remote terminal session using the rlogin protocol, which is similar to the Telnet protocol.

This control should not be used when connecting to a server over the Internet because the user credentials are sent as unencrypted text. For secure remote command execution and interactive terminal sessions, it is recommended that you use the SocketTools Secure Shell (SSH) control instead.

Requirements

The SocketTools ActiveX Edition components are self-registering controls compatible with any programming language that supports COM (Component Object Model) and the ActiveX control specification. If you are using Visual Basic 6.0 you must have Service Pack 6 (SP6) installed. It is recommended that you install all updates for your development tools.

This control is supported on Windows 7, Windows Server 2008 R2 and later versions of the desktop and server platforms. If you are using Windows 7, you must have Service Pack 1 (SP1) installed as a minimum requirement. It is recommended that you install the current service pack and all critical updates available for the operating system.

This product includes both 32-bit and 64-bit ActiveX controls. Native 64-bit CPU support requires the latest 64-bit version of Windows 7, Windows Server 2008 R2 or later versions of the Windows operating system.

Distribution

When you distribute an application that uses this control, you can either install the file in the same folder as your application executable or as a shared component in the appropriate system folder. If you install the control in the system folder, it is important that you distribute the correct version for the target platform and it must be registered. If you install the control in the same folder as your executable, it is recommended that you use registration-free activation or COM redirection to ensure that the correct version of the control is loaded by the application.