Sponsored Content
Full Discussion: RSH/rlogin problem
Top Forums UNIX for Dummies Questions & Answers RSH/rlogin problem Post 302389668 by mojoman on Monday 25th of January 2010 01:07:41 PM
Old 01-25-2010
RSH/rlogin problem

Hello,

When I try and RSH/RLOGIN onto a box with user root, I get the prompt but the username/password combination NEVER work. I have the password up properly on the host machine. Does rsh/rlogin not make use of ./etc/passwd and /etc/shadow?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rsh & rlogin

I'm trying to execute the next command: " rsh CompName date " which means i want to get the date from a machine which i have its CompName. but i get the answer : "Connection refused" what do i need to do ? how can i sign myself as user or guest in the other machine ? thanks in... (2 Replies)
Discussion started by: Inbal
2 Replies

2. Programming

rlogin/rsh incoming port

Hi all, In need to know why my sample code below that connect to a rlogind (513) fails, but original unix rlogin does not ? (.rhosts is verified to be correct) I heard rlogin/rsh bind to a reserved port before connecting to the rlogin server. what are they ??? s = socket(AF_INET,... (1 Reply)
Discussion started by: andryk
1 Replies

3. UNIX for Advanced & Expert Users

RLOGIN problem

hi ! i ve a problem with rlogin. i have a server from which only root user can Rlogin other servers. other users can t rlogin, they get the following error : "rcmd2: socket: The file access permissions do not allow the specified action" Does somebody can help ? Thanks, Karine (3 Replies)
Discussion started by: karine
3 Replies

4. IP Networking

rlogin problem

On the HP-UX hostA, the command rlogin hostB generates the error "rlogind: Host address mismatch" even though the hostname & IP of hostA are defined in the .rhosts file and the /etc/hosts files of hostB respectively. The IP and the hostname of hostB are defined in the /etc/hosts file of hostA. (1 Reply)
Discussion started by: vijaysharma.vs
1 Replies

5. UNIX for Advanced & Expert Users

RLogin problem

I need to establish rlogin between 2 of my servers (and I know, it's not secure, smart, etc. ... it's a temporary requirement that I have to do) I tried all the standards. I'm trying to rlogin from server A to server B On server B, I made a /.rhosts file that contains server A's name On... (4 Replies)
Discussion started by: FredSmith
4 Replies

6. UNIX for Advanced & Expert Users

problem in rlogin

Dear Experts, i want to make one script ,by running that script it should rlogin from one mashine to another and the username and passord should be in the script so that it could not ask from me the username and password of another machine from me . please help me out. Regards, SHARY (1 Reply)
Discussion started by: shary
1 Replies

7. HP-UX

rlogin problem

on the system, sometimes the rlogin command can not login the remote node,but ping command can echo the packet. if the inetd domean restarted , rlogin runs normally. We want to know what cause the rlogin failed and how to fix it. (2 Replies)
Discussion started by: Frank2004
2 Replies

8. Shell Programming and Scripting

ftp, rlogin , rcp, rsh are not wroking

Hi Friends I am facing one problem, I am not able to use ftp, rlogin , rcp, rsh in a particular server. when I am trying to ftp certain file from that server it is giving Connection closed by remote host. Now from other unix box I am not able to rlogin that particular server. as .rhosts... (3 Replies)
Discussion started by: itsjoy2u
3 Replies

9. Shell Programming and Scripting

Rlogin / RSH / SSH

Hello, I am looking for a connection method in which i can connect to a remote server but I want to have only one chance to connect to the remote server (not to be asked for iuser name and password again). If I have provided a wrong password then I want the connection to broke and be routed... (1 Reply)
Discussion started by: LiorAmitai
1 Replies

10. AIX

Deny rsh,tn,or rlogin

Is there a way to deny access to a specific remote login option. example: usera--deny telnet access but keep rsh and rlogin userb--keeps telnet, rsh, and rlogin I'm basically trying to contol the access per services instead of changing the LOGIN REMOTELY(rsh,tn,rlogin) option to yes or no. (12 Replies)
Discussion started by: leemalloy
12 Replies
RSH()																	     RSH()

NAME
rsh - remote shell SYNOPSIS
rsh host [-l username] [-n] [-d] [-k realm] [-f | -F] [-x] [-PN | -PO] command DESCRIPTION
Rsh connects to the specified host, and executes the specified command. Rsh copies its standard input to the remote command, the standard output of the remote command to its standard output, and the standard error of the remote command to its standard error. This implementa- tion of rsh will accept any port for the standard error stream. Interrupt, quit and terminate signals are propagated to the remote com- mand; rsh normally terminates when the remote command does. Each user may have a private authorization list in a file .k5login in his login directory. Each line in this file should contain a Ker- beros principal name of the form principal/instance@realm. If there is a ~/.k5login file, then access is granted to the account if and only if the originater user is authenticated to one of the princiapls named in the ~/.k5login file. Otherwise, the originating user will be granted access to the account if and only if the authenticated principal name of the user can be mapped to the local account name using the aname -> lname mapping rules (see krb5_anadd(8) for more details). OPTIONS
-l username sets the remote username to username. Otherwise, the remote username will be the same as the local username. -x causes the network session traffic to be encrypted. -f cause nonforwardable Kerberos credentials to be forwarded to the remote machine for use by the specified command. They will be removed when command finishes. This option is mutually exclusive with the -F option. -F cause forwardable Kerberos credentials to be forwarded to the remote machine for use by the specified command. They will be removed when command finishes. This option is mutually exclusive with the -f option. -k realm causes rsh to obtain tickets for the remote host in realm instead of the remote host's realm as determined by krb_realmofhost(3). -d turns on socket debugging (via setsockopt(2)) on the TCP sockets used for communication with the remote host. -n redirects input from the special device /dev/null (see the BUGS section below). -PN -PO Explicitly request new or old version of the Kerberos ``rcmd'' protocol. The new protocol avoids many security problems found in the old one, but is not interoperable with older servers. (An "input/output error" and a closed connection is the most likely result of attempting this combination.) If neither option is specified, some simple heuristics are used to guess which to try. If you omit command, then instead of executing a single command, you will be logged in on the remote host using rlogin(1). Shell metacharacters which are not quoted are interpreted on the local machine, while quoted metacharacters are interpreted on the remote machine. Thus the command rsh otherhost cat remotefile >> localfile appends the remote file remotefile to the local file localfile, while rsh otherhost cat remotefile ">>" otherremotefile appends remotefile to otherremotefile. FILES
/etc/hosts ~/.k5login (on remote host) - file containing Kerberos principals that are allowed access. SEE ALSO
rlogin(1), kerberos(3), krb_sendauth(3), krb_realmofhost(3) BUGS
If you are using csh(1) and put a rsh(1) in the background without redirecting its input away from the terminal, it will block even if no reads are posted by the remote command. If no input is desired you should redirect the input of rsh to /dev/null using the -n option. You cannot run an interactive command (like rogue(6) or vi(1)); use rlogin(1). Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here. RSH()
All times are GMT -4. The time now is 12:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy