I grepped for the port number 17398, so there might be some unrelated packets in there.
You could use a command similar to the following to allow trace the communication between your server running at port 17398 and your client(s):
Quote:
server log: After the last TCP Retransmission the connection timed out causing write(2) to return ETIMEDOUT which caused the server to issue a close(2) on the socket.
Are you sure that you're performing a close(). A close() on socket at the server side should cause a FIN segment to be sent to the client(s).
What do you mean by "shutdown the server". Is the process terminated? (e.g. with KILL).
This seems to indicate that there is a problem with your server code.
We're having problems getting disconnected from AIX with our telnet sessions.
I can't ping the server when this happens, either. Other serves can be pinged at the same time.
This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after... (0 Replies)
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
i am using Putty to do ssh to all the unix nodes that we have in our work environment. it is very strange that all my network connections will timeout quickly in 10 mins, it can either be a putty connection, sqlplus or toad. is there some setting that can help to prevent this. please let me know... (3 Replies)
Hello everyone. Thanks for reading. I am using Ubuntu 7.04 to experience this problem:
I have written my own programs that communicate to eachother and I am having a hard time detecting a TCP socket disconnect when the remote side's computer has a power-failure (for example).
On the computer... (6 Replies)
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Hi , My redhat 5 frequently disconnects from network. Once rebooted , network is working for one day or two. After that the NIC suddently stops working. Even if i give "#service network restart" or ifup eth0 commands it won't come up. I even tried reconfigure the network card. but no use. Only... (6 Replies)
Is there a way to have persistent terminal windows to redhat server across viewer disconnects? I can do that with the help of an extra MS Windows server and rdp, but is there a way of doing that without the Windows server?
Here's the scenario. I have multiple redhat servers (VMs) which have no... (3 Replies)
I have inherited and SCO OpenServer Release 6 server. The clients connect using telnet to get to a proprietary database application for Service tickets. The issue I am currently having is that the connection just stops abruptly and you can see "telnet session terminated" on the terminal emulation... (22 Replies)
Discussion started by: sean6605
22 Replies
LEARN ABOUT DEBIAN
tcpconnect
TCPCONNECT(1) General Commands Manual TCPCONNECT(1)NAME
tcpconnect - general TCP/IP client
SYNOPSIS
tcpconnect [-irv] [-l localaddr] host port
DESCRIPTION
tcpconnect creates a TCP/IP connection to a server running on the machine host, listening to port port. It then reads standard input and
sends to the remote server, and data received from the server is printed to standard output. When end-of-file is reached on both standard
input and the TCP/IP connection, tcpconnect terminates.
OPTIONS -i Terminate at end-of-file on standard input; don't wait for the server to close the connection.
-r Terminate when the remote server closes the connection; don't wait for end-of-file on standard input.
-v Verbose mode. Prints a message to standard error when the connection has been established.
-l addr:port
Bind the local end-point of the connection to IP address addr, TCP port port. Either the IP address or the port, but not both, may
be left out, meaning that the operating system gets to choose that part by itself.
SEE ALSO tcplisten(1), telnet(1), tcpbug(1).
BUGS
The names of the options are not yet finalized, and may change at a future release.
1997 April 13 TCPCONNECT(1)