On Thu, 20 Apr 2006, Andrew Friedley wrote:
> >'telnet 192.168.1.1 33973' ...
> > telnet: Unable to connect to remote host: Connection refused'
> This is what I was about to suggest - looks like ports are being
> filtered. rsh appears to be able to run commands on remote hosts, which
> indicates you have at least some connectivity.
I beg to disagree. Trying to telnet with a port specified would work
only if there is some program listening on that port on the remote
machine - this would happen only if the LAM application would still be
running and waiting for connections. If the telnet is performed at a
later time, there's nothing listening on that port and the "Connection
refused" message is normal.
However, the idea of ports being filtered is still valid and a
probable explanation for the OP's problem.
--
Bogdan Costescu
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu_at_[hidden]
|
