Using DOS-Based Remote Console


Choosing a Connection Type

You can run remote console sessions through a LAN or WAN connection, or via a modem or a null modem cable.


Running RCONSOLE Through a LAN or WAN Connection

To run a remote console session over a LAN or WAN connection you must do the following:

  1. Load the RSPX NLM on the server. (This also loads REMOTE NLM.)
  2. Run RCONSOLE.EXE from the workstation to access the server.

Each of these tasks is described in detail in the following procedure.


Prerequisites

NOTE:  You don't need the Supervisor object right to the remote server because RCONSOLE does not use Novell Directory Services.


Procedure

  1. At the server console prompt, type

    LOAD RSPX <Enter>

    You are prompted to enter a password to use when you establish the remote console session from a workstation. If you want to use the supervisor password, you must enter it at this point.

    By default, the RSPX NLM requires packet signatures to ensure security. You can change the default setting if desired. For more information about packet signatures, see NetWare Server Security.

    Once the RSPX NLM is loaded on the server, you can start a remote session from a workstation. (REMOTE NLM is automatically loaded with RSPX NLM.)

  2. Go to the workstation and log in to the network.

  3. Make sure you have a drive mapped to the directory where the RCONSOLE.EXE file is located (usually SYS:PUBLIC).

    If you don't have a drive mapped, type

    MAP S16:=SYS:PUBLIC <Enter>

  4. Start RCONSOLE by completing one of the following steps:

    1. If you know the name of the server, type the following command and then skip to Step 7:

      RCONSOLE servername <Enter>

    2. If you know only part of the server name, type the partial name followed by an asterisk, select a server from the displayed list, and continue with Step 7.

    3. If you do not know the name of the server, type the following command.

      RCONSOLE <Enter>

  5. Select LAN from the Connection Type menu.

    A list of available servers appears.

  6. Connect to the server, using one of the following methods:

    1. Select a server from the list.

    2. Type the name of the server.

    3. If the server name doesn't appear in the list and you know the IPX internal network number of the server:

      • Press <Insert>.
      • Enter the IPX internal network number in hexadecimal notation.

  7. At the prompt, type the password you established when you loaded REMOTE.NLM on the server.

    The remote console session is now open. The workstation screen displays the same information you would see on the server console screen.

    NOTE:  Graphical screens are not displayed in remote console utilities.

    When the utility launches, if a graphical screen is displayed on the server console screen, the System Console screen is displayed in the remote view.

    After a remote console session starts, if someone at the server console switches to a graphical screen, the switch is not reflected on the remote screen.

  8. To view a menu of options for the remote session, press <Alt>+<F1>.

    The remote console Available Options menu appears.

    During an RCONSOLE session you can use the keys described in the following table. All the other keys function as if you were at the server console.


    Table 1. RCONSOLE Keys

    Key Description

    <Alt>+<F1>

    Access the Available Options menu.

    <Alt>+<F2>

    Exit Remote Console.

    <Alt>+<F3>

    Cycle backward through the current console screens.

    <Alt>+<F4>

    Cycle forward through the current console screens.

    <Alt>+<F5>

    Show the address of the workstation you are using for this session.

    <F1>

    Display Remote Console help when the Remote Console Available Options menu is on the screen. (When another screen is showing, this key displays the relevant server help information.)

  9. To end the remote console session, press <Alt> + <F2> from the console prompt or select End Remote Session with Server from the Available Options menu.

  10. Choose Yes from the Quit Remote Console Session? box.

    If you specified the name of a specific server as a parameter when you executed RCONSOLE, the remote session with that server is ended.

    If you selected the server from a list of available servers, the available servers list is redisplayed. To exit from the list of servers, press <Esc> and then select Yes from the Exit Remote Console? menu.


Preparing to Run a Remote Console Session Over a Modem

Before running remote console sessions over a modem or null modem cable, you must complete the following steps:

  1. On the server, load REMOTE.NLM, RS232.NLM, and the appropriate communications port driver, such as AIOCOMX.NLM.
  2. Create a callback file, if desired.
  3. Load necessary workstation files.

Each of these tasks is explained in the following procedure.


Prerequisites


