cannot "enter" in station...

[Oleg Goudovany_1]

Hi, all!
Today I could'nt enter in some station. I tried did it in terminal window and X-terminal. But I see this machine in network, I can ping it. OK.
When I type in terminal window :
#rlogin lks1
I got:
rcmd: connect: lks1: Connection refused

Why refused?
What reason for that and how enter in it?

Thanx in advance,
Oleg

[Ross Zubritski]

Oleg,

Make sure the ined didn't die on the machine you are trying to connect to.

Regards,

RZ

[Yogeeraj_1]

hi,

Below a quote from "man rlogin", which clearly explains the requirements for the use of remote commands.


The rlogin command connects your terminal on the local host to the remote host (rhost). rlogin acts as a virtual terminal to the remote system. The host name rhost can be either the official name or an alias as listed in the file /etc/hosts (see hosts(4)).

In a manner similar to the remsh command (see remsh(1)), rlogin allows a user to log in on an equivalent remote host, rhost, bypassing the normal login/password sequence. For more information about equivalent hosts and how to specify them in the files /etc/hosts.equiv and .rhosts, see hosts.equiv(4). The searching of the files /etc/hosts.equiv and .rhosts occurs on the remote host, and the .rhosts file must be owned by the remote user account.

If the originating user account is not equivalent to the remote user account, the originating user is prompted for the password of the remote account. If this fails, a login name and password are prompted for, as when login is used (see login(1)).

The terminal type specified by the current TERM environment variable is propagated across the network and used to set the initial value of your TERM environment variable on the remote host. Your terminal baud rate is also propagated to the remote host, and is required by some systems to set up the pseudo-terminal used by rlogind (see rlogind(1M)).

All echoing takes place at the remote site, so that (except for delays) the remote login is transparent.

If at any time rlogin is unable to read from or write to the socket connection on the remote host, the message Connection closed is printed on standard error and rlogin exits.


hth
Yogeeraj

[Ron Kinner]

rlogin requires that the other end be listening on the rlogin port (which I don't happen to know the number of offhand). First check on the remote machine that it is listening by doing a
netstat -a | grep rlogin

second the two machines need to know each other's ip address via /etc/hosts or DNS so check
nslookup remotehostname
on both machines and make sure they both can get an IP for the other. Ping the other machine by both ip address and host name to make sure.

third your login and password needs to be valid on the remote machine and I suppose you also need a home directory on the remote machine.

There could also be a firewall issue if the traffic passes through a firewall.

Ron

[Robert-Jan Goossens]

Hi,

Think Ross has a very good point here,

# ps -ef | grep inetd
root 1010 1 0 Dec 2 ? 5:29 /usr/sbin/inetd

Hope it helps,

Robert-Jan.

[Oleg Goudovany_1]

Thanx for everyone for answer - they called me to know more. And I knew!
I check as was recommend - that's OK! Station access to "itself"! But nobody didn't nothing. Please answer what happened - why station began to work?

Thanx, Oleg

[Michael Steele_2]

That's got to be network related, either on the server with a runaway process, like inetd, or within the network itself. A block on the telnet service? Was there a network backup being performed? (* This will do it *) Huge file transfers via ftp are another and will cause a timeout between connections.