Unable to join friend's coop server since update 4.08

[chris_uk_83]

Has anyone else had an issue with coop servers since update 4.08? I was previously able to play coop with my brother, with me hosting, quite reliably, and tonight he gets the "unable to join server" message every time he tries to join.

 

He sees it in the list, and it's displaying correctly, but gets an error message every time he joins.

 

I checked the port forwarding, I had to set it up in the first place, and that's still working fine.

[Nocke]

no issues with coop here

[DD_FT-]

Is the error just simply "unable to join server", or does it show anything else, like an error number?

 

He may want to try and delete the contents of the Data/Multiplayer/Cooperative folder... then try and connect again.

 

 

[[KG]Destaex]

Trying to do this as a noob with my own mission now. The other player is freezing (his cursor does not spin) when he tries to connect. 

It would be a shame if my first attempt at making a mission was stopped because I happened to create one as a bug was introduced

[-DED-Rapidus]

Where is the server created? on the computer behind the router? if so then we need to do port forwarding to begin with.

[JediMaster]

As seen here, I first mentioned this issue on May 10th, although the problem appeared earlier.

 

The symptom is always client freezes with spinning circle stuck mid-spin needing task manager kill of Il-2. Host can fly no issues on empty server.

Any mission, including included coop template one.

[LachenKrieg]

On 7/24/2020 at 2:42 PM, JediMaster said:

The symptom is always client freezes with spinning circle stuck mid-spin needing task manager kill of Il-2. Host can fly no issues on empty server.

Any mission, including included coop template one.

I am having this same issue. D-Server starts and registers with no issues. I can join as a player using my personal account and play the missions. When other players try to join, their client software crashes. Is there a solution to this yet?

Just to pass on information. I went into Windows 10 and allowed IL-2 in the firewall. If you are hosting a mission coop/dogfight and other players are not able to join your server, check your firewall setting for IL-2. This fixed the issue for me.

 

Thanks @-DED-Rapidus

Edited August 5, 2020 by LachenKrieg
Problem solved

[JediMaster]

Oh, you are using D Server.

 

I'm just going into il-2 and clicking MP - coop - continue - create server - then set it all up.

[-DED-Rapidus]

6 hours ago, JediMaster said:

I'm just going into il-2 and clicking MP - coop - continue - create server - then set it all up.

There is no difference, ports 28000 and 28100 are used for TCP and UDP packets in both cases.

[JediMaster]

No difference from the firewall ports side, no.

 

There must be a difference from the code side, though. One is il-2.exe hosting, the other is dserver.exe hosting.

[JediMaster]

Ok, so Charlo and I did some testing, both of us trying to host using coop example mission included with BoX.

 

After clicking connect, after 3.5-4 mins of a frozen screen we will get error #10019 unable to connect to game server. The host can get in and fly easily, but the client will never get to the lobby to pick a plane.

 

Really scraping the barrel bottom for ideas here...

[-DED-Rapidus]

@JediMaster, please give your SDS file or take a screenshot from the lobby When you launch coop server. I need to see the server startup parameters.

[JediMaster]

Not sure where the SDS file is, so here's the screenshots. Unchanged from when Charlo and I tried last night.

 

Originally I had restrict injectors checked, but he has some mod or other that caused him to see a rejection when he tried to connect - at once I might add. So I unchecked it and he tried again, and then it took around 4 mins before he got the #10019 error. I got the same when I tried to connect to his.

[JediMaster]

Anyone able to replicate this?

[chris_uk_83]

That's the same error we get, exactly the same behaviour.

 

The thing is, it used to work fine, then, one day, after a game update, it just stopped working.

 

I'm hoping for more ideas from those in the know, I'm stuck right now.

[JediMaster]

There are 2 possibilities. It's an Il-2 update that did it, it's a Windows 10 update that did it.

 

Either way, there should be some way to log what is going on.

[JediMaster]

Did another test, this time with DF instead of coop. Otherwise, same situation. NOT using a dserver, just going into the game and creating my own after choosing MP/DF.

Same results. Clients freeze. Game mode is irrelevant.

 

Now something else I've wondered. Those who it works for vs those who it does not...do you have a routable IP on your PC, or does your router/cable modem use NAT?

In the past, my IP started with 107. whatever, but for the last several months at least it's now a 192.168. If I do a "whatismyip.com" lookup, I see my external one is still 107, but the ISP has now activated NAT and my home gets a single IP. I remember 20 years ago we got 5, I think.

 

So if I go to settings - MP, I see a 192.168 address there. I can fill that into the Use IP field and it makes no difference, but I'm wondering if for the people where it still works--do you have a 192 IP or a routable one from your ISP? Those for whom it does not work, of course the same question.

 

I'm going to try diving into the actual firewall rules (as opposed to the simple "allow" checkboxes) where I can specify ports and other aspects and see if I can get it to behave differently.

[JediMaster]

None of the firewall rule changes made a difference.

 

Next up - disabling it for a limited period to see if THAT works.

[Tuesday]

On 9/8/2020 at 9:27 PM, JediMaster said:

None of the firewall rule changes made a difference.

 

Next up - disabling it for a limited period to see if THAT works.

 

I am having the same problem as you - disabling the firewall entirely did not work either, in my case. 

 

To date I have tried everything that you have, too.  Still no luck.

[DD_FT-]

On 9/5/2020 at 1:08 AM, JediMaster said:

(...)

 

Now something else I've wondered. Those who it works for vs those who it does not...do you have a routable IP on your PC, or does your router/cable modem use NAT?

In the past, my IP started with 107. whatever, but for the last several months at least it's now a 192.168. If I do a "whatismyip.com" lookup, I see my external one is still 107, but the ISP has now activated NAT and my home gets a single IP. I remember 20 years ago we got 5, I think.

 

So if I go to settings - MP, I see a 192.168 address there. I can fill that into the Use IP field and it makes no difference, but I'm wondering if for the people where it still works--do you have a 192 IP or a routable one from your ISP? Those for whom it does not work, of course the same question.

 

(...)

Setting up a firewall rule would also mean adding a port forwarding rule. (Besides allowing the UDP/TCP traffic in through a specific port)

 

Meaning: All Internet based traffic that comes towards your IP (107.x.x.x) via UDP/TCP on the specified ports, should be forwarded to the server PC in your local network - that 192.168.x.x address. (Or could be a PC name, depending on what your router is capable of) 

Downside to using the IP Address is that your local 192.168.x.x assigned to the server PC might change - preferably you should set it to be fixed/reserved in the router.

 

Whether it's relevant to your problem, I cannot tell - just wanted to try and explain that Internet address and router/traffic stuff ....

 

Good Luck!

[JediMaster]

I have no router. My PC is plugged directly into my cable modem. However, my ISP has NAT turned on. I cannot touch it. I can't tell how it might be set either.

I used to have a public IP for my PC, but it no longer does. So I can't create any port forwarding rules.

 

I also disabled my Windows firewall and it made no difference.

[JediMaster]

Ok...I went searching the net and found out how to get into my cable modem. So I logged in and found I had port fwding rules in there from YEARS ago that I had forgotten about.

 

I had almost no memory of doing them, but I know they were me because one had the name "DCS" and the other "ROF".

 

ROF uses the same ports as Il-2 (no coincidence there) but my PC's IP had changed over the years from 192.168.0.3 to .4 (or vice versa, I forget which).

 

So I altered the rules to use my PC's new IP and voila! my friend can now connect.

 

I know DCS didn't require those rules anymore, I've had people connect to me without issue in the last few months, but apparently Il2/ROF still does.