Procedure

  1. At the server console prompt, type

    [LOAD] REMOTE [ password] <Enter>

    You must provide a password to use when establishing the remote console session from a workstation. If you do not specify the password as a parameter, you are prompted to enter one.

    If you want to use the supervisor password, you must enter it at this point.

  2. Complete the following steps to load the communications interface module and driver:

    1. Load the communications port driver by typing

      [LOAD] AIOCOMX <Enter>

      This driver is provided with NetWare. You can replace it with an equivalent driver if you choose.

    2. Load the modem connection NLM by typing

      [LOAD] RS232 [ comm_port] [ modem_speed] [N] [C] <Enter>

      Replace comm_ port with the communications port number (1 or 2).

      Replace modem _speed with the baud rate (2400, 4800, ... 115200).

      Use the N parameter if you are using a null modem cable.

      Use the C parameter if you want to use the callback option. The callback option is explained in the next step.

  3. (Optional) Create a CALLBACK.LST file in the SYS:SYSTEM directory on the server.

    A callback list is a list of modem (telephone) numbers that are authorized to access the server.

    The server uses the callback option only if the C parameter was used when the RS232 NLM was loaded on the server.

    When a call comes in, the server notes the number of the modem calling and then terminates the connection. The server then checks for the number in the callback list. If the number is in the list, the server calls the number and reestablishes the modem connection. If the number is not in the list, the server ignores the call.

    Use a text editor or the EDIT utility to create the file. If you need help creating the file, see Using EDIT to Create and Edit Text and Batch Files.

    1. In the file, enter a list of callback numbers that are authorized to start a remote console session.

      For example, you might list three numbers:

      18015552257
      5554321
      4269

      The first is a long distance number (with an area code), the second is a local number, and the third is an internal extension number.

    2. Save the text file.

  4. Prepare the workstation as a remote console by creating a directory and copying the following RCONSOLE run files to it:

    RCONSOLE.EXE
    RCONSOLE.HEP
    RCONSOLE.MSG
    IBM_RUN.OVL
    _RUN.OVL
    IBM_AIO.OVL
    _AIO.OVL
    TEXTUTIL.HEP
    TEXTUTIL.IDX
    TEXTUTIL.MSG

    It doesn't matter where you place the directory or what you name it. The run files come with your NetWare system.

You are now ready to run a remote console session over a modem.


Running RCONSOLE Over a Modem


Prerequisites


Procedure

  1. At the workstation, change to the directory you created for the remote files (described in Preparing to Run a Remote Console Session Over a Modem) and type

    RCONSOLE <Enter>

  2. Select Asynchronous from the Connection Type menu.

  3. If this is the first session from this workstation, select Configuration from the Asynchronous Options menu, and then continue with Step 4. Otherwise, skip to Step 7.

  4. In the Current Modem Configuration window, set the options according to your modem and workstation specifications.

    1. Use the arrow keys to highlight a field and press <Enter>.

    2. If the cursor becomes active in the field, type in the appropriate information.

    3. If a selection is displayed, select the appropriate item.

      The UserID and the Call Back fields must be filled in. Choose any string for the UserID. For example, you may use your name or your phone number. This ID is displayed on the server console during the remote session.

    4. In the Callback field, enter the modem (telephone) number you are calling from.

      If the Call Back option is used, this number must be in the callback list. See Preparing to Run a Remote Console Session Over a Modem.

  5. Press <Esc> to exit the window.

  6. Choose Yes from the Save Changes? box to save your configuration.

  7. Choose Connect to Remote Location from the Asynchronous Options menu.

    A list of available servers is displayed.

  8. Select a server.

    If you are using the callback option, the server terminates the connection and compares the number in the modem configuration file with the numbers in the callback list.

    If the number in the modem configuration file is in the list, the server dials the number to establish the connection and then displays the console prompt. If the number is not in the list, the server displays an error message.

  9. Once the console prompt is displayed, the remote console session is active. Press <Alt>+<F1> to view the Available Options menu.

    During the RCONSOLE session, you may use the keystrokes shown in Table 1. All other keys function as if you were at the server console.

    NOTE:  RCONSOLE does not provide guaranteed packet delivery. When sending or receiving packets from a server with extensive disk or LAN activity, RCONSOLE may time out.

    If this happens, you receive a No response from server or an Unable to send request to server message. If you receive one of these messages, retry the operation.

    NOTE:  Graphical screens are not displayed in remote console utilities.

    When the utility launches, if a graphical screen is displayed on the server console screen, the System Console screen is displayed in the remote view.

    After a remote console session starts, if someone at the server console switches to a graphical screen, the switch is not reflected on the remote screen.

  10. To exit the remote console session, press <Alt>+<F2> at the console prompt or select End Remote Session from the Available Options menu and then select Yes.


Loading Remote Modules on Bootup

You can put commands in the AUTOEXEC.NCF file to load remote console modules each time the server is booted.

Since these modules require the remote password, you may choose to place an encrypted version of the password in the file, too. The method described in this section secures the server console by hiding the remote console password from users who access the AUTOEXEC.NCF file.

