Re: How to "kill" a tcp port...

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jako Menkveld (jako.menkveld_at_envalue.ch)
Date: 02/04/05 

Date: Fri, 4 Feb 2005 10:31:04 -0000

"Aquila Deus" <aquila.deus@gmail.com> wrote in message
news:1107512389.581833.316910@g14g2000cwa.googlegroups.com...
> Jako Menkveld wrote:
>> Rob
>>
>> I'll give that a try. Are you saying there is no way of closing the
> socket
>> from the Server side then?
>
> 1.If the server process (not appdomain) dies without closing the port,
> the OS will kill it.

I also thought this would be the case, but for some reason the OS (Win XP by
the way), keeps the connection open because the client-side was still
connected. It doesn't make a lot of sense, but that's what seems to happen.

>
> 2.TCP itself should give the client an error if the server dies without
> closing the connection. Maybe it is ignored by .NET remoting?

I can really comment on that, once again, I would have expected something
like that to happen, but no luck there either.

>
> What I don't understand is that your netstat shows the port was still
> listening after server quit.. Did the server process really quit?
>

The server process did die (can't see it in Task Manager for any user). The
interesting thing is that if I run netstat -o and get the process ID of the
listener, I can't find that process ID in Task Manager either and it is
different from the original server's process ID.

Relevant Pages

  • Re: Why Would ResponseStream().Read return zero bytes when not at end of file?
    ... there is no network requirement that the number of bytes delivered by the server before closing the connection is identical to the number of bytes the server advertised in the HTTP response. ... The advertised length is just that: an advertisement. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Implications of not closing db connection?
    ... "vivienne wykes" wrote in message ... > an issue for other server users by not closing the db connection. ...
    (comp.lang.java.programmer)
  • Re: How to "kill" a tcp port...
    ... Are you saying there is no way of closing the ... keeps the connection open because the client-side was still ... > 2.TCP itself should give the client an error if the server dies without ... The server process did die (can't see it in Task Manager for any user). ...
    (microsoft.public.dotnet.general)
  • Re: How to "kill" a tcp port...
    ... Are you saying there is no way of closing the ... keeps the connection open because the client-side was still ... > 2.TCP itself should give the client an error if the server dies without ... The server process did die (can't see it in Task Manager for any user). ...
    (microsoft.public.dotnet.framework)
  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)