forte bind error [message #1722762] |
Mon, 08 February 2016 22:02 |
meon eclipse Messages: 3 Registered: February 2016 |
Junior Member |
|
|
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 #1722876 is a reply to message #1722762] |
Tue, 09 February 2016 21:22 |
|
Hi,
my knowledge on Windows is rather thin. I did a quick google search on the error code. Some people are reporting that it could be from a firewall or anti-virus software. I also saw one report that Windows Defender could cause the problem.
I hope this helps.
Alois
|
|
|
Re: forte bind error [message #1722877 is a reply to message #1722876] |
Tue, 09 February 2016 21:45 |
meon eclipse Messages: 3 Registered: February 2016 |
Junior Member |
|
|
Hi, Thank you for the response. I have tried turning both the firewall and anti-virus (including windows defender) software off, but the problem seems to be something else. There was a discussion on the some ports being marked as exclusive for other programs, but this does not seem to be the case either. I have also tried booting in safe mode, but that does not help either. Anyway, at least it seems like a problem on just my pc (if not windows 8 ). And how tragic for one of the bad ports to be 61499...
[Updated on: Tue, 09 February 2016 21:46] Report message to a moderator
|
|
|
|
|
Re: forte bind error [message #1728001 is a reply to message #1723977] |
Wed, 30 March 2016 07:31 |
Jose Maria Jesus Cabral Lassalle Messages: 199 Registered: February 2016 |
Senior Member |
|
|
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.02904 seconds