www.LabF.com  
   Products   DownloadPrice & OrderSupportCompanyTutorialsSitemap
           










  back | index | next

Entering Startup Info

This section describes the Startup fields you can use to select or enter proper parameters to run remote commands.


The Start Method Box

The first thing you should select is the Start Method. Initially REXEC is selected.

RSH

For RSH method ("Remote Shell"), you should know your user ID name. If you click on RSH, the Password field will be grayed. Some hosts require your PC to be authorized before using RSH, as it does not require a password. On UNIX systems, you need to add your PC name to the /etc/hosts.equiv and $HOME/.rhosts files on your host.

REXEC

For REXEC (Remote Executable) method, you can choose either the direct access insecure execution mode or the secure (SSH) channel mode.

In the Start Method box of the Startup window, you can see a list of actual SSH1/SSH2 protocol connections you have previously established by the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client (see Starting an SSH Session in the Starting and Terminating Telnet_SSH section on how to establish secure connections). The Refresh button allows you to renovate the list.

If you clear the Use SSH Forwarding check box then the direct access insecure mode will only be used for REXEC operations.

If you want REXEC operations to be done in secure connection mode, enable the Use SSH Forwarding check box and select a desired remote host (an active SSH server) from within the list.

In the SSH1/SSH2 mode, the "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and Startup Client will automatically be used, so you need not set up any port forwarding manually.

If the REXEC server and SSH1/SSH2 server you are using in a Startup session are on the same remote host then the Host Name/IP Address field can contain "localhost" or "127.0.0.1". This is more preferable than its actual IP address in most cases (but depends on how the host has been configured).

You can use the netstat utility to watch your network connections.

SSH1/SSH2 daemons do not usually provide for port numbers less than 1024. This is why the "Dynamic Port Forwarding" feature does not work for RSH and RLOGIN methods.

RLOGIN

For RLOGIN (Remote Login) method, you can use the following macros in a command or startup files (see section Command Box below):

  • "$(DELAY)"
  • "$(CR)"
  • "$(LF)"
  • "$(CRLF)"
  • "$(SEND)"
  • "$(INPUTPASSWORD)"
  • "$(DISPLAYNUMBER)"

Note that the profile file is always executed on a remote host for this method when a user logs in.

Startup uses the randomized RLOGIN initial portnumber to avoid possible rejection of connection.

lShell (local Shell)

The lShell (i.e., local Shell) mode allows you to enter a command line to run a local executable file (on your PC) like you do that with the MS Start/Run box. For example, you may choose to run Telnet, Notepad, local X clients, etc.

For information about local X clients, please refer to Appendix F Local X and Motif Clients.

Telnet

The Telnet method is similar to other methods. You enter login information to establish Telnet connection with your remote host and specify a command line or file you want to execute on the host. When you press Execute, Startup will launch a non-interactive Telnet session (i.e., without the Telnet window).

In this mode, the direct access insecure mode will be used for Telnet operations (without SSH X11 forwarding).

Note that you must use the -display argument in the command line to invoke a remote X client (to communicate with XServer on your PC-host). In this case, the X client connects to your XServer and operates.

For example, you can execute the following command line to invoke the 'xterm' application on your PC-host:

path/xterm -display 192.168.36.41:0 &
or
path/xterm -display $(LOCALIP):$(DISPLAYNUMBER) &

Telnet/SSH2 (SSH-2 Client)

The Telnet/SSH2 (SSH-2 Client) method is similar to other methods. You enter login information to establish Telnet_SSH connection with your remote host and specify a command line or file you want to execute on the host. When you press Execute, Startup will launch a non-interactive Telnet_SSH session (i.e., without the Telnet_SSH window).

It is not recommended to use the '&' sign because of unstable results. E.g., if you need to start 'xterm' on a remote host, then the "xterm" command line is preferable (and "xterm&" is not recommended).

In the Start Method box of the Startup window, you can see a list of actual SSH1/SSH2 protocol connections you have previously established by the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client. The Refresh button allows you to renovate the list.

