WebTerm X Frequently Asked Questions
What do I need to use the RSH Protocol?
The RSH protocol lets you log in to your host without a password. Generally, RSH is used to connect to hosts where system security is not a concern.
Before you can use the RSH protocol, you need to create a file called .rhosts in your home directory on the applicable host. This file should contain the system name (of the the PC/Mac) and user id name (login name on the host system) of all the users with permission to log in to the host system account without a password. The format of the .rhosts file is:
systemname1 username1
systemname2 username2
If the name of your PC is entered in the /etc/hosts.equiv file on the host, or if your account on the host does not have a password, you do not need to set up an .rhosts file. Also, your PC's IP address must be listed in the etc/hosts file and the RSH listener must be running.
Rsh uses either the .profile or the .cshrc file in your home directory to set up the environment in which the application runs. Certain environment variables, such as the LC_LIBRARY_PATH on Sun systems, need to be set correctly before you can run X applications. If you have trouble starting an X application using RSH, check that the necessary environment variables are set. See your system administrator for more information.
Use the rexec protocol if security is an issue or if you are unable to put the .rhosts or hosts.equiv authorization files on your host.
Determining if you have a user account.
The easiest way to determine if you have a user account on a host computer is to attempt to log on using Telnet, a widely supported connection protocol.
Note: If you are not able to connect to the host computer using telnet, you will need to contact your network system administrator for assistance.
If you can connect to your host and log on, you know you have a valid user account. If not, you need to contact your system administrator to determine if your log on information is correct and what the restrictions on your account are.
Determining if your host is accessible on the network.
If you can telnet to your host, or it responds back at all, then it should be accessible on the network.
If you can not telnet, try to PING your host's IP address. Microsoft includes a ping utility with Windows 95 & NT. If you can't ping your host it is probable that its not at that IP address, not on the network, behind a firewall, or not powered on. Please see your system administrator for assistance.
Determining if your computers IP address is listed in the etc/hosts file.
Your computer's IP address must either be listed in the etc/hosts file on the host or resolved via a Domain Name Server (DNS). The later is beyond the scope of this document. However, on a Unix system you can easily determine if your IP address is listed in the etc/hosts file by entering the following at the command prompt:
grep -n <your computers ip address> //etc/hosts
Determining if RSH is available on your host.
The easiest way to test for rsh is to create a sample connection. If the connection does not seem to work, here are some steps to take to see if the listener is installed and configured.
If you have tested an rsh connection with no success, the next thing to try is to verify that you can at least telnet to the host. This is usually quite simple:
On a Windows system, run telnet <your hostname> from the Run... command in the Windows Start menu.
Note: If you are not able to connect to the host computer using telnet, you will need to contact your network system administrator for assistance.
If you can telnet to the host computer, run the netstat utility, which shows the connection daemons that are running. At the Unix prompt in a telnet window enter:
netstat -an > temp && grep -n 514 temp
If the rsh listener is running on the "well known" TCP socket (514) on the host, the result of the above command should look something like:
xx:tcp 0 0 *.514 *.* LISTEN
Otherwise, a you need to start the listener before any connection can be made. See your UNIX vendor's documentation or one of the many commercially available UNIX references for details on this UNIX administration task.
Should you have any questions or issues please use our Support Request Form.
NOTE: For discontinued products or products no longer in development, contact Sales at 603.880.9118 or via e-mail at: sales@powerlan-usa.com.
|
