Problem to get into multicrew or same instance while playing on the same LAN

[Sophokles Logimo]

My wife and myself both like to play Elite Dangerous, but unfortunately, the game will usually not allow us to get into the same instance when flying separate ships, as well as not let us multicrew (in the latter case, this results in connection error Black Adder).

We have tried to set up port forwarding, but had the same problem afterwards.

I would have guessed that being on the same local network makes thing easier for the game to have people be in the same instance, not harder. Is there a solution to this?

 

[Bottom Hat]

You need to form a cunning plan m'lord.

 

[Vedmo]

Does she have you blocked?

 

[Agony_Aunt]

It is possible to connect. I've done it myself from a single machine.

Is one of them an Epic account? I had problems doing multicrew with an Epic and a non-Epic account. Had to do things in a specific order (private group, open up for multicrew, search for multicrew) for it to work. I had no problems with winging though.

 

[Sophokles Logimo]

[...]
Is one of them an Epic account? I had problems doing multicrew with an Epic and a non-Epic account. Had to do things in a specific order (private group, open up for multicrew, search for multicrew) for it to work. I had no problems with winging though.

Yes, her account is an Epic account, but how would that influence the issue?

And we are in the same wing, no problem, we can even see each other's wing beacons... just not our ships in an instance. Our blips on the radar look like NPC ships (only in the wing color), and if we select each other, all we see is a spiral thing, looking a bit like a FSD wake, not the actual ships. We cannot shoot the same enemies, etc., though we do seem to see similar ships with the same NPC names.

Now, if there is a third person in the wing, that sometimes works, but we haven't been able to experiment whether this is a reliable solution yet - and sometimes nobody but us is available.

We'll try the private group approach for multicrew, thanks for the hint. Though I'd prefer to play in open with the rest of our squadron.

 

[Bottom Hat]

There was a thread about 24hrs ago with a solution to the epic issue. Written by llandranel I think. I don't know if it is your solution, but worth checking out.

 

[Sophokles Logimo]

There does not seem to be such a thread.

 

[Bottom Hat]

There does not seem to be such a thread.

I'll have a look. Brb

 

[Bottom Hat]

Here you go. Was on page 2. Don't know if it will help though, but worth looking at.

Update for Epic users receiving "Skartlet Krait" a lot.

Ok, so this is from an official email I got in response to a ticket I put in, just thought you might like to know, they're on it, but don't know when it'll be solved; Hey there (Llandrenel), Thanks for getting in touch with us and apologies for the delayed response. So this is actually an...

forums.frontier.co.uk

 

[Sophokles Logimo]

That's an entirely different problem. The epic account in our case here does not have issues connecting to the servers at all.

To reiterate: The problem described here only arises when doing mutlicrew or combat instances with a player on the same LAN. When trying multicrew, from Frontier account to Epic account ship, it times out with the message "Black Adder". We haven't tested the other way round yet. However, with a third person from a different network in the group, instancing at least has been shown to work at least sometimes.

 

[Bottom Hat]

Well apologies for trying to help. I did say it might have nothing to do with it, but there you go.

 

[Enkelas]

hi,
my wife and i had this problem sometimes. we both were at the same station (we have a private group) and when trying to give wing the invitation never arrived. then one of us had to dc and log in again or went out of the station and enter suprecruise and come back.
this worked most of the time. when not then we plotted the same route and jumped to the same system and then most of the time both were in the same instance and could see us.

this would last most of the time but it is true that at times even jumping to the same system and being in wing didnt work.

it seems that elite servers dont like players playing with the same ip and being together

 

[CMDR Harada]

I wonder if this has to do with your machines local IP ( used for your local LAN ), versus it's NAT'd one ( that the ED servers would see ) ? IE : You and your wifes machine both use the same NAT/External IP address on your router, but different internal IP's.

Attempting to connect to your NAT'd IP from inside your network would cause all sorts of issues.

 

[Chrystoph]

If you are using one of the software firewalls such as the built in Windows FW, I would try deleting the rules for Elite and let the FW refind it.

That will force it to write new rules; not a gauranteed fix, but it has solved numerous problems in the past.

 

[Requiem Mortis]

If one of your machines has a wireless connection then you might consider using a mobile phone as wireless hotspot and get a completely separate connection. ED has a very light data usage and should only be a few Mb/hr

 

[Agony_Aunt]

Yes, her account is an Epic account, but how would that influence the issue?

From a technical point of view i have no idea. Just that it has been an issue.

 

[Sophokles Logimo]

If you are using one of the software firewalls such as the built in Windows FW, I would try deleting the rules for Elite and let the FW refind it.

That will force it to write new rules; not a gauranteed fix, but it has solved numerous problems in the past.

That's worth a shot, thanks for the idea! I'll also try to monitor the connections with Wireshark tonight to see if that offers any new information.

 

[Sophokles Logimo]

I wonder if this has to do with your machines local IP ( used for your local LAN ), versus it's NAT'd one ( that the ED servers would see ) ? IE : You and your wifes machine both use the same NAT/External IP address on your router, but different internal IP's.

Attempting to connect to your NAT'd IP from inside your network would cause all sorts of issues.

That might be the case, yes, but if that is true, then it's a design error in the game client, and needs to be addressed by Frontier.

 

[Morbad]

We have tried to set up port forwarding, but had the same problem afterwards.

This is rather vague.

Have you made sure that both clients have their ports forwarded through every firewall between them and your ISP, and set each client to use different ports?

 

[Sophokles Logimo]

This is rather vague.

Have you made sure that both clients have their ports forwarded through every firewall between them and your ISP, and set each client to use different ports?

Yes.