07-04-2005
Put it back to NOWAIT.
Run it again and while it's ok, run "netstat -an" and find the socket for the connection. rshd reads the input for the command until it get EOF. Then it runs the command. So the socket will probably be half-closed and in CLOSE-WAIT. Now let the NT box get that message. Look again in "netstat -an". Did the socket change? If not, the problem is not on the unix system.
A possible cause of "connection reset by peer" is that the NT box is seeing a second box somewhere with the same IP address as the Unix system.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I use ssh to work on the server (OS X 10.4.x) remotely from home (Debian / OS X 10.5.3). If I leave my machine idle, I get disconnected after a couple of minutes. I get the following error message:
Read from remote host "server name": Connection reset by peer
Connection to "server name" closed.... (2 Replies)
Discussion started by: osxhawk
2 Replies
2. Shell Programming and Scripting
hi
i am connecting to a remote server using sftp protocol.
i am using the command like "sftp USER01@122.10.12.45"
then i got the error "Couldn't read packet: Connection reset by peer"
please help its very urgent (5 Replies)
Discussion started by: Satyak
5 Replies
3. IP Networking
hi all.
am running postgresql in a vm on debian server.
i have some client programs connecting to the db.
when i check the logs of postgresql i see "connection reset by peer"
can someone help me with this issue...
thanks. (1 Reply)
Discussion started by: coolatt
1 Replies
4. UNIX for Advanced & Expert Users
Hello
I'm facing the above problem while doing a performance run. I've a script which I'm launching from my windows desktop using mozilla. The script will invoke backend action on a Solaris host which in turn feeds the records to a driver located on a linux box(Cent OS).
What's happening is... (1 Reply)
Discussion started by: subramanyab
1 Replies
5. UNIX for Dummies Questions & Answers
I get this error when I log in through console:
"fatal: Read from socket failed: Connection reset by peer".
Can you tell me what this is and why it happens, and how to stop it? Thank you. (1 Reply)
Discussion started by: iamnew2solaris
1 Replies
6. UNIX for Dummies Questions & Answers
I have created a script to cat the contents of a log file and pipe it to head and tail so I can get specific lines.
When I do this I sometimes randomly get the error
"cat: write error: Connection reset by peer". It is completely sporatic and sometimes it doesnt happen and sometimes it does... (4 Replies)
Discussion started by: atelford
4 Replies
7. UNIX for Dummies Questions & Answers
Hi ,
when i run ,
tkt=/u01/ctrlfile/tkt.tmp
grep "TICKET NBR" $cdrFile | head -$count | tail -1 > $tkt
i got error
grep: writing output: Connection reset by peer
but some time its working withour error its working fine but some time i got this error
any help please (5 Replies)
Discussion started by: OTNA
5 Replies
8. UNIX for Advanced & Expert Users
Hello,
I have recently updated my AIX machine from version 6.1.7.5 to 6.1.9.1 and i noticed that the errpt of the server is full of ssh messages like the one below:
sshdprocess_id>]: fatal: Read from socket failed: Connection reset by peer
Does anyone knows if this a known bug of the ssh... (15 Replies)
Discussion started by: omonoiatis9
15 Replies
9. UNIX for Dummies Questions & Answers
Hello to all,
i have a problem when trying to estabilish a sftp connection.
i setup a sftp server (i used feeFTPd) and i'm now trying to connect from two different machines.
from the first one everything is fine:
$ sftp -vvv user@xxx.xxx.xxx.xxx
Connecting to xxx.xxx.xxx.xxx...... (9 Replies)
Discussion started by: dc26
9 Replies
10. Red Hat
Hi Guys,
I can't SSH to a remote system - connection reset by peer..any ideas ?
-The Source is Linux, the Remote is Windows
-The remote has OpenSSH running on Port 22 - Telnet confirms port is open
-User1 has a RSA2 Key (2048) key, which is capture in the 1010101-pub.key specified by the... (1 Reply)
Discussion started by: stevie_velvet
1 Replies
LEARN ABOUT ULTRIX
connect
connect(2) System Calls Manual connect(2)
Name
connect - initiate a connection on a socket
Syntax
#include <sys/types.h>
#include <sys/socket.h>
connect(s, name, namelen)
int s;
struct sockaddr *name;
int namelen;
Description
The call initiates a connection on a socket. The parameter s is a socket. If the socket is of type SOCK_DGRAM, this call permanently
specifies the peer to which datagrams are sent. If it is of type SOCK_STREAM, this call attempts to make a connection to another socket.
The other socket is specified by name, which is an address in the communications space of the socket. Each communications space interprets
the name parameter in its own way. The size of the structure sockaddr is namelen.
Return Values
If the connection or binding succeeds, then 0 is returned. Otherwise, a -1 is returned, and a more specific error code is stored in errno.
Diagnostics
The call fails under the following conditions:
[EBADF] The s is not a valid descriptor.
[ENOTSOCK] The s is a descriptor for a file, not a socket.
[EADDRNOTAVAIL]
The specified address is not available on this machine.
[EAFNOSUPPORT] Addresses in the specified address family cannot be used with this socket.
[EINPROGRESS] The connection is requested on a socket with FNDELAY set (using
[EISCONN] The socket is already connected.
[ETIMEDOUT] Connection establishment timed out without establishing a connection.
[ECONNREFUSED] The attempt to connect was forcefully rejected.
[ENETUNREACH] The network is not reachable from this host.
[EADDRINUSE] The address is already in use.
[EFAULT] The name parameter specifies an area outside the process address space.
[EWOULDBLOCK] The socket is nonblocking, and the connection cannot be completed immediately. You can select the socket for writing by
using the system call while it is connecting.
The following errors are specific to connecting names in the ULTRIX domain:
[ENOTDIR] A component of the path prefix is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
[ENOENT] The named socket does not exist.
[EACCES] Search permission is denied for a component of the path prefix.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
See Also
accept(2), fcntl(2), getsockname(2), select(2), shutdown(2), socket(2)
connect(2)