Another good test if the entry in .rhosts might be the problem is, to just login via ssh from the box that tries to get access via rsh and do a
and check the hostname given in the last field surrounded by brackets. This is the name that should be placed into the .rhosts. If not necessary you can leave usernames out. Should work only anyway if you keep the UIDs on the systems the same for the user id.
I installed Openserver 5.0.7 and I cannot telnet to the localhost and I can't telnet from my old SCO 3.2.42 to the new SCO machine but I can ping the new machine and it will telnet to the old machine. (2 Replies)
I'm trying to use rsh command to read a variable on a remote machine. I can rlogin with no problem. If I rsh HOST I also get connection like with rlogin. There is no need for passwords. But when I rsh HOST COMMAND it waits 30 seconds then gives me a connection refused error message. Any ideas?
... (4 Replies)
Hi there,
Anything will help.
I have running server on computer and want to connect from some clients.
Server:
memset(&hints, 0, sizeof(hints));
hints.ai_family = domain;
hints.ai_socktype = SOCK_STREAM;
error = getaddrinfo("localhost", "8300", &hints, &res0);
if (error)
{
... (1 Reply)
rsh is not working
command:rsh targethost -l username command
Error:Connection refused
I checked on the server rshd was not working.
Tried to start by /usr/sbin/in.rshd start
# ./in.rshd start
rshd: getpeername: Socket operation on non-socket
Please help (1 Reply)
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
I dont' what happened with my servers (test servers only) but I just noticed that suddenly I cannot up the domain anymore (Sun Java System Application Server 9.1_01).
a. server.log
org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the... (1 Reply)
Hello,
I am doing an rsh connection to server2.
I want to perform several command on server2.
I.E:
i=1
rsh server1 -l username "z=$i;`script.ksh`"
(1)Is this the right way to give z value to be used on server2?
(2) Is this the right way to run a script on server2? (1 Reply)
Hi- While trying ftp from AIX to Windows im getting below error. Can anyone share ur views on this topic.
root@AB101# ftp -n 10.192.168.68
ftp: connect: A remote host refused an attempted connect operation.
ftp>
Thanks. (3 Replies)
Hi all,
i got stuck with telnet issue, I am not able to telnet on 4001 port it show connection refused.
with default port it will open
# telnet 127.0.0.1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Fedora release 14 (Laughlin)
Kernel 2.6.35.6-45.fc14.i686 on... (1 Reply)
Hi, i checked on rhel VPS is running sshd
(service ssh status)
But i cant connect via putty: "Network error: Connection refused"
Please which log file in my centos rhel linux i need to watch or what are steps to do to discover cause? (3 Replies)
Discussion started by: postcd
3 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