Error Code 10048
"Binding socket failed: Error code 10048"
"Binding socket failed: Error code 10048"
EDIT: Fixed, both instances were using the same port. If anyone runs into this issue, change one instance's port to something else.
Last edited by Twinki on Sun Nov 02, 2014 8:53 pm, edited 3 times in total.
-
- Filter Inserter
- Posts: 778
- Joined: Sun Sep 07, 2014 12:59 pm
- Contact:
Re: "Binding socket failed: Error code 10048"
If you're running two instances on the same PC, one of them will need to use a different port. Two applications can never use the same port at the same time.
I don't have OCD, I have CDO. It's the same, but with the letters in the correct order.
Re: "Binding socket failed: Error code 10048"
Well only one instance is hosting the actual server, so only one should be using the port right? I'll go ahead and try two different ports.Boogieman14 wrote:If you're running two instances on the same PC, one of them will need to use a different port. Two applications can never use the same port at the same time.
EDIT: Fixed.
Re: "Binding socket failed: Error code 10048"
yeah, just copy the whole directory and you are good to go.
But this principle is maybe the key for the 3 player problem.
Communicate with two system on the same port outside of private network may result in problems.
Is there any way to have 2 Ports open for one network?
But this principle is maybe the key for the 3 player problem.
Communicate with two system on the same port outside of private network may result in problems.
Is there any way to have 2 Ports open for one network?
Re: "Binding socket failed: Error code 10048"
you can change the port the game uses in Config\config.ini , port=34197 (near the bottom)
I'm running 2 clients on one computer for mod testing, and _aD joined me over the internet without any problems for a 3 player game. I forward 2 ports to my computer (34197 and 34198), one for each client.
I'm running 2 clients on one computer for mod testing, and _aD joined me over the internet without any problems for a 3 player game. I forward 2 ports to my computer (34197 and 34198), one for each client.
Re: "Binding socket failed: Error code 10048"
well this is exactly our problem.
I tried it like you mentioned.
I opened port 34197 and 34198 for 192.168.0.10 (my local machine which opens two instances) in my router.
I changed the port in the config for the host 34197 and the second client who will join to 34198.
Now I hosted from the 34197 instance and joined from the other with 192.168.0.10.
Now drs tried it from outside the network and same problem as before. He kicked me but stayed in game with the server.
What's the problem? I guess even if I'm joining over public IP instead of local ip (192.168...) it would be happend.
?!?
_aD was from outside your network?
You and _aD had same bit version (32/64)?
I tried it like you mentioned.
I opened port 34197 and 34198 for 192.168.0.10 (my local machine which opens two instances) in my router.
I changed the port in the config for the host 34197 and the second client who will join to 34198.
Now I hosted from the 34197 instance and joined from the other with 192.168.0.10.
Now drs tried it from outside the network and same problem as before. He kicked me but stayed in game with the server.
What's the problem? I guess even if I'm joining over public IP instead of local ip (192.168...) it would be happend.
?!?
_aD was from outside your network?
You and _aD had same bit version (32/64)?
Re: "Binding socket failed: Error code 10048"
You need to log in the second client via the public ip as well, not the local 192.168.0.10 , because the server will send drs the ip of the 3rd machine: 192.168.0.10 , and he can't connect to that.
Re: "Binding socket failed: Error code 10048"
Hmm didn't worked for us... I did now everything logical but "Player was dropped from the game"... ![Sad :(](./images/smilies/icon_e_sad.gif)
![Sad :(](./images/smilies/icon_e_sad.gif)
Re: "Binding socket failed: Error code 10048"
Both of the problems described in this version (error 10048 and dropouts because of mixed local/public IP addresses) have now better error messages, so I'm moving this to resolved.