Two ways to solve this problem:
the first: by looking for the software that takes up the port and shutting down
Reason: Other programs occupy 2425 ports of the Flying pigeon
Workaround: Use the netstat command to see which process is consuming the port
Format: Netstat-ano | Find "2425"
Results: UDP 0.0.0.0:2425 *:* 1716
The last 1716 is to occupy the process ID of the 2425 process, see what it is, can end the process directly, and then open the Flying pigeon on it.
About the netstat command can enter the command netstat/? See more
Displays the process ID in the Task Manager process list: View-Select column-On the hook PID can display the process's PID information.
The second way: By changing the default port
In fact, I did this to solve this mistake: in the shortcut ' attribute ' in the ' target ' path plus the port number you want to bind, I was instead: "C:documents and settingsadministrator desktop software Ipmsg.exe" 12345 12345 of which is the port number I want to bind, one problem is that both sides of the software should use the same port, that is, the two are changed to the same end of the slogan.