Remote Command Console

Most ORACLE database administration utilities from ORACLE corporation are constructed in a manner such that they support use from a GUI and a command-line (such as SQL*Plus, Import, Export, SQL*Loader, Instance Manager, etc.). Also, most Windows NT tasks that would normally be performed locally in a point and click manner also have their command line equivalents. This is beneficial: tasks using utilities with command line equivalents can be scripted where appropriate, as well as the commands issued remotely rather than locally at the server console.

The most obvious choice for obtaining a remote command line is, of course, TELNET. By default, Windows NT does not include a TELNET service (although NT and Win95 both provide a TELNET client by default). There is a TELNET server included with the NT Resource Kit, but this particular application poses some concerns in that it does not support multiple simultaneous users without allowing certain security exposures. A variety of third-party TELNET servers are available, and most them are quite inexpensive and work very well. However, there is another utility called the "Remote Command Server" that is included with the NT Resource Kit that may satisfy the remote command-line need without additional purchases.

The remote command server consists of two components: the RCMDSVC.EXE (an application that runs as a service on the remote machine) and the RCMD.EXE (a simple command-line client application). The remote command server has some advantages in that it has a very small footprint on the server, and supports NT authentication: the user can simply launch the RCMD.EXE and supply the server name with no need to enter a userid and password. The user must have interactive login privileges on the remote machine since this approach, like TELNET, is the equivalent of typing at a command-line prompt during a local login at the server console. This application tends to work very reliably, and presents no unusual security concerns. Please see the documentation included with the NT Resource Kit for installation instructions.

Both TELNET and Remote Command Server sessions will work from NT Workstation or Windows95 PC's (this is not necessarily true of some of the included GUI remote management tools). Both have low bandwidth requirements, making them very useful for work over dial-up connections. Note that if a GUI application is started through use of a remote command-line session, the GUI will not display back to the client; rather, the GUI screen will appear on the console where it is not accessible remotely. If or when this unintentionally occurs, a new command-line session can simply be started and a KILL command issued against the previous session.