Sometime TCPview reveals many many lines such as (mywinmepc is the local
host)..
 
 >  TCP    mywinmepc:1103           localhost:1102         TIME_WAIT
 >  TCP    mywinmepc:1105           localhost:1104         TIME_WAIT
 >  TCP    mywinmepc:1107           localhost:1106         TIME_WAIT
 >  TCP    mywinmepc:1111           localhost:1110         TIME_WAIT
 >  TCP    mywinmepc:1113           localhost:1112         TIME_WAIT
 >  TCP    mywinmepc:1115           localhost:1114         TIME_WAIT
 >  TCP    mywinmepc:1117           localhost:1116         TIME_WAIT
 
ETC...
 
Some other "services" sit in TIME_WAIT state such as old POP3 calls.
 
Is there a way to clear these "TIME_WAIT" ports without resorting to
rebooting the pc?
 
(My pc.. is WinMe, configured as an ICS host, sharing a dialup with a
networked WinXP pc)
 

[Reply or follow-up to this message]

The default for a connection to remain in the TIME_WAIT state is 240 seconds after the session close is started. That is an adjustable Registry setting for TimeWaitDelay. Now if they are hanging around a lot longer than that, then the sessions are not being closed for some reason. When your system reaches it maximum open sessions, it will force the oldest session closed.

[Reply or follow-up to this message]

Do you have any idea what the maximum for "open" sessions is or where that is set? 
It seemed that there were far too many time_wait's lingering for hours.






On Sunday, February 26, 2006 at 8:07 pm, Jack Gulley wrote:
>...When your system reaches it maximum open sessions, 

>it will force the oldest session closed. 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum