TCP Sticky Ports?

[WheeDoggy]

Win 98SE/IE6
(Is this a TCP problem or something to do w/ IE6?)

I have noticed that occasionally in the open port list that even after closing an open port (whether manually or it times out), it will remain open listening.

Only happens in O/B sends TO http 80, local send port# varies according to available consecutive port.

ex.: local:XXXX x.x.x.x:80 CLOSE_WAIT

(Sometimes CLOSE_WAIT will not timeout and exit and I need to close manually)

Either way,
Sometimes after x-mit, 0.0.0.0:XXXX 0.0.0.0:80 LISTENING
will not exit until re-boot.
This is seemingly random in occurrence as I see no pattern in instances.

I hope I worded this question correctly.... :0

Thanks

 

[Laopang]

As I know, in the serve side (passive closed)

ESTABLISH(receive FIN, send ACK)->CLOSE_WAIT(Application close the FD)->LASE_ACK(receive ACK)->CLOSE

So ,if your application comes into CLOSE_WAIT, that means your application does not close the relevant FD(socket)in time.

Check your application and make sure that you have closed the socket as soon as the operation of it are completed.

My experience is in Linux, I have not replanted my application into Windows, so I don't be sure that when a process is closed, if all its socket will be closed. In linux, when a process is cancelled, all resource is released.

 

[WheeDoggy]

Hi Laopang

Thanks for the reply.

I like how you said "In linux, when a process is cancelled, all resource is released." which opens the door for some Micro$oft bashing but I'll resist the temptation.

I still find it a bit wierd that even when IE does appear to close the socket that it will remain listening on occasion.

It is however always IE when this "phenomenon" does occur.

Regards