Login or Register to Ask a Question and Join Our Community


Solaris

TCP Problem

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris TCP Problem
# 1  
Old 04-17-2008
TCP Problem
I am running a Java Client on Solaris 9 which communicates with the Server using TCP/IP.

The client transmits a FIN packet to server. The server sends a ACK, FIN enters LAST_ACK state and then waits for ACK from client. The client did not respond back leaving the server in LAST_ACK itself. Also the Client connects with the server on a fixed port, so the new connection attempt also results in a failure.

The point is, the client is written not to close the connection. I am not sure how and why the client sends a FIN. One more thing is the client is killed every day but this might not lead to this problem as ideally on killing, only a RST shud be sent to the server. The client is written on Java which will properly close the connection on exit.

My question is, Is der are any TCP/IP issue with the solaris stack which lead me to this problem? The server side is clean(even LAST_ACK sockets are teared down after 1000 seconds after which connection attempt is successful).
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Problem and question with TCP

Hi guys , i write this message for a doubt, a time ago i wrote a client/server program with TCP/IP in Linux. When i tested the program flooding the server with messages of 1024 bytes (Or 1025 bytes i dont remember exactly the number but was more that 1000 bytes) in certain point a message was... (5 Replies)
Discussion started by: Kovalevski
5 Replies

2. UNIX for Advanced & Expert Users

Bizzare TCP/IP problem

Hi all. I have a really really weird problem that I've been working on for days. The problem manifested as users cannot connect to our web servers via SSH when they're using our wireless network. Here's where it gets weird: - Clients from anywhere other than the wireless subnet can... (4 Replies)
Discussion started by: pileofrogs
4 Replies

3. Programming

Problem with tcp server

Hello @ all, I hope you can give me some advice :b: I will be following code for a tcp server and doStuff () function, the clients treated. From some point, I have several identical clients (zombies, I think), the same records in the database write. Has anyone an explanation? What can I... (1 Reply)
Discussion started by: yumos
1 Replies

4. Programming

epoll problem with tcp connect()

I am using epoll to manage my network connections. At the client side, the idea is to send the message upon detecting the completion of connect(). I've set up the socket to be nonblocking, then after calling of connect(), I add the socket into the epoll and wait on the event to be detected from... (0 Replies)
Discussion started by: tuesday420
0 Replies

5. Shell Programming and Scripting

tcp/ip and memory problem

how the data from disk is loaded into memory and then it supplied to tcp/ip packet. how i can trace the no of pages loaded in memory by that process and rate of context switch for that process. (1 Reply)
Discussion started by: amar20
1 Replies

6. Red Hat

tcp/ip problem

how the data from disk is loaded into memory and then it transfered to tcp/ip packet. how i can find how many pages are loaded into memory by that process what is the rate of context switch for that process. (5 Replies)
Discussion started by: amar20
5 Replies

7. AIX

TCP/IP socket binding problem

I have what appears to be a unique socket problem, although admittedly my tcp/ip programming experience is relatively limited. I have a AIX server process using TCP/IP berkely sockets, and a Windows (C#) process. The windows process takes input from a user and sends a message to the Unix... (1 Reply)
Discussion started by: adiaconou
1 Replies

8. IP Networking

WinXP and TCP/IP Problem

Hi Eveyone, I have A small problems maybe some one can help me. I'm running a small network at home with internet access. Two PC's have Win XP and one has Win98se. I have them all hook up on a SMC router. ALL windows firewall are off and and harddrive sharing is on. I am using DCHP network... (3 Replies)
Discussion started by: Peterh
3 Replies

9. IP Networking

IBM-AIX and TCP/IP Problem

I am having a problem and I feel it's network related. I have an RS6000 running AIX. I use a terminal emulation program that allows me to connect to my server via TCP/IP. When I try and make the connection, it takes F-O-R-E-V-E-R to get a login prompt on the screen. I also cannot ftp to... (3 Replies)
Discussion started by: Docboyeee
3 Replies

10. IP Networking

tcp problem with port

I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message, Exec format error cannot bind a name to the port. As far as I know the port is not being used by another client. How... (1 Reply)
Discussion started by: lopez
1 Replies
Login or Register to Ask a Question

LEARN ABOUT SUSE

ss

SS(8)							      System Manager's Manual							     SS(8)

NAME

       ss - another utility to investigate sockets

SYNOPSIS

       ss [options] [ FILTER ]

DESCRIPTION

       ss  is  used  to  dump socket statistics. It allows showing information similar to netstat.  It can display more TCP and state informations
       than other tools.

OPTIONS

       These programs follow the usual GNU command line syntax, with long options starting with  two  dashes  (`-').   A  summary  of  options	is
       included below.

       -h, --help
	      Show summary of options.

       -V, --version
	      Output version information.

       -n, --numeric
	      Do now try to resolve service names.

       -r, --resolve
	      Try to resolve numeric address/ports.

       -a, --all
	      Display all sockets.

       -l, --listening
	      Display listening sockets.

       -o, --options
	      Show timer information.

       -e, --extended
	      Show detailed socket information

       -m, --memory
	      Show socket memory usage.

       -p, --processes
	      Show process using socket.

       -i, --info
	      Show internal TCP information.

       -s, --summary
	      Print  summary  statistics. This option does not parse socket lists obtaining summary from various sources. It is useful when amount
	      of sockets is so huge that parsing /proc/net/tcp is painful.

       -4, --ipv4
	      Display only IP version 4 sockets (alias for -f inet).

       -6, --ipv6
	      Display only IP version 6 sockets (alias for -f inet6).

       -0, --packet
	      Display PACKET sockets.

       -t, --tcp
	      Display only TCP sockets.

       -u, --udp
	      Display only UDP sockets.

       -d, --dccp
	      Display only DCCP sockets.

       -w, --raw
	      Display only RAW sockets.

       -x, --unix
	      Display only Unix domain sockets.

       -f FAMILY, --family=FAMILY
	      Display sockets of type FAMILY.  Currently the following families are supported: unix, inet, inet6, link, netlink.

       -A QUERY, --query=QUERY
	      List of socket tables to dump, separated by commas. The following identifiers are  understood:  all,  inet,  tcp,  udp,  raw,  unix,
	      packet, netlink, unix_dgram, unix_stream, packet_raw, packet_dgram.

       -D FILE
	      Do not display anything, just dump raw information about TCP sockets to FILE after applying filters. If FILE is - stdout is used.

       -F FILE, --filter=FILE
	      Read filter information from FILE.  Each line of FILE is interpreted like single command line option. If FILE is - stdin is used.

       FILTER := [ state TCP-STATE ] [ EXPRESSION ]
	      Please take a look at the official documentation (Debian package iproute-doc) for details regarding filters.

USAGE EXAMPLES

       ss -t -a
	      Display all TCP sockets.

       ss -u -a
	      Display all UDP sockets.

       ss -o state established '( dport = :ssh or sport = :ssh )'
	      Display all established ssh connections.

       ss -x src /tmp/.X11-unix/*
	      Find all local processes connected to X server.

       ss -o state fin-wait-1 '( sport = :http or sport = :https )' dst 193.233.7/24
	      List all the tcp sockets in state FIN-WAIT-1 for our apache to network 193.233.7/24 and look at their timers.

SEE ALSO

       ip(8), /usr/share/doc/iproute-doc/ss.html (package iproutedoc)

AUTHOR

       ss was written by Alexey Kuznetosv, <kuznet@ms2.inr.ac.ru>.

       This manual page was written by Michael Prokop <mika@grml.org> for the Debian project (but may be used by others).

																	     SS(8)