forte bind error [message #1722762] |
Mon, 08 February 2016 17:02  |
Eclipse User |
|
|
|
Hello,
I am getting WSA Error 10013 when running forte on windows 8. I got the error code by printing out the return value WSAGetLastError(). Additionally, I figured that only some ports like 61499, 61500, 61501 give this error. If I run forte on a port like 60000, 20000, the sockets are successfully created. I have also used the netsh show command to see if there was an exclusive right on the ports above, but there was no exception for the ports above. Previously I was able to solve this problem by just restarting the computer, but now I can't even do that.
Does someone know about this problem?
Attached image of the error. It says no error, but the error is really 10013 which I got by debugging forte.
Thank you.
|
|
|
|
|
|
|
Re: forte bind error [message #1728001 is a reply to message #1723977] |
Wed, 30 March 2016 03:31   |
Eclipse User |
|
|
|
Even though I posted a possible solution, I didn't have the problem back then. After a while I got the problem, applied my own solution and it didn't work. The binding returned the error 10013 (WSAEACCES), but actually the port wasn't in use.
This problem is apparently not because the port is already used, but because of permissions issues.
This post
http://stackoverflow.com/questions/21791436/wseacces-error-binding-to-socket-on-windows-server-2008
helped me, and in my case the Internet Connection Sharing service wasn't running, at least I didn't find it, but my problem was that my LAN interface was set to allow sharing the internet connection to other network. Even though the other network wasn't on, the problem dissapeared when I unchecked the internet sharing option.
So, in case someone has a problem with binding in FORTE, try to turn off everything related to internet sharing.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04581 seconds