"netstat" tells the truth but the truth, as always, may
be more complex than you were expecting.  A closed TCP port can
hang around for quite a while in state FIN_WAIT_2, depending on
the vagaries of the TCP implementation at the far end.  The
port's still closed, it's just that kernel resources haven't
been freed up yet.  They will be.  Meanwhile, it still shows
up in "netstat".

Mike O'Brien