Re: How to "kill" a tcp port...
From: Aquila Deus (aquila.deus_at_gmail.com)
Date: 02/04/05
- Next message: Dmitriy Lapshin [C# / .NET MVP]: "Re: How do I make a C# UserControl into an OCX file for VB6 use?"
- Previous message: Jako Menkveld: "Re: how to auto-update a text file before closing it"
- In reply to: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Next in thread: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Reply: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Messages sorted by: [ date ] [ thread ]
Date: 4 Feb 2005 02:19:49 -0800
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.
2.TCP itself should give the client an error if the server dies without
closing the connection. Maybe it is ignored by .NET remoting?
What I don't understand is that your netstat shows the port was still
listening after server quit.. Did the server process really quit?
- Next message: Dmitriy Lapshin [C# / .NET MVP]: "Re: How do I make a C# UserControl into an OCX file for VB6 use?"
- Previous message: Jako Menkveld: "Re: how to auto-update a text file before closing it"
- In reply to: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Next in thread: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Reply: Jako Menkveld: "Re: How to "kill" a tcp port..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|