Error "bind(tcp) error. Can't support file attch error = 0"

[chaiw...@gmail.com]

I cannot send attach file on IPMessenger. IPMsg has error "bind(tcp) error. Can't support file attch error = 0". I uninstall prog. and fresh install but this error come again. Please help me.

[Hiroaki SHIROUZU]

It seems another program is already binding 2425/TCP port.

[chaiw...@gmail.com]

I've already check that not has any process bind this port.

How to solve this error ??

NOTE: I have changed to new network card before this problem happended.  

[Hiroaki SHIROUZU]

I don't know.

It seems your environment is not normal.

[NK]

I have exactly the same problem. No app is holding 2425 TCP i.e. its free and but IPMsg still raises this error on launch. I launched from command line with different ports like 2426 but the same behaviour exists. 

So, I guess more than 1 person has abnormal environment. But, what is normal? how do you define normal?

[SHIROUZU Hiroaki]

Please see.

Any way, bind of winsock returns not zero(=error), but WSAGetLastError is zero.

This behavior is not normal.

=========================================================================

Common：Please use a short title, and short sentences.

BugReport:  (Please use the below format)

   Version Info (principle, latest ver) :

   OS/Environment :

   ErrorMessage :

   Error Details / Conditions :

   Reproduction Steps :

Ignored Questions: No preliminary survey (reproduction steps, survey, etc.)

=========================================================================

2021年4月5日月曜日 12:40:30 UTC+9 NK:

[NK]

Hi,

For now, I have solved the issue by running the messenger on port 12425 on all nodes in my network, it's working fine. However, doesn't work on default 2425. All other machines were able to run on 2425 but file transfer with mine would not have been possible, so changed all.

PFB the details sought:

   Version Info (principle, latest ver) : 5.0.2/ latest version

   OS/Environment : Windows 10 2004

   ErrorMessage : bind(tcp) error. Can't support file attach error = 10013

   Error Details / Conditions : TCP port 2425 not in use by any other app (confirmed with ' netstat -a | find "2425" ' && also using Sysinternal's TCPView application) but IP messenger raises this error on launch. It's able to work with 2425 UDP.

   Reproduction Steps : Just launching the app raises the error.

Let me know if you need any additional info. Thanks.

[SHIROUZU Hiroaki]

Your error number is 10013, so it is not same.

You can confirm someone reserve tcp 2425 port in the following command in cmd.exe.

 netsh int ipv4 show excludedportrange tcp

2021年4月5日月曜日 21:25:27 UTC+9 NK:

[NK]

Yes, I see. It is definitely reserved. And, since I had not reserved the port myself, I looked it up. Turns out, Microsoft does it for Hyper-V and also some known malware attack points and apparently they are dynamic i.e. they change across reboots mostly.

Now, even if Microsoft got the port 2425 wrong then also this would be affecting a considerable number of users, yes?! Maybe you can include this error and potential resolution in the FAQ? Just a suggestion.

Thanks for you guidance, Hiroaki-san.

[SHIROUZU Hiroaki]

Good.

Thank you for your report.

2021年4月6日火曜日 14:01:36 UTC+9 NK: