Paul Turner
More than one avatar was detected! There might be multiple accounts sharing this same name.
Assigned
No issues.
Reported
Comments
Problem is with nVidia drivers, reinstalled driver 376.33 from December and Minecraft worked. Latest nVidia drive - 378.49 causes Minecraft to not work.
I have the same/similar issue. I've setup a Windows 10 Bedrock server (1.16.02) that works on a whitelist basis which local (LAN) users are able to connect to but remote (WAN) users are unable to join (their gamertag and xuid have been populated within whitelist.json). The server log shows the remote user's gamertag as "connected" and then automatically "disconnects" them about 25s later, but provides no further detail. Within the game their player appears briefly at the spawning point and the remote user sees the messages "Locating Server", "Unable to connect to World". My WAN address is static and my router is set to forward TCP/UDP to port 19132 on the Bedrock server. Correct operation of the port forwarding has been confirmed with a port checker.
This behaviour is the same for multiple remote users, though one is able to successfully connect to the server which demonstrates there is not a fundamental issue with my router or firewall settings. Could the issue be associated with Xbox Live user authentication or the remote user's Xbox One/Windows 10 Online Safety Settings? If so, what are the correct settings to allow server access?
I've reviewed the "potential workaround" posted to this issue but it doesn't really address what appears to be a more fundamental issue with WAN user access to the Bedrock server.