icosahedron <email@example.com> wrote:
| It says "Now downloading installer program..." and sits there.
| Letting it wait for several hours makes no difference. Doing a
| netstat, I see www.franz.com:http CLOSE_WAIT on the list almost
| immediately after starting the program.
This, at least, is perfectly normal: CLOSE_WAIT is the state you
will be in for the entire transfer if your browser closes the
client-to-server side of the TCP/IP connection after sending the
Wait a second... That's backwards! CLOSE_WAIT is the state the
*server* will be in for the entire transfer if the client does a
"half-close", in which case the connection on *your* side should
be in FIN-WAIT-2 for the entire remainder of the transfer [after
briefly passing through FIN-WAIT-1].
See Figure 6 in <http://www.ietf.org/rfc/rfc793.txt> for the
full TCP state diagram. It suggests that your client has received
a FIN (close) from the server but then thinks it still has more
to send so has never formally closed its end (which would have
sent its own FIN to the server).
"the FIN-WAIT-2 problem" as seen from the *server's* point of view,
which you would be seeing as connections in CLOSE-WAIT. You might
ask someone at Franz if they're seening a lot of connections on
their server hung in FIN-WAIT-2 pointing to your address...
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607