ansaurus

Question

Answer 1

+1 A:

Without a kernel driver this is not possible. It is not legal in Windows to grab a socket handle in another process and close it proactively.

JaredPar 2009-03-13 19:31:47

Answer 2

A:

You could investigate SO_REUSEADDR.

Daniel Earwicker 2009-03-13 19:45:29

This will allow multiple people to bind but you won't be able to close the other handle.

JaredPar 2009-03-13 19:46:18

Answer 3

+1 A:

Only that process that owns the socket can close it, so all you could try is ending the process that owns the socket.

From the command line you can find the Process ID of the process using a particular socket using the -o option to netstat. For example:

netstat -noa | findstr LISTENING

I don't know how you do this programmatically in .NET though.

Dave Webb 2009-03-13 19:46:23

The application owned the socket, but it's went out of scope.

Malfist 2009-03-13 19:49:03

@Malfist: Then the (only) solution is to keep track of it somehow.

Henk Holterman 2009-03-13 20:01:23

Well, it's ordered to close, and then it goes out of scope but nestat still lists it as listening

Malfist 2009-03-13 20:26:14

How to get a specific socket and close it