In the SSH1/SSH2 mode, the "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and Startup Client will automatically be used, so you need not set up any port forwarding manually.

To use this method, you must prove your identity to the remote system using either password authentication or RSA/DSA authentication method. RSA/DSA authentication uses a public/private key pair to authenticate the connection. If RSA/DSA authentication is selected (by checking on the RSA/DSA Authentication check box), you should enter your passphrase in the Password entry field. Also you should specify a location of the identity file (in the Private Key File entry field) to be used for this process. If the RSA/DSA Authentication check box is disabled, then the password authentication method will be used.

For more information on how to establish secure connections, refer to Starting an SSH Session in the Starting and Terminating Telnet_SSH section in chapter Telnet_SSH.

Note that you need not use the -display argument in the command line to invoke remote X clients (to communicate with XServer on your PC). In this case, the X client you invoke connects to your XServer via the SSH channel of your choice and operates using standard SSH X11 forwarding (without establishing new connection between hosts).

For example, you can execute the following command line to invoke the 'xterm' application on your PC-host:

path/xterm;

Note that if you apply the -display argument in the command line to invoke a remote X client (to communicate with XServer on your PC), then the standard SSH X11 forwarding will not be used (and a new insecure Telnet connection will be established between the X client and your XServer according to the -display argument).

You can use the netstat utility to watch your network connections.


The Login Box

The Login box lets you enter information required to log onto a host. If your start method is set to RSH, the Password field is disabled.

Host Name/IP Address

This field defines a name for a remote host you want to connect to and execute commands. You can enter either the network node name for the host or its network address. When you click on the scroll arrow beside the HostName field, a drop-down box will display host definitions being in your hosts file. To select a host, click on an appropriate definition.

Note that a host name you specify here may not result in the same remote host name due to different name-address DNS translations in different LANs. You should specify the host name or IP address for a remote host in a LAN that are known inside that LAN for that host.

User ID

This field is where you enter your User ID for the host you want to connect to.

Password

This field defines your password for the REXEC, RLOGIN, or Telnet method. When you enter your password, an asterisk will appear for each character you type in.

Enable Save Password

If this check box is disabled, then you will be prompted to enter a password each time when it is needed (e.g., when you Save Job As with the setting and then launch the job).


The Command Box

The Command box lets you enter information required to execute a command or to run a startup file on the specified host.

Command

This field is used to enter a command that will be sent to a host or to specify a startup file you want to run. The command you enter depends on your host system and how it is set up. In the lShell mode, you should enter a command to be run locally (on your PC). You can enter up to 255 characters in a command line.

UNIX C Shell Command

If you have defined all necessary environment variables in the C shell resource file (i.e. the .cshrc file), then you can simply enter a command. For example, to start xterm:

xterm &

UNIX Bourne Shell Command

Because the Bourne shell startup file (i.e. the .profile file) will not be invoked when the Startup program logs onto the host, it is recommended that you include the path and display variables on the command line. For example:

path/xterm -display mypcname:0 &

where path is the location of the xterm on the host, and mypcname is the network name or IP address of your PC.

Note that you can use the following macros in a command or startup files:

  • $(LOCALHOST) for the network name of your PC
  • $(LOCALIP) for the IP address of your PC
  • $(LOCALDISPLAY) for the display specification of your XServer
  • $(DISPLAYNUMBER) for the display number of your XServer

For example:

path/xterm -display $(LOCALHOST):0 &

path/xterm -display $(LOCALIP):0 &

path/xterm -display $(LOCALDISPLAY) &

path/xterm -display $(LOCALIP):$(DISPLAYNUMBER) &

Also, you can use macros $(INPUTLIP) to place any text into the command line before its executing. For example, if the Command field contains the following line:

xterm -display $(INPUTLIP):0 &

then you will be prompted to input the text string (an IP address is assumed). If you enter 1.2.3.4, then the resulting command line will be:

