X-Win32 Knowledge Base   >   Connection refused for rexec or rsh sessions

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




Connection refused for rexec or rsh sessions

A connection refused error message when attempting to start an rexec or rsh session means that the remote system that you are contacting is either not running rexec or rsh, or it is not listening for rexec or rsh connections on the interface that you are attempting to connect from. This problem is not isolated to X-Win32 and would occur with any rexec or rsh client that attempts to connect to this particular remote Unix, Linux, or BSD (e.g. Red Hat, SuSE, Debian, Ubuntu, HP-UX, AIX, Solaris, or FreeBSD) machine. Follow the steps below to diagnose this connection problem.


NOTE: Connection refused means that the remote host is actively notifying your local computer that the connection attempt was refused; this rules out firewalls as a problem, since a firewall will cause the rexec or rsh connection attempt to timeout in one to two minutes instead of returning this immediate connection refused error. Thus, you do not need to change your

Troubleshooting Steps

  1. Consider using a StarNetSSH session instead of rexec or rsh, as SSH is typically enabled by default on most Unix, Linux, and BSD systems and is much more secure than these older protocols
  1. The rexec or rsh service may be disabled, or enabled only for the loopback address and not for external network interfaces. On most Unix systems, services are enabled via a line in the file /etc/inetd.conf. On modern Unix or Linux systems, inetd has been replaced with xinetd; xinetd settings are stored in separate files in the /etc/xinetd.d/ directory. These files can be modified to enable these services, or to allow them to accept connections from external network interfaces.

    See Also



How Can We Improve This KB Article?

Please rate the quality of this article: Excellent Good Fair Poor

Did this article answer your question? If not, we'd like to hear more about it:

Do you need additional assistance? If so, enter your email address:

Articles are periodically updated based on your feedback. If you enter an email address, then you will be given the opportunity to open a case, for which you will receive a response within 2 business days.