The following procedure explains how to set an encrypted password and autoload REMOTE.NLM with the encrypted password.

  1. To encrypt a password for REMOTE.NLM, type the following:

    [LOAD] REMOTE <Enter>

  2. Execute the following command:

    REMOTE ENCRYPT <Enter>

    The server prompts you to enter the password to be encrypted.

  3. Enter the password you want to use for remote console sessions.

    If you want to use the supervisor password, you must enter it at this point.

    The system displays the encrypted value and a message asking if the LOAD REMOTE command should be written to the SYS:SYSTEM\LDREMOTE.NCF file.

  4. To include the LOAD REMOTE command with your encrypted password in the LDREMOTE.NCF file, respond Yes.

    The system places a LOAD REMOTE command into the LDREMOTE.NCF file with the encrypted password as a parameter.

    You can execute the LDREMOTE.NCF file with the encrypted password whenever you want to load REMOTE.NLM, or you can place the command to execute the file into your AUTOEXEC.NCF file by completing all the steps in this procedure. Either option will save you from having to type in the encrypted password, which is often quite long, every time you load REMOTE.NLM.

  5. To autoload REMOTE.NLM with an encrypted password on bootup, use either NWCONFIG or EDIT to open the AUTOEXEC.NCF file.

    For information about editing .NCF files, see Using EDIT to Create and Edit Text and Batch Files.

  6. Move the cursor to the end of the file and type the following:

    LDREMOTE

    1. For LAN or WAN connections, type the following after LDREMOTE:

      LOAD RSPX

    2. For modem connections, type the following after LDREMOTE:

      LOAD AIOCOMX

      The AIOCOMX driver is provided with NetWare. You can replace it with an equivalent driver if you choose.

      LOAD RS232 [ comm_port] [ modem_speed] [N] [C]

      Replace comm_ port with the communications port number (1 or 2).

      Replace modem _speed with the baud rate (2400, 4800, ... 115200).

      Use the N parameter if you are using a null modem cable.

      Use the C parameter if you want to use the callback option. For information and instructions, see Preparing to Run a Remote Console Session Over a Modem.

  7. Exit and save the AUTOEXEC.NCF file.

    The server will now automatically load the necessary remote modules and your encrypted password whenever it is booted.

For more information about utilities related to using a remote console, see RCONSOLE, REMOTE, RS232, or RSPX in the Utilities Reference library.


Upgrading Files on a Remote Server

You can use a remote console to copy new NetWare files to a server. Files can be copied from diskettes, a CD-ROM drive, a local drive, or from a network directory. To copy new NetWare files to volume SYS: on a remote server, follow these steps.


Prerequisites


Procedure

  1. Start a remote console session with the server.

  2. At the remote console, type

    [LOAD] NWCONFIG <Enter>

  3. Choose Copy Files Option.

  4. Choose a remote path.

    This is the path from which the files will be installed. You may load files from NetWare diskettes, a local drive, a CD-ROM, or a network drive.

  5. Follow the subsequent prompts.


Installing or Reconfiguring Applications on a Remote Server

You can use a remote console session to install or reconfigure Novell or third-party products on a remote server. Follow these steps.


Prerequisites


Procedure

  1. Start a remote console session with the server.

  2. At the remote console, type

    [LOAD] NWCONFIG <Enter>

  3. Choose Product Options > View/Configure/Remove Installed Products.

    A list of currently installed products (if any) appears.

  4. To reconfigure an installed product, select that product and press <Enter>. Follow screen instructions.

  5. To install a new product, press <Insert>.

    A message states that the product will be installed from the A: drive, unless otherwise indicated.

  6. If necessary, insert the product installation diskette into the drive.

  7. Press <Enter> to accept the default, drive A:, or press <F3> to enter a different installation source path.

  8. Follow the prompts to install the product.


Rebooting a Remote Server

You can reboot a NetWare server from a remote console by first modifying the server's AUTOEXEC.BAT file and then executing another .NCF file that you create for this purpose.


Prerequisites


Procedure

  1. To automatically reboot the server, put commands to change to the NetWare directory and execute SERVER.EXE in the server's AUTOEXEC.BAT file.

    For example, if the SERVER.EXE file is in the NWSERVER directory on drive C:, put the following lines in the server's AUTOEXEC.BAT file:

    CD C:\NWSERVER

    SERVER.EXE

  2. Start a remote console session with the server.

  3. Load the EDIT NLM on the server by typing

    LOAD EDIT <Enter>

  4. Create an .NCF file and include the following commands in the order given:

    REMOVE DOS

    RESTART SERVER

    See Using NWCONFIG to Create and Edit Startup Batch Files.

  5. Save the file in the SYS:SYSTEM directory.

  6. Start a remote console session with the server.

  7. Send a message to all users to inform them that the server is going down.

    See Sending Console Messages to Workstations if you need help sending a message.

  8. At the system prompt on the remote console, enter the name of the .NCF file you created.

    This reboots the server. The keyboard is disabled for a few minutes while the file is processed.

    When the file has finished processing, a connection is lost message appears.

  9. Press <Esc> to exit the remote session.

  10. Open a new remote console connection with the server.