06-08-2008
rsh is not working ,error :connection refused
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
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: Mace
4 Replies
2. IP Networking
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)
Discussion started by: Dudu1984
1 Replies
3. AIX
All,
I am using AIX 5.3.
while running the rsh command I am getting below error message.
------------------
A remote host refused an attempted connect operation.
------------------
.rhost file is updated with correct entry on both the servers. I.e.
Login ID Server name
in /etc/hosts... (12 Replies)
Discussion started by: anshu ranjan
12 Replies
4. Solaris
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)
Discussion started by: labdakos
4 Replies
5. UNIX and Linux Applications
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)
Discussion started by: lhareigh890
1 Replies
6. UNIX for Advanced & Expert Users
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)
Discussion started by: yanis
3 Replies
7. Linux
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)
Discussion started by: muzaffar.k
1 Replies
8. Debian
I have two computers running Debian 6.0 and one running Solaris 2.6 on a private network. The Debian computers can ftp to the Solaris computer but if a Debian computer is the destination the ftp connection is refused. I assume this is some security feature of Debian. What can I do to allow... (2 Replies)
Discussion started by: snorkack59
2 Replies
9. Shell Programming and Scripting
Hi I am trying to execute a shell script which is in unix server gs1. The script is below which basically connects to another unix server q15 and tries to get a file using FTP .
But i get error as "ftp: connect: Connection refused
Not connected.
Not connected."
Please help with if the below... (8 Replies)
Discussion started by: samrat dutta
8 Replies
10. UNIX for Dummies Questions & Answers
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
rshd(8c) rshd(8c)
Name
rshd - remote shell server
Syntax
/etc/rshd
Description
The command is the server for the routine and, consequently, for the program. The server provides remote execution facilities with authen-
tication based on privileged port numbers.
The is invoked by when it receives a connection on the port indicated in the cmd service specification. 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 reads characters from the socket up to a null (` ') byte. The resultant string is interpreted as an ASCII number, base
10.
3) If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr.
A second connection is then created to the specified port on the client's machine. The source port of this second connection is
also in the range 0-1023.
4) The server checks the client's source address. If the address is associated with a host for which no corresponding entry exists in
the host name data base the server aborts the connection. For further information, see
5) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as a user
identity to use on the server's machine.
6) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as the user
identity on the client's machine.
7) A null terminated command passed to a shell is retrieved on the initial socket. The length of the command is limited by the upper
bound on the size of the system's argument list.
8) The command validates the user according to the following steps. The remote user name is looked up in the password file and a is
performed to the user's home directory. If either the lookup or fail, the connection is terminated. If the user is not the supe-
ruser, (user id 0), the file or is consulted for a list of hosts considered equivalent. If the client's host name is in this file,
the authentication is considered successful. If the lookup fails, or the user is the superuser, the file in the home directory of
the remote user, is checked for the machine name and identity of the user on the client's machine. If the lookup fails, the connec-
tion is terminated.
9) A null byte is returned on the connection associated with the stderr and the command line is passed to the normal login shell of the
user. The shell inherits the network connections established by
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 (0 is returned in step 9 above upon successful completion of all the steps prior to
the command execution).
locuser too long
The name of the user on the client's machine is longer than 16 characters.
remuser too long
The name of the user on the remote machine is longer than 16 characters.
command too long
The command line passed exceeds the size of the argument list (as configured into the system).
Hostname for your address unknown.
No entry in the host name database existed for the client's machine.
Login incorrect.
No password file entry for the user name existed.
No remote directory.
The command to the home directory failed.
Permission denied.
The authentication procedure described above failed.
Can't make pipe.
The pipe needed for the stderr was not created.
Try again.
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
Restrictions
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.
See Also
rsh(1c), rcmd(3x), services(5), inetd(8c)
rshd(8c)