Dedicated Server 2.5.5 - Problem: Connection Timeout

[Kirin]

Greetings aces

 

I am trying to setup a dedicated server for my frineds. It's running on a seperate PC on the same network that I used to run a pseudo dedicated DCS server before without problems.

 

I deinstalled regular DCS and installed the dedicated server. I can launch it. And I can connect to it. After a few minutes I will always receive a connection timeout. Same with my friends trying to connect to it. I tried port forwarding for port 10308 which did not help.

 

Any suggestion how to troubleshoot further?

 

 

Kirin out

[Kirin]

Small update. I am able to host without problems from my main PC in regular DCS. If that helps.

[Kirin]

This is what happens - about 2:35min in:

 

16:49:29.703 INFO NET player 2 occupied unit 1

16:49:29.703 DEBUG NET ServerInfo json size is: raw = 227, gzip = 168. 1 chunks.

16:51:53.763 INFO SCRIPTING event:type=relinquished,initiatorPilotName=Qilin,target=Pilot #001,t=29872.047,targetMissionID=1,

16:51:53.763 INFO NET remove: client 2

16:51:53.763 DEBUG NET ServerInfo json size is: raw = 219, gzip = 161. 1 chunks.

 

Any hints?

[ElementLT]

have you tried disabling the firewall all together? (On the host PC?) not sure if this link would be any help but this was a good read.

 

[Kirin]

have you tried disabling the firewall all together? (On the host PC?) not sure if this link would be any help but this was a good read.

 

 

Thanks for the input. Interesting read. What makes me wonder is why I can host a game running on the gaming PC without problems. Only the dedicated server seems to act up. The server is visibly and just disconnects clients at random. Usually after 2min in a plane, longer if you stay just in the role selection.

[dFlow]

I have the same situation.

Currently I am running a DCS dedicated server on a machine in my network (VM). On another machine I am playing.

Now it happened to me that I got kicked out of my own server on a game session, where others remained on it - I got a connection timeout! on my own server in my own network!

 

Strange enough a couple of mins later one of my guests had a timeout himself, where the rest of us remained on the server without any issues ...

 

I don't believe that this is a firewall issue, as the game was able to connect for everyone and the server is visible in the list.

 

Currently I am on the latest version of OB (17.6.2020)

[docWilly]

I have the same experience as client - especially with the latest updates (not the one from June 17th which is not installed yet on my PC).

 

Connection timeout around 2-5 min beeing on the MP server - which was very rare before. It´s not a matter of "ping" nor of my internet connection (100MB down/40MB up). Still have no clue whats going on. Ports are open (to be sure), firewall is not blocking.

[bengo]

I have the same experience as client - especially with the latest updates (not the one from June 17th which is not installed yet on my PC).

 

Connection timeout around 2-5 min beeing on the MP server - which was very rare before. It´s not a matter of "ping" nor of my internet connection (100MB down/40MB up). Still have no clue whats going on. Ports are open (to be sure), firewall is not blocking.

 

Hi, were you able to fix this ?

I'm seeing the same thing here, so I was wondering if you found a solution.

[XCNuse]

Bump to an old thread; I changed to a new computer for my dediserver and the new computer keeps randomly kicking groups of people.

 

2022-05-04 01:58:59.527 INFO    Scripting: event:type=relinquished,initiatorPilotName=XCNuse,target=Devil-4,t=2715.801,targetMissionID=100,
2022-05-04 01:58:59.530 INFO    NET: remove: client[2]
2022-05-04 01:59:02.526 INFO    Scripting: event:type=relinquished,initiatorPilotName=RAM 1-4 | Glue,target=Devil-2,t=2718.801,targetMissionID=98,
2022-05-04 01:59:02.527 INFO    NET: remove: client[4]

 

out of 3 of us on tonight, 1 person survived, 2 of us were kicked.

My old computer never had this issue.

For what it's worth, it's the same network, both are static IPs on a external static IP so I can guarantee that is not the issue.

 

I realized this could have also occurred when I updated router as well, so found a different setting, NAT Acceleration (NAT Boost), have disabled that thinking it might have some effect... will attempt to update if I ever find anything further.

Edited May 4, 2022 by XCNuse