i am able to login to AX server thru console but not able to login directly thru server.
also the server is not ping-able with other server.
As vbe already said this is perhaps because you have no network connection. This can have a lot of causes (on the client side as well as the servers), nobody can help you there without a lot more information.
If you regain the etwork connection and the problem still persists: every user has 2 attributes, "login" and "rlogin", which can be "true" or "false". See the output of the lsuser-command:
"login" allows the user to login at the console (or - which is the same - via the HMC). "rlogin" allows the user to connect to the system via the network. Many ssh-configurations are done in a way they do not honour this rlogin-setting, so you might be able to bypass this if your system is poorly configured, but if everything is set up correctly you should be unable to log on via network if "rlogin" is set to "false".
Hi All,
I am very new to Unix and already have a problem... My predecessor didn't note down the username and password to login to the console of an HP D Class 9000 enterprise server we have. I was wondering whether there is any way to bypass this console login screen in Unix... If not is there... (1 Reply)
I somehow modified the system so that no one can telnet or ssh into this box as any user including root. I might have blown away important files, I don't know.
Please let me know what I have to check to make it so that I can login.
This is what I get when I try to telnet or ssh:
telnet bk02... (5 Replies)
Hi,
I have solaris 10 installed on my computer and when try to login in console mode, it would give output something like this.
login:root
Password:
Last login: Thu May 29 10:00:55 on console
-sh: syntax error: `(' unexpected
-sh: grep: not found
-sh: uname: not found
-sh: test:... (1 Reply)
Hi
I can neither able to login on console with my user ID nor with root user on HP-UX 9000/800 v11.11. I am putting the correct Password.While my colleague can login as his user on console. What is the reason that I can't login to console?
Pl. help & thanks in advance.
Mike (5 Replies)
Hello,
I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification.
I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server.
i.e. the same login info. is used for both,... (2 Replies)
Hello,
I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification.
I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server.
i.e. the same login info. is used for both, when... (1 Reply)
Dear Friends ,
I got a problem In our AIX 6.1 server . When I start or restart the machine I cannot Login the server . It shows a dialog box and shows some comments , those are :
>>
The DT messaging system could not be started .
To correct the problem :
1. Choose to return the login... (1 Reply)
I want to learn AIX. I would like to find someone who would be willing to give me a login to their AIX home lab server. My intent is to poke around and discover the similarities and differences of AIX compared to other *NIXs.
I am a UNIX admin so I can think of what some immediate concerns may... (1 Reply)
Hopefully my question makes sense, but I was wondering if the telnet service has anything to do with console logins or if they are completely unrelated. So for example, does the /etc/default/login file in UNIX have anything to do with Telnet? So if I want to verify that the root user can't login... (8 Replies)
We are having occasional problems accessing some AIX servers. When this happens we cannot ssh to the server in question or login via HMC console terminal window. We can ssh some commands to the server and get responses but other commands just hang, ssh serverA date returns the date, ssh serverA... (5 Replies)
Discussion started by: Kierong
5 Replies
LEARN ABOUT MINIX
rlogind
RLOGIND(8) System Manager's Manual RLOGIND(8)NAME
rlogind, in.rld - remote login server
SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld
tcpd login /usr/sbin/in.rld
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request
is received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so
that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance
of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in
rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.
The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
SEE ALSO rlogin(1).
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
``Try again.''
A fork by the server failed.
``/bin/sh: ...''
The user's login shell could not be started.
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)