![]() ![]() You don't have to be the current process owning the socket to close it. Killing the process that owns the connection is really a bad idea here because this would take down the server (all users would lose functionality when we just want to selectively and temporally drop this one connection). Normally, I would add a firewall to do the job, but this would take some time, and I was in an emergency situation. this user is doing bad things, we asked them to stop but the connection didn't get dropped somewhere along the way). Then, I discover that this connection is undesired (e.g. A client makes a connection and port 56789 is allocated for it. I want to close/kill them.ĮDIT, for clarification: Let's say that my server listens TCP port 80. I don't want answers on how to monitor them (I already do this). But the answers looked like a manual page of netstat or netsh commands focusing on how to monitor the ports. Googling about this, I saw some people asking the same thing. Does somebody knows how to close a TCP or UDP socket for a single connection via windows command line? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |