Home > Net >  About "usually each socket address only allow the use of a" port to take up the problem
About "usually each socket address only allow the use of a" port to take up the problem

Time:10-07

To start my communication with this port, 8000, no times "usually each socket address only allow the use of a" this exception, CMD observation takes up the port of PID is 3368, tasklist | findstr searches "3368" output is empty, in the task manager did not find the corresponding process, is how to view the process to take up this port? Exit is the last time I did not shut down?

CodePudding user response:

You use CMD input net under the stat - a view if there was occupied, in fact you basically take up, port can not be multiple services of monitoring,

CodePudding user response:

.net stat - a no Spaces, write wrong, is the netstat -a

CodePudding user response:

reference 1 floor XBodhi. Response:
are you using CMD input net under the stat - a view whether occupied again, actually prompts you basically take up, the port can not be multiple services of monitoring,

I know it's being used, I want to know is who take up, when I go to check who take up the have not,

CodePudding user response:

You use hyperterminal sniffer, Telnet IP port,

Or do you find a third-party tools analysis came out,

CodePudding user response:

According to the pid program and the direct baidu

However, personal advice not to use do port 8000, 8000 too common,

CodePudding user response:

Netstat - b can see,


CodePudding user response:

reference 5 floor wanghui0380 reply:
based on pid check program, the direct baidu

However, personal advice not to use do port 8000, 8000 too common,

Thank you oh

CodePudding user response:

reference 6 floor XBodhi. Response:
netstat - b can see,

Thank you oh ~ won't appear, is sometimes appear, comes at a time when I can look at,

CodePudding user response:

Before you open the CLOSE

CodePudding user response:

Open before the CLOSE, if the code to run to Catch abnormal events, the existing connection not closed in time, can appear when establishing a connection again this hint,

CodePudding user response:

Loved
references to the tenth floor response:
open before you CLOSE, if the code to run to Catch abnormal events, the existing connection not closed in time, to establish a connection will appear when the prompt,

I know this? Thank you

CodePudding user response:



Task manager - & gt; Resources - monitor & gt; Network - & gt; Port
Use systemexplorer
Netstat - b

CodePudding user response:

The port was taken, a radish, a pit
  •  Tags:  
  • C#
  • Related