My telnet access to the server is not available anymore. I have found that when I execute >telnet IP, the login prompt for username/password entry is not displayed. Cursor blinks in a empty line and I dont see the prompt to enter my username.
It hungs in this state and not possible to ctrl+c
When I try this, following process appears in
In ps -ef list, similar processes are present and are not being cleared.
I tried to kill them without success by >kill -9 PID
I checked the messages log and found those logs,. I am able to ssh the same server
How I can solve this telnet problem?
Thanks,
Kory
---------- Post updated 08-05-11 at 06:05 AM ---------- Previous update was 08-04-11 at 08:33 AM ----------
Nobody has any idea?
What I can do for those processes? Also If I can killl them somehow, would it be possible to telnet ?
i'm having trouble enabling telnet access to my suse linux machine.
i can ssh to my machine just fine, but when i try to telnet i get a "connection refused" error. how can i fix this?
okay,
-nydel (1 Reply)
Just took over a UNIX Server from someone who left our company.
Having problems with access by some existing users as well as new users.
I get the following message from telnet sessions, when attempting access at the "Login:" prompt:
"UX:in.login:ERRO: Login incorrect"
"telnetd:Unable to... (2 Replies)
I have installed aix 5.2 on aix box through serial console connected to COM 1 . I even get a login prompt after the fresh installation . But as soon as i give a root & enter i again get a login prompt.i..e I am not able to logon after a fresh installation.
and even i configured IP configuration... (0 Replies)
I use server Unix with AIX 5.2.
I can't telnet to server about 5 mn, then i can access to server via telnet.
This problem have again and again. Sometime can, sometime can't.
I dont know why?
Do you have any idea? (4 Replies)
I have just set up a user on our system HP-Thru64. The user needs to be able to su to root after they login and this works fine. Users cannot login from root externally so you have to first connect as a user and then su. I am wondering is it possible for me to prevent the user from having telnet... (4 Replies)
Hi
I have a perl script code in which connecting with db2 database and doing some process. My perl script code and db2 database server present in the same unix server. I am connecting and executing perl script code via windows telnet. Now my question is i could not able to connect db2 server... (4 Replies)
Hello,
I have recently taken over administration of a Sco Unixware server (Version 7.1.4), but have no previous experience with Unix.
I now have the following problem: Most computers on the network are unable to Telnet to the Unix server but some PCs with privileged users can, which is... (7 Replies)
Hello,
I've bought an semi-dedicated (cloud computing) server, but yesterday I had to change my IP, so I tried this with PuTTY:
Went to
/etc/network/interfaces
And changed
iface eth0 inet static
To
iface eth0 inet dhcp
Hoping to get an dynamic IP
Then I restarted my... (5 Replies)
Discussion started by: lukinhasb
5 Replies
LEARN ABOUT OSF1
rlogin
rlogin(1) General Commands Manual rlogin(1)NAME
rlogin - Connects the local host with a remote host
SYNOPSIS
rlogin [-8L] [-e character] [-l user] remote_host
The remote login command (rlogin) logs into remote_host and connects your local terminal to the remote host.
OPTIONS
Allows an 8-bit data path at all times. Otherwise, unless the Stop and Continue key sequences on the remote host are not standard, rlogin
uses a 7-bit data path and the eighth (high) bit of each byte is stripped. Changes the Escape character. Substitute the character you
choose for character. Changes the remote username to the one you specify. Otherwise, your local username is used at the remote host.
Allows the rlogin session to be run in litout mode. In this mode, the escape sequence ~. (where ~ is the escape character) disconnects you
from the remote host and the escape sequence ~^Z (where ^Z, or Ctrl-Z, is the suspend character) suspends the rlogin session if you are
using csh.
DESCRIPTION
The remote terminal type is the same as that given in the local TERM environment variable. The terminal or window size is also the same,
if the remote host supports them, and any changes in size are transferred. All echoing takes place at the remote host, so except for
delays, the terminal connection is transparent. Pressing the Stop and Continue key sequences stops and starts the flow of information, and
the input and output buffers are flushed on Interrupts. The rlogin command can only be used to connect to systems that are running the
rlogind daemon.
On systems that do not support rlogin, you can use telnet (if supported) as an alternative.
If you do not specify the -l option, the local username is used at the remote host. If -l user is specified, the username entered is used
at the remote host. In either case, the remote host allows access only if one or both of the following conditions is satisfied: The local
host is included in the remote host's /etc/hosts.equiv file, the local user is not the superuser, and the -l user option is not specified.
The local host is included in a $HOME/.rhosts file in the home directory of the remote user account. If -l user is specified, the local
username must also be included in the file.
If neither of these conditions is met and a password is defined for the remote user account, the remote host prompts for a password. The
remote password file is checked to verify the password entered, and the login prompt is displayed if the password is not correct. Pressing
the End-of-File key sequence at the login prompt ends the remote login attempt.
For security reasons, any $HOME/.rhosts file must be owned by either the remote user or the root user and should have permissions set to
600 (read and write by owner only).
In addition to the preceding conditions, rlogin also allows access to the remote host if the remote user account does not have a password
defined. However, for security reasons, use of a password on all user accounts is recommended.
Unless otherwise modified by the -e option, the standard Escape character for disconnecting from the remote host is a ~ (tilde). The Escape
character is only recognized by the remote host if it occurs at the beginning of a line. Otherwise, the Escape character is sent to the
remote host as a normal character. To send the Escape character to the remote host as a normal character at the beginning of a line, press
the Escape character twice. Pressing the Escape character and a (dot) (for example, ~.) immediately disconnects the local terminal from
the remote host.
EXAMPLES
In the following examples, the local host is listed in the /etc/hosts.equiv file at the remote host: To log in to a remote host with your
local username, enter: $ rlogin host2 Password: <Enter password>
To log off the remote host and close the connection, enter the End-of-File key sequence. To log in to a remote host with a differ-
ent username, enter: $ rlogin host2 -l dale
You are prompted to enter your password and then are logged in to the remote host host2 with the username dale. To log in to host2
with the your local username and change the Escape character to (backslash), enter: $ rlogin host2 -e\
FILES
Specifies remote hosts from which users can execute commands on the local host (provided these users have an account on the local host).
Specifies remote users who can use a local user account.
SEE ALSO
Commands: rcp(1), rsh(1), rlogind(8), telnet(1)
Files: rhosts(4)rlogin(1)