eXodusFrequently Asked Questions
What do I need to use the REXEC Connection Protocol?
The rexec protocol lets you start an X application on a Unix host without setting up .rhosts or /etc/hosts.equiv authorization files, as you would if you were using RSH. With the REXEC protocol, you must enter both your username and password for the host to start an X application.
The REXEC protocol requires a password be validated before accessing the host. REXEC sends the username and password you entered in eXodus and your Mac's IP address to the specified host. If the host validates the information, REXEC sends the command to be executed. (Otherwise, the connection will be closed.)
Note: In order to use REXEC with eXodus your computers IP address must be listed in the etc/hosts file and the REXEC listener must be running.
The simplest way to verify whether or not you can use the REXEC protocol is to try and connect to your host using it.
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 computers IP address is listed in the etc/hosts file.
To use the REXEC protocol, 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 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 REXEC is available on your host.
The easiest way to test for an REXEC 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 rexec 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.
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 512 temp
If the rexec listener is running on the "well known" TCP socket (512) on the host, the result of the above command should look something like:
xx:tcp 0 0 *.512 *.* 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.
|
