solved Multiplayer missions run in single player; no server created -- Failed to bind TCP socket: 10049

[Nealius]

For better performance with resource-intensive missions, I run a second instance of DCS (not dedicated server) as a server. This has been working normally for years.

 

As of the 2.7.5.10869 update, creating a new server launches the mission as if in single player through the Mission tab, and no server is created.

 

I am logged in, online mode, the selected missions are multiplayer missions with client slots. They are the same missions I've been running prior to this update.

 

Creating a server from my first instance of DCS (client) works normally. 

 

 

Log attached. Interesting error line:

Quote

DCS: Error running erver: [string "erver"]:1: '=' expected near '<eof>'

 

This does not appear when launching a server from my primary instance of DCS.

dcs.log

Edited August 13, 2021 by Nealius

[Nealius]

New log after troublshooting. Still doesn't work. This line in the log might be the culprit:

 

ERROR   NET: Failed to bind TCP socket: 10049

 

I double-checked my static IP. Double checked my router's port forwarding. Doublechecked Windows Defender port allowances. Everything is good on my end. Still won't host a server.

dcs.log

[Nealius]

RESOLVED

 

I compared serverSettings.lua files between the instance that worked and the one that didn't.

 

Correct serverSettings.lua file entry: 

["bind_address"] = "",

 

Incorrect serverSettings.lua file entry:

["bind_address"] = "113.xxx.xxx",

 

I have always had an IP address assigned to the "bind_address" line and it has never been a problem. Apparently that has been changed and wasn't in the update changelogs.