xterm -display 1.2.3.4:0 &

To execute a command entered in the field, click on the Execute button.

Command File

This field is used to specify a startup file you want to run on a host or edit it.

When you click on the scroll arrow beside the Command File field, a drop-down box will display all startup files stored in the WinaXe Plus's home directory.

In order to execute instructions in a startup file, select from the box or enter into the field a name for the file you want to run and press the Execute button. If the file exists, its first line appears in the Command field.

Another way of specifying a startup file is to enter into the Command field a file name preceded by the @ sign, for example @mystartup.su.

Edit

When you press on this button, the Microsoft Notepad is invoked and the startup file specified in the Command File field will be opened. This lets you view or modify the file before running it.

Log File

When you enable this option, whenever you execute a single command or a startup file, any startup or error message information that the host or client would normally display will be sent to a file. The log file resides in the WinaXe Plus's home directory. The file's name differs depending on how you execute commands.

  • If you execute a single command entered into the Command field, all log information will be saved in a file called startup.log.

  • If you run a startup file, the log file will be saved as filename.LOG, where filename is the name of the startup file.

Information will be sent to a log file for the amount of time specified in the Exit after Timeout of field, after which the socket will be closed.

Wait for RLogin Password

This option is used if you want to enter your password only when a prompt from the RLOGIN daemon appears.

Exit after Timeout of

This field defines the amount of time the socket will stay open after the host connection has been made. The default value is of ten seconds. If the connection gets established but the invoked program does not get time to start up, you can set this to a higher value.

Default
This button will initialize all parameters to their default values.
Status Messages

Whenever you execute a single command or a startup file, any startup or error message information that the host or client would normally display is sent to the box.


Example of Initiating the REXEC Session via SSH

First, make sure that:

  • your remote host is accessible from your PC

  • your remote host supports the REXEC protocol for your PC

  • sshd-daemon (or sshd2-daemon) is running on your remote host

  • your PC is accessible from your remote host.

If OK, then you may initiate the REXEC session via SSH like the following steps:

1) Initiating the Telnet_SSH session

  • Start Telnet_SSH by double-clicking on the Telnet_SSH icon from the WinaXe Plus Programs' folder (the Telnet Connect Host window should appear)

  • Choose SSH-1 (or SSH-2) in the Interface section

  • Enter the network name or IP address of the remote host you want to connect to

  • Change the default SSH port number if required

  • Click OK to establish connection with the remote host (the SSH Authentication window should appear)

  • Choose to Use plain password to log in

  • Specify the login information required for your host system: User name and Password in the Passphrase field

  • Click OK to log in to the remote host (the Telnet_SSH window should appear)

2) Initiating the Startup session

  • Launch Startup by double-clicking on the Startup icon from the WinaXe Plus Programs' folder (the Startup window should appear)

  • Choose REXEC in the Start Method section

  • Enter localhost as the network name or 127.0.0.1 as the IP address in the Host Name/IP Address field in the Login section

  • Enter your User Name in the User ID field (e.g., John)

  • Enter your Password required for your login to the remote system (e.g., Smith)

  • Select the line with the SSH connection to your remote host from the list box under the Use SSH Forwarding check box

  • Check the Use SSH Forwarding check box

  • Specify other required settings

  • In the Command field, enter the following line:
    ls -l
  • Click the Execute button

    Startup will open the REXEC session to the remote host through the encrypted connection. In the Status Messages pane, the output of the command (i.e. the list of directories and files from your home directory on your host) should be displayed.

   

WinaXe Plus
X-server and ssh-client
> Download now!

> Info
   > PC With
   > All in one
   > Easy to
> Specs
   > Package
   > Specifications
   > Requirements
   > Network variants
   > New features
> Price & order
   > Price list
   > Payment methods
> Support
   > Technical questions
   > Sales questions
   > FAQ
   
> Tutorials
   > Manual

  
           
           
    © LabF. All rights reserved.     Privacy policy     e-mail us at: sales@labf.com