Like with CurrPorts, nothing happens when I try to close the connection in this tool. UPDATE 2: Found TCPView for Windows which show the process as "". It's no longer in Process Explorer, but still shows up in netstat and still stops the app from starting the listener. I right clicked on it and chose "Close Handle". UPDATE: I started up Process Explorer and did a search for 3000 and found this: (3000): 5552 I haven't seen this behaviour before and figured it was interesting enough to see if anyone has a solution. Private Sub Button1Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click Dim proc Process.GetProcessesByName('winword') For i As Integer 0 To proc.Count - 1 proc(i). TCP 0.0.0.0:3000 0.0.0.0:0 LISTENING 3116 Please check and test the following code, it will close all open Word windows.
Now, the app doesn't exist in the Task Manager, so I tried to find its PID and kill it, which led to this interesting result: C:\Users\username>netstat -o -n -a | findstr 0.0:3000 The Stop statement suspends execution, but unlike End, it does not close any. Apparently there's an instance of it still listening to the port because whenever I start it, it can't create a listener (C#, TcpListener, but that's irrelevant) because the port is already taken. I'm developing an app that listens on port 3000.
0 kommentar(er)
