× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2004

Re: Tracing Client TCPIP communications

Ok, that makes more sense, but which end isn't returning
data, and which end is closing (ie client or server).

Is there anything more that you could explain?  For example
which end (client or server) seems to be having the problem
during the handshake?  The logs we have don't say much at
all about what's going on.  

Thanks for your help, John.

On Sat, 10 Jan 2004 13:32:31 -0600
 "John Brandt Sr." <pgmr@xxxxxxxxxxxxxxx> wrote:
> It means that the socket is not returning any data and is
> being force closed
> by the remote location.
> 
> John Brandt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.