Wireshark mailing list archives

Re: Sockets not closing


From: Jaap Keuter <jaap.keuter () xs4all nl>
Date: Fri, 27 Nov 2009 11:43:15 +0100

Hi,

That's the final state when closing a TCP connection. It's timed out after
2MSL, returning to the closed state. Check your Stevens.

Thanks,
Jaap

On Fri, 27 Nov 2009 13:03:36 +0530, "Mohan Radhakrishnan"
<mohanr () fss co in> wrote:
Hi,
        
 I am really not sure if wireshark can be of much help here. We see the
following issue in many of our servers when connecting to Oracle. Does
anyone have any suggestions ?
 Would we know if packet captures can be of any help here ? Just trying
to ask this group because the collective experience with TCP can be very
helpful.
 
  TCP    10.177.44.131:1026     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1030     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1031     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1032     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1033     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1036     10.177.44.34:1521      TIME_WAIT
  TCP    10.177.44.131:1037     10.177.44.34:1521      TIME_WAIT

 
 
Thanks,
Mohan
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe


Current thread: