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

RyuStaar

RyuStaar
Do you have an IPv6 address? you could try enabling that, as it assigns a unique id to each pc and doesn't fudge around with NAT

Edit: I had to edit .ini settings to get it to work, found a post on reddit
 

Sophokles Logimo

Sophokles Logimo
So, we ran another test, using a secondary account of mine, which is also an Epic account. Took a while, because I had to do the tutorial first etc., but once I left the PF district, we winged up, I could see her and she could see me, no problem. But then I logged off and on again, and now we had the same phenomenon.

So at least we now know it is NOT an issue with Epic accounts either.
 

Sophokles Logimo

Sophokles Logimo
After further investigation, using both machines on a cellphone connection and with the epic accounts (we lost motivation to try this again with the Frontier account on my side), the problem did NOT seem to exist any more, even though the separate instances happened for one time when we logged out and back in - going to some other place, however, fixed it reliably (2 of 2 times).

Maybe I'll make more tests in the future, but right now... well, it's tedious and the wrong type of mysterious. I hope the ticket offers any insights.
 

LKx

L
Since it's working with phones, maybe there something with your router configuration which forbid machines behind it to host a session. However did you tell that sometimes it works, or it never worked?
 

Sophokles Logimo

Sophokles Logimo
To be more precise, whe other players are in the wing, we can see them both, but not necessarily each other, or sometimes just one of us can see the other.
 

CMDR X

CMDR X
Try the following. It helps me fix windows networking weirdness most of the time.
(Win10 instructions. Works on Win7 too just different clickies)

On both computers:

1. In the search box on the taskbar, type Command prompt, press and hold (or right-click) Command prompt, and then select Run as administrator > Yes.

2. At the command prompt, run the following commands in the listed order:
  • Type netsh winsock reset and press Enter.
  • Type netsh int ip reset and press Enter.
  • Type ipconfig /release and press Enter.
  • Type ipconfig /renew and press Enter.
  • Type ipconfig /flushdns and press Enter.

3. In the search box on the taskbar, type and select Control Panel > Network and Sharing Center > Change adapter settings > Right Click adapter > Properties > Uncheck TCP/IPv6 > Click OK

4. Restart computers and try hooking up in Elite.

5. Let us know if it helps or not.
 

CMDR X

CMDR X
Sophokles Logimo said:
Predictably, this had no effect.
Click to expand...

Sorry to hear. I am assuming you are playing in Open. Have you tried a Private Group? I'm asking because my family plays together often in PG, on the same LAN, and apart from the occasional having to re-log to see each other, it all plays nice.

Only thing I can think of, is that the game tries a bit harder to same-instance members af a group than it does players in Open.
 
Last edited:

Sophokles Logimo

Sophokles Logimo
So, I finally got a reply to my support ticket.

"We think it's more likely to be an CMDR / account issue rather than a problem with your connection - if you were seeing connection issues, we'd expect you to see them in normal gameplay as well. it's possible that your account has some unrecoverable data that is causing the problem - a ship or module that our servers can't correctly read."

So, following this, we deleted, just as a test, all stored modules on both sides.

And since then, we have made several tests, and both instancing and multicrew now worked! (This is of course preliminary, as we've had positive results in the past as well, but this time we checked three different cases, so it should hold up better.)

I find this highly weird. Having some modules or ships can produce problems with instancing and multicrew?

Huh.
 
Last edited:

Sophokles Logimo

Sophokles Logimo
I had to add the below ticket to a previously seemingly fixed issue:

I am sorry to inform you that with the latest patch, the problem is back. We saw it with instancing her ship and mine into the same instance, which did not work, as seen before.
However, there have also been significant other changes to our accounts, though they did not seem to produce any problems before the latest patch: I bought a fleet carrier, we left our old squadron and founded our own, my wife got an Anaconda.

Is it possible that the reoccurence of the problem is related to the latest patch?
Click to expand...
 

Caydran

Caydran
Requiem Mortis said:
For others that may not be aware.

With regards to setting up Port Forwarding and using a different port for each client, see....

customersupport.frontier.co.uk

How do I set up port forwarding?

Port forwarding is commonly used to resolve problems encountered when connecting to the Frontier Servers, or to other players. It is especially important to enable port forwarding if UPnP is disabl...
customersupport.frontier.co.uk customersupport.frontier.co.uk

Quote
"You will need to forward a UDP port. We usually suggest port 5100 but you can use 5101, 5102, 5111, or 5200, using the in-game options.

Tell Elite Dangerous which ports to use:
1) Head to the main menu in-game. If you are currently logged in, please return to the main menu by selecting Save and Exit from the Escape menu.
2) Open Options.
3) Go to Network.
4) Set Port Forwarding to On.
5) Set Mapped Port Number to the number you chose on your router in Step 1.

Elite Dangerous will now use port forwarding instead of UPnP."
Click to expand...

While all of the above is correct, this WILL NOT WORK unless you have "Port Forwarding" set up in your "Router/Modem" as well. This will be different for each router or modem so instructions are impossible, but you will need to "Turn Off - UPnP" in your modem or router and "Turn On" a "Port Forward" using the same port set in Elite's networking.

Your port forward in your router/modem should look like this.

Your Conputer's IP Address where Elite is installed.
192.168.1.5 with a Port to Forward, i.e. 5100

So, it will come out as "192.168.1.5:5100".

In Elite's network settings, which should show the IP address of your machine where Elite is installed as well as the port to be forwarded, which will be read from your modem/router's "Port Forward".

It's counterintuitive, but set up a "port forward" in your router/modem FIRST, and then go to Elite's Network Settings and you should see the IP Address of your computer where Elite is installed and the Port to be forwarded in Elite's Network Settings.

In conclusion, just setting up a port to be forwarded in Elite's network settings is only half of what needs to be done to get this to work properly.

Oh, Seven....
 
You must log in or register to reply here.
Back
Top Bottom