[BDS-17887] LAN suddenly stopped working after 1.19.50 update Created: 01/Dec/22  Updated: 14/May/24  Resolved: 14/May/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.19.50
Fix Version/s: None

Type: Bug
Reporter: vkuspa Assignee: Unassigned
Resolution: Incomplete Votes: 3
Labels: None
Environment:

Server: Dell PowerEdge R710
Windows Server 2019
2 x 2.26Ghz E5520 Quad Core
288 GBs RAM
Minecraft data on it's own 500 GB SSD
Single integrated 1GB/s NIC
(No log files were generated although the server window said they were)


Confirmation Status: Unconfirmed

 Description   

Updated my personal BDS server for LAN use to 1.19.50 from 1.19.41.01.

BDS 1.19.41.01 was working fine over LAN - no issues.
BDS 1.19.50 cannot find the server, stuck on "Locating...".

I tried alternate methods of updating (restarting the server and PCs between each attempt):

  • Drag-and-drop new files into existing server folder, overwriting the previous 1.19.41.01 files and copying back server.properties and world data.
  • Create new folder with 1.19.50 update files, overwriting new server.properties and world data with previous 1.19.41.01 versions
  • Create new folder with 1.19.50 files, keeping all new files and running with no alterations

All these yielded the same "Locating..." result in the game.

I restarted a backup 1.19.41.01 server - and Minecraft was able to find the server again.

I am unsure if this helps - I started a Java server on the server with the 1.19.2 version - same issue: Minecraft cannot find the server.

All PCs can ping the server and connect to all other services as no networking or other options changed on the hardware - only updating the BDS software to 1.19.50.

Various "bug fixes" posted here and around the internet have not changed the situation and any changes I have made trying to fix this have been reverted back to how they were during 1.19.41.01.



 Comments   
Comment by [MCQA] Kinga Izdebska [ 14/May/24 ]

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Comment by Maciej Piornik [ 30/Aug/23 ]

Hi

Does this issue still occur after updating to 1.20.15?

This ticket will automatically reopen when you reply.

Comment by javafreak [ 04/Jul/23 ]

After installing the 2023-06 Cumulative Update Preview for Windows 11 Version 22H2 for x64-based Systems (KB5027303) Windows update, I'm back to having a viable workaround again. This is what did and didn't work for me:

Running bedrock server on default ports, LAN visibility enabled:
  - Bedrock server shows up in the LAN Games section of the Friends list of the Minecraft client running on the same PC. Connecting to the server works as expected.
  - Manually adding an "Additional Server" on the Servers tab of the Windows Minecraft client does not work. It just gets stuck on "Locating server". I tried using both the PC's IP address and loopback (127.0.0.1) with port 19132, but it couldn't find it.
  - Server does NOT show up in the Friends list on the PS5.

Running bedrock server on default ports, LAN visibility disabled:
  - Exactly the same behavior as above. i.e. same behavior regardless of whether LAN visibility is enabled or disabled.
  
Running bedrock server on 19232/19233 ports, LAN visibility disabled. Also running Phantom on 19132:
  - Bedrock server no longer shows up in the LAN Games section of the Friends list of the Minecraft client running on the same PC.
  - Manually adding an "Additional Server", on the servers tab of the Windows Minecraft client, using port 19132 (phantom) does NOT work. Stuck on "Locating server".
  - One interesting thing here is that although neither the LAN game or Additional Server using 19132 works, Phantom is reporting that it is getting pinged by the Minecraft client.
  - Manually adding an "Additional Server", on the servers tab of the Windows Minecraft client, using port 19232 (bedrock server) DOES work. Connecting to the server works as expected. This is surprising given that using the Additional Server when bedrock server was running on 19132 did NOT work.
  - Server DOES show up in the Friends list on the PS5. Connecting to the server works as expected.

Since I'm back to a viable workaround, I don't need to downgrade back to Windows 10 after all.

Comment by javafreak [ 04/Jul/23 ]

I just upgraded my system to Windows 11 and unfortunately the situation is worse as I can no longer connect the Windows Minecraft client to the bedrock server at all, whether running phantom or not.

The PS5 also still can't find the bedrock server unless phantom is running.

So now I need to downgrade Windows back to 10 where at least I have a workable solution.

 

Comment by javafreak [ 04/Jul/23 ]

I just installed the bedrock 1.20.1.02 dedicated server for Windows and the issue still exists. This is what I found:

After starting up the bedrock server, it now shows up in Friends list on the Windows client (running on the same machine). Previously it didn't, so I had the dedicated server added as an Additional Server on the Windows client. But unfortunately it doesn't show up on the PS5 Friends list.

But the workaround still works:

I changed the server ports to 19232/19233 and disabled LAN visibility in the server.properties file. (I have to disable LAN visibility to avoid a port conflict with Phantom). Then when I run Phantom as before (on port 19132), it now shows up in the Friends list on the PS5. Of course, since I disabled LAN visibility, it doesn't show up in the Friends list on the Windows client now, but I can still connect, as before, using the Additional Server configuration configured to port 19232.

Comment by Maciej Piornik [ 03/Jul/23 ]

Hi

Does this issue still occur after updating to 1.20,1?

This ticket will automatically reopen when you reply.

Comment by javafreak [ 10/Feb/23 ]

I just upgraded to 1.19.61.01 and the problem still exists, but the workaround still works.

Comment by javafreak [ 28/Jan/23 ]

I had exactly the same issue when I upgraded from 1.19.40.02 to 1.19.51.01 on a Windows 10 PC. After the upgrade, the server no longer showed up in the friends list on the PS5. It appeared again after downgrading, but couldn't connect due to outdated server. I even tried the 1.19.60.27 preview version, but that also did not show up on the PS5.

However, I just found a workaround:

I set enable-lan-visibility to false in the server.properties and set server-port and server-portv6 to 19232 and 19233 respectively. I then ran phantom (https://github.com/jhead/phantom) like this in a command window:

phantom-windows.exe -server localhost:19232

As soon as I ran phantom, the server appeared in the friends list on the PS5 and I was able to connect to the server. The fact that this works suggests to me that there's a bug in the bedrock server related to the new enable-lan-visibility property.

 

Comment by Wisteso [ 25/Jan/23 ]

This issue is still occurring on 1.19.51 for me, which appears to be the latest right now.

Comment by Maciej Piornik [ 25/Jan/23 ]

Hi

Have you tried redownloading newest version and just setting up new server to verify if issue still occurs?

This ticket will automatically reopen when you reply.

Comment by Wisteso [ 22/Jan/23 ]

I am also having this issue.  Running 1.19.51 on Windows 10 update 22H2 using a typical ASUS gaming laptop.  Network is WiFi.

The LAN connectivity for the bedrock server is extremely intermittent.  Some days it works, and some days it does not.  I can see no pattern other than luck of the day.  Restarting the server process does not help.  I will be unable to connect from any clients (iOS, iPadOS, Windows 10, etc).  I am not even able to connect using 127.0.0.1 loopback.

I am not changing my configuration at all between days when it works, and days when it does not work.  I dont have any other issues with other services running on the server laptop (RDP works fine, for example).

 

Generated at Sat Jan 11 08:19:45 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.