01-14-2003
Rlogin???
From any computer on our network when you rlogin into one machine (this only happens on this machine) it'll hang for about 3 minutes before loggin into that machine. If your sick of waiting you can do a <ctrl> C and then it'll rlogin into the machine it is meant to BUT it wont keep the shell enviroment for that user.
I got no idea what it could be. I checked all the user scripts .login .cshrc all soucring files it's calling. I can't find anything.
Any idea's what could be causing this issue?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a script and need to use rlogin to access "server1".
As there will be different servers used and there will be different usernames and passwords.
Is it possible to pass the server name, username and password as arguments on the command line and the script work from there.
... (2 Replies)
Discussion started by: seaten
2 Replies
2. Shell Programming and Scripting
I'm comparing a table from two databases on two different servers to check for equality.
1. How do I use rlogin from a script , is it like this ?
rlogin -l $username $server1
where $username and $server1 are passed from the command line.
2.create a copy of that table, compress it and... (3 Replies)
Discussion started by: seaten
3 Replies
3. Cybersecurity
does anyone know how to stop rlogin to my sunsolaris
so I have 2 machines...I can not telnet one becouse that is not allowed but I can telnet the other and do rlogin to first one..I want to stop that..
so..
telnet A from C machine - works
telnet B from C machine - does not work
but... (3 Replies)
Discussion started by: amon
3 Replies
4. IP Networking
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 Dummies Questions & Answers
hi
i got 3 boxes, boxA, boxB, boxC
i can do the below
boxA> ufsdump 0fu boxB:/mydirectory/myfile /myfile
boxA> rlogin boxB is okay
but when i do the below
boxA> ufsdump 0fu boxC:/mydirectory/myfile /myfile, system says error,
boxA> rlogin boxC got error
on... (5 Replies)
Discussion started by: yls177
5 Replies
6. UNIX for Dummies Questions & Answers
i got a dout in rlogin . whether rlogin is same as telnet (1 Reply)
Discussion started by: shanmugam
1 Replies
7. UNIX for Advanced & Expert Users
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
8. Shell Programming and Scripting
Hi all,
i need to remotely execute a couple of commands on anyother server, but rsh is not allowed. for that matter i am bound to use rlogin. so what i am trying to do in the script is :
1) rlogin asad
2) Wait for Login prompt
3) Waiting for Password Prompt
4) Once authenticated, execute... (4 Replies)
Discussion started by: asadlone
4 Replies
9. IP Networking
Hai guys,
Both "rlogin" and "telnet" are used to login remote host.Is there any differece between these 2 commands? (or) are both same?
Thanks (1 Reply)
Discussion started by: Felicia23
1 Replies
10. Solaris
Guys, I'm running solaris 9 on two systems: 1 and 2, let's say.
From 1, if I say rlogin 2, i can just login. No passwd prompt!
From 2, if I say rlogin 1, it asks for the passwd. (able to login with a passwd)
But, they both have the same config files, same set up, same network etc.
What... (13 Replies)
Discussion started by: the_red_dove
13 Replies
LEARN ABOUT OSX
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD