Wireshark-users: Re: [Wireshark-users] Question on Fin/ack
From: Jack Jackson <jack@xxxxxxxxxxxxxxx>
Date: Mon, 26 Mar 2007 14:16:57 -0700
Remember that the connection is not closed until both ends have sent fin and both fins have been acked.

Another consideration is that a TCP connection moves to the Timed Wait state after both fins have been acked. While the connection is in Timed Wait the TCP stack must remember the IP addresses and ports of both ends of the connection. Timed Wait is often 1-2 minutes. If the print server has limited data space, it might refuse new connections until table entries free up if many connections are made in a short period of time.

At 11:39 AM 3/26/2007, Jamie Crawford wrote:
Hi,
Thanks for the response. I got to thinking about the same thing about maybe only accepting one session at a time and called the printer manufacturers support. We were both right, it will only handle one session at a time and will throw an error if you try to connect twice. I've escalated this up to make a code change on the server side to quit probing the printer and sending the job before the printer sends the ack to kill the probe session, or just quit probing the printer before the print job. Thanks for taking your time to check it out.