clearing TIME_WAIT - how?

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)

Did you post the same in the WinXP NG, Ogg?
If not, maybe you should?

Harry.


"Ogg" wrote in message
...
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)

webster72n wrote:

Did you post the same in the WinXP NG, Ogg?
If not, maybe you should?

Harry,

So not only are those not running Win Me apparently unwelcome in these NGs
but also asking questions about Win Me are now also inappropriate. g So
what exactly do you think should be posting in these NGs and what should
the question be about? :-)

Note Ogg's network ICS host is running Win Me which by now I'm sure you
understand means he is running Windows Millennium. vbg

--
Mike Maltby

WHY?? Everyone here (but you) is using both XP and ME....so I am quite
sure the gurus can help him.

Figgs, muttering 4 letter words to herself...

"webster72n" wrote in message
...

Did you post the same in the WinXP NG, Ogg?
If not, maybe you should?

Harry.


"Ogg" wrote in message
...
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)

lol Stick a patch on g
Joan


Heather wrote:

Figgs, muttering 4 letter words to herself...

Note Ogg's network ICS host is running Win Me which by now I'm sure
you understand means he is running Windows Millennium. vbg

Don't bet your *beer money* on that one, lol.

Figgs

"Mike M" wrote in message
...
webster72n wrote:

Did you post the same in the WinXP NG, Ogg?
If not, maybe you should?

Harry,

So not only are those not running Win Me apparently unwelcome in these
NGs but also asking questions about Win Me are now also inappropriate.
g So what exactly do you think should be posting in these NGs and
what should the question be about? :-)

Note Ogg's network ICS host is running Win Me which by now I'm sure
you understand means he is running Windows Millennium. vbg

--
Mike Maltby

Ogg,

Why do you want to clear these? To do so close the app or operating
system service that is using the ports concerned. Note though that all
are directed at the localhost so it's not as if they are open and waiting
on the net. Like yourself I'm perhaps a little intrigued at the number of
posts in this state.

Rather than TCPView what does netstat (run from a DOS prompt) have to say?
Does it show the same ports in the same state?
--
Mike Maltby



Ogg wrote:

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)

LOL!! Did that and so far, so good. At Day 19 or so.....and no major
cravings. Go get the patch and join me.

Only one day of the *bitchies*. But that was Ron's fault, lol. He
spoke to me. Silly man!!

XX Figgs

"Joan Archer" wrote in message
...
lol Stick a patch on g
Joan


Heather wrote:

Figgs, muttering 4 letter words to herself...

lol Yes I've got to get the patches, these lozenges are no good for me
they are making me feel quite ill and worse than actually smoking, don't
worry haven't smoked since Friday night.
Joan


Heather wrote:
LOL!! Did that and so far, so good. At Day 19 or so.....and no
major cravings. Go get the patch and join me.

Only one day of the *bitchies*. But that was Ron's fault, lol. He
spoke to me. Silly man!!

XX Figgs

Heather wrote:

Note Ogg's network ICS host is running Win Me which by now I'm sure
you understand means he is running Windows Millennium. vbg

Don't bet your *beer money* on that one, lol.

LOL

However from Ogg's post:
"(My pc.. is WinMe, configured as an ICS host, sharing a dialup with a
networked WinXP pc)"
--
Mike Maltby