1.9.0.15 Not Listening on any port (Still broken on 1.11.2.1

Just tested on Server 2019, same result. 

Just tested on Server 2019, same result. 

Just tested on Server 2019, same result. 

Do you need any further information? 

Do you need any further information? 

Do you need any further information? 

I have a similar problem. I also tried to lower the version to 1.8.1.2, the problem persists. The problem is as on Windows 10, I also have a problem on Linux Mint. Moreover, if you run the server for Java Edition on any port, then everything works fine.

I have a similar problem. I also tried to lower the version to 1.8.1.2, the problem persists. The problem is as on Windows 10, I also have a problem on Linux Mint. Moreover, if you run the server for Java Edition on any port, then everything works fine.

I have a similar problem. I also tried to lower the version to 1.8.1.2, the problem persists. The problem is as on Windows 10, I also have a problem on Linux Mint. Moreover, if you run the server for Java Edition on any port, then everything works fine.

I'm also having this issue. All firewall and port forwarding taken care of, and no mention of the server listening on either port. Tried this on two Windows 10 machines and both had this same issue.

I'm also having this issue. All firewall and port forwarding taken care of, and no mention of the server listening on either port. Tried this on two Windows 10 machines and both had this same issue.

I'm also having this issue. All firewall and port forwarding taken care of, and no mention of the server listening on either port. Tried this on two Windows 10 machines and both had this same issue.

Same issue here. Sometimes, on my iPad only, the server will appear in the friends tab and let me connect to the server.

Same issue here. Sometimes, on my iPad only, the server will appear in the friends tab and let me connect to the server.

Same issue here. Sometimes, on my iPad only, the server will appear in the friends tab and let me connect to the server.

Same problem here, can't find anything to help

Same problem here, can't find anything to help

Same problem here, can't find anything to help

I also have the same problem...

I also have the same problem...

I also have the same problem...

Interestingly, people are able to connect to my server through cellular data, even though the ports that are forwarded correctly are shown to be closed. Anybody can connect though cellular data, but nobody is able to connect using wifi.

Interestingly, people are able to connect to my server through cellular data, even though the ports that are forwarded correctly are shown to be closed. Anybody can connect though cellular data, but nobody is able to connect using wifi.

Interestingly, people are able to connect to my server through cellular data, even though the ports that are forwarded correctly are shown to be closed. Anybody can connect though cellular data, but nobody is able to connect using wifi.

same one

same one

same one

using phantom seemed to allow my friend to connect to my server, admittedly not an ideal solution though.

using phantom seemed to allow my friend to connect to my server, admittedly not an ideal solution though.

using phantom seemed to allow my friend to connect to my server, admittedly not an ideal solution though.

Can you elaborate on what phantom is and how you used it? Googling "Minecraft Phantom" doesn't yield many useful results! 

Can you elaborate on what phantom is and how you used it? Googling "Minecraft Phantom" doesn't yield many useful results! 

Can you elaborate on what phantom is and how you used it? Googling "Minecraft Phantom" doesn't yield many useful results! 

Also just to add, the port forwarding works perfectly if I use the Java version.

Also just to add, the port forwarding works perfectly if I use the Java version.

Also just to add, the port forwarding works perfectly if I use the Java version.

This is what I see in TCP View, as you can see, the server is not listening to the ports like the other programs are and the Remote Address and Remote Port are just * and the state is blank. 

This is what I see in TCP View, as you can see, the server is not listening to the ports like the other programs are and the Remote Address and Remote Port are just * and the state is blank. 

This is what I see in TCP View, as you can see, the server is not listening to the ports like the other programs are and the Remote Address and Remote Port are just * and the state is blank. 

I also cleared the local address loopback before adding a new server, still the same. New computer, new network, new server, results always the same. I just don't understand what other people are doing that enables them to connect externally. (This works on local machine and lan)

I also cleared the local address loopback before adding a new server, still the same. New computer, new network, new server, results always the same. I just don't understand what other people are doing that enables them to connect externally. (This works on local machine and lan)

I also cleared the local address loopback before adding a new server, still the same. New computer, new network, new server, results always the same. I just don't understand what other people are doing that enables them to connect externally. (This works on local machine and lan)

Well strange turn of events, it's working now and here are a few things I have noticed:  it's now apparent that the server doesn't need to say "listening" on either TCP View or on the server itself.

When you check on canyouseeme.org if it is working it will change from "Connection timed out" to "Connection refused" when it's working. 

I hope this helps someone. 

Well strange turn of events, it's working now and here are a few things I have noticed:  it's now apparent that the server doesn't need to say "listening" on either TCP View or on the server itself.

When you check on canyouseeme.org if it is working it will change from "Connection timed out" to "Connection refused" when it's working. 

I hope this helps someone. 

Well strange turn of events, it's working now and here are a few things I have noticed:  it's now apparent that the server doesn't need to say "listening" on either TCP View or on the server itself.

When you check on canyouseeme.org if it is working it will change from "Connection timed out" to "Connection refused" when it's working. 

I hope this helps someone. 

Tim, how did you solve your problem? I haven't figured out a solution and would love to hear what you did to fix it.

I am having a very similar issue with 1.11.4.

I have confirmed that my ISP (this is being done on a home network, and I suspect that this is the problem) is not blocking any of the required ports, and that port forwarding is working on my router for all other applications. When the bedrock dedicated server attempts to bind to the port, there are no errors shown in console. Players on the same network can connect, others cannot. The port also shows as closed even when the server is running, so it is not binding correctly. I tried using Ubuntu Server and Windows Desktop versions on two separate computers connected to the same network, I had the same results with both. To tickle my fancy, I also tried running PocketMine and Nukkit (two 3rd party server applications, to be clear, I am not requesting support for these two, just done for testing), same thing: local players can connect, external ones cannot, port shows as closed.

I'm extremely dumbfounded right now. It doesn't appear to be an issue specific to Mojang's official server software (tested on 3 different server softwares). It's also not an issue with one of my computers, because I tested on two different operating systems with the same results. My router configuration is correct, because the ports are forwarded correctly when using other software.

I think this has something to do with being on a home network. The results were the same between every single trial I ran, and the only constant variable between each trial was the network the computer was connected to. Even though my ISP is not blocking these ports, I believe that this is a limitation with home networks is causing problems with the MCBE server-client protocol.

Tim, how did you solve your problem? I haven't figured out a solution and would love to hear what you did to fix it.

I am having a very similar issue with 1.11.4.

I have confirmed that my ISP (this is being done on a home network, and I suspect that this is the problem) is not blocking any of the required ports, and that port forwarding is working on my router for all other applications. When the bedrock dedicated server attempts to bind to the port, there are no errors shown in console. Players on the same network can connect, others cannot. The port also shows as closed even when the server is running, so it is not binding correctly. I tried using Ubuntu Server and Windows Desktop versions on two separate computers connected to the same network, I had the same results with both. To tickle my fancy, I also tried running PocketMine and Nukkit (two 3rd party server applications, to be clear, I am not requesting support for these two, just done for testing), same thing: local players can connect, external ones cannot, port shows as closed.

I'm extremely dumbfounded right now. It doesn't appear to be an issue specific to Mojang's official server software (tested on 3 different server softwares). It's also not an issue with one of my computers, because I tested on two different operating systems with the same results. My router configuration is correct, because the ports are forwarded correctly when using other software.

I think this has something to do with being on a home network. The results were the same between every single trial I ran, and the only constant variable between each trial was the network the computer was connected to. Even though my ISP is not blocking these ports, I believe that this is a limitation with home networks is causing problems with the MCBE server-client protocol.

Tim, how did you solve your problem? I haven't figured out a solution and would love to hear what you did to fix it.

I am having a very similar issue with 1.11.4.

I have confirmed that my ISP (this is being done on a home network, and I suspect that this is the problem) is not blocking any of the required ports, and that port forwarding is working on my router for all other applications. When the bedrock dedicated server attempts to bind to the port, there are no errors shown in console. Players on the same network can connect, others cannot. The port also shows as closed even when the server is running, so it is not binding correctly. I tried using Ubuntu Server and Windows Desktop versions on two separate computers connected to the same network, I had the same results with both. To tickle my fancy, I also tried running PocketMine and Nukkit (two 3rd party server applications, to be clear, I am not requesting support for these two, just done for testing), same thing: local players can connect, external ones cannot, port shows as closed.

I'm extremely dumbfounded right now. It doesn't appear to be an issue specific to Mojang's official server software (tested on 3 different server softwares). It's also not an issue with one of my computers, because I tested on two different operating systems with the same results. My router configuration is correct, because the ports are forwarded correctly when using other software.

I think this has something to do with being on a home network. The results were the same between every single trial I ran, and the only constant variable between each trial was the network the computer was connected to. Even though my ISP is not blocking these ports, I believe that this is a limitation with home networks is causing problems with the MCBE server-client protocol.

Hi guys. I found the problem of the server why is not listening it is very simple. 

The cause of the problem is if you play minecraft on phone/tablet/ipad/xbox/pc on the same network . bedrock server will not open because the same port

Look first close all the worlds on minecraft if you playing 

Second check the port if it is on your computer ip (the pc you use for the server) if it at the same ip

After that download server.properties (https://www.mediafire.com/file/u1j1hj15n7sec47/server.properties/file ) from this link and put it in server file and put your pc ip in the file.

start the server and do not join from the server list. join from friend list . and if your port are putted on your computer ip (that you use for the server ) you can share your public ip to your friend to join the server. And i hope i helped you 

By the way it doesn't Have to say it is listening

Hi guys. I found the problem of the server why is not listening it is very simple. 

The cause of the problem is if you play minecraft on phone/tablet/ipad/xbox/pc on the same network . bedrock server will not open because the same port

Look first close all the worlds on minecraft if you playing 

Second check the port if it is on your computer ip (the pc you use for the server) if it at the same ip

After that download server.properties (https://www.mediafire.com/file/u1j1hj15n7sec47/server.properties/file ) from this link and put it in server file and put your pc ip in the file.

start the server and do not join from the server list. join from friend list . and if your port are putted on your computer ip (that you use for the server ) you can share your public ip to your friend to join the server. And i hope i helped you 

By the way it doesn't Have to say it is listening

Hi guys. I found the problem of the server why is not listening it is very simple. 

The cause of the problem is if you play minecraft on phone/tablet/ipad/xbox/pc on the same network . bedrock server will not open because the same port

Look first close all the worlds on minecraft if you playing 

Second check the port if it is on your computer ip (the pc you use for the server) if it at the same ip

After that download server.properties (https://www.mediafire.com/file/u1j1hj15n7sec47/server.properties/file ) from this link and put it in server file and put your pc ip in the file.

start the server and do not join from the server list. join from friend list . and if your port are putted on your computer ip (that you use for the server ) you can share your public ip to your friend to join the server. And i hope i helped you 

By the way it doesn't Have to say it is listening

UDP, which is used by Bedrock, isn't connection oriented, so you won't see any statuses in something like TCPView, or netstat, only that a socket is open.

That being said, something is making the connections not play well with NAT in the slightest, the UDP packets aren't triggering the port forwarding rules on my EdgeRouter X most of the time.

UDP, which is used by Bedrock, isn't connection oriented, so you won't see any statuses in something like TCPView, or netstat, only that a socket is open.

That being said, something is making the connections not play well with NAT in the slightest, the UDP packets aren't triggering the port forwarding rules on my EdgeRouter X most of the time.

UDP, which is used by Bedrock, isn't connection oriented, so you won't see any statuses in something like TCPView, or netstat, only that a socket is open.

That being said, something is making the connections not play well with NAT in the slightest, the UDP packets aren't triggering the port forwarding rules on my EdgeRouter X most of the time.

I am having this exact same issue,

I have a Spectrum RAC2V1K, configured all the port forwarding in my router correctly (TCP & UDP), and set a static IP for my desktop, and made sure there's permissions in the firewall for all of the ports I have tried. (I have tired many different port configurations as well as temporarily disabling the firewall)

The part that stumps me is that just a week ago everything was working perfectly, but then I had my internet upgraded due to some special that spectrum was offering, so they had to change the modem from an old ARIS to whatever they gave me, a Spectrum E31U2V1. The new modem and router seem to not be playing nice with the Bedrock server.

However I have a modded server running on the default minecraft port 25565 with the new router and modem, and I am able to connect to it just fine. And modded server ports also shows up as being open when I use canyouseeme.org. 

So my issue is only with the Bedrock server, from what I've read its because its not listening on its assigned ports 19132. When I use canyouseeme.org is says "network conecction timed out" as opposed to "connection refused" as Tim Turnill mentioned above

Any insight would be greatly appreciated, I've provided all the information I can think of

I am having this exact same issue,

I have a Spectrum RAC2V1K, configured all the port forwarding in my router correctly (TCP & UDP), and set a static IP for my desktop, and made sure there's permissions in the firewall for all of the ports I have tried. (I have tired many different port configurations as well as temporarily disabling the firewall)

The part that stumps me is that just a week ago everything was working perfectly, but then I had my internet upgraded due to some special that spectrum was offering, so they had to change the modem from an old ARIS to whatever they gave me, a Spectrum E31U2V1. The new modem and router seem to not be playing nice with the Bedrock server.

However I have a modded server running on the default minecraft port 25565 with the new router and modem, and I am able to connect to it just fine. And modded server ports also shows up as being open when I use canyouseeme.org. 

So my issue is only with the Bedrock server, from what I've read its because its not listening on its assigned ports 19132. When I use canyouseeme.org is says "network conecction timed out" as opposed to "connection refused" as Tim Turnill mentioned above

Any insight would be greatly appreciated, I've provided all the information I can think of

I am having this exact same issue,

I have a Spectrum RAC2V1K, configured all the port forwarding in my router correctly (TCP & UDP), and set a static IP for my desktop, and made sure there's permissions in the firewall for all of the ports I have tried. (I have tired many different port configurations as well as temporarily disabling the firewall)

The part that stumps me is that just a week ago everything was working perfectly, but then I had my internet upgraded due to some special that spectrum was offering, so they had to change the modem from an old ARIS to whatever they gave me, a Spectrum E31U2V1. The new modem and router seem to not be playing nice with the Bedrock server.

However I have a modded server running on the default minecraft port 25565 with the new router and modem, and I am able to connect to it just fine. And modded server ports also shows up as being open when I use canyouseeme.org. 

So my issue is only with the Bedrock server, from what I've read its because its not listening on its assigned ports 19132. When I use canyouseeme.org is says "network conecction timed out" as opposed to "connection refused" as Tim Turnill mentioned above

Any insight would be greatly appreciated, I've provided all the information I can think of

I hate to resurrect, but when I changed my port forwarding from tcp/udp to just udp my ubuntu server worked instantly. I knew it was my router causing similar issues not receiving any packets on the server.

Hope this helps someone.

I hate to resurrect, but when I changed my port forwarding from tcp/udp to just udp my ubuntu server worked instantly. I knew it was my router causing similar issues not receiving any packets on the server.

Hope this helps someone.

I hate to resurrect, but when I changed my port forwarding from tcp/udp to just udp my ubuntu server worked instantly. I knew it was my router causing similar issues not receiving any packets on the server.

Hope this helps someone.

Hi all,

Is this still an issue?

Unlike Java, Bedrock runs on 19132/UDP rather than TCP. I've not seen issues where broadcast doesn't work except in scenarios where the world has been loaded in single player or in a world file manipulation tool.

Please post if this is ongoing for you.

Ionic

Hi all,

Is this still an issue?

Unlike Java, Bedrock runs on 19132/UDP rather than TCP. I've not seen issues where broadcast doesn't work except in scenarios where the world has been loaded in single player or in a world file manipulation tool.

Please post if this is ongoing for you.

Ionic

Hi all,

Is this still an issue?

Unlike Java, Bedrock runs on 19132/UDP rather than TCP. I've not seen issues where broadcast doesn't work except in scenarios where the world has been loaded in single player or in a world file manipulation tool.

Please post if this is ongoing for you.

Ionic

Hi, I think this is the same issue I am having. I am able to connect to my bedrock server (running on a Win 10 desktop) from within my LAN.  But I cannot connect externally. I have checked, my port forwarding settings on my router countless times. I've tried changing ports as well. I have inbound rules for UDP and TCP in Windows Defender. 

I have tried Versions 1.14.32.1 and 1.14.1.4.

I have set up a different server (Plex) to see if that would work externally and that works fine.

I would really love to get this working for my kids and their friends during this Covid mess. Any help is much appreciated.

Thanks

Hi, I think this is the same issue I am having. I am able to connect to my bedrock server (running on a Win 10 desktop) from within my LAN.  But I cannot connect externally. I have checked, my port forwarding settings on my router countless times. I've tried changing ports as well. I have inbound rules for UDP and TCP in Windows Defender. 

I have tried Versions 1.14.32.1 and 1.14.1.4.

I have set up a different server (Plex) to see if that would work externally and that works fine.

I would really love to get this working for my kids and their friends during this Covid mess. Any help is much appreciated.

Thanks

Hi, I think this is the same issue I am having. I am able to connect to my bedrock server (running on a Win 10 desktop) from within my LAN.  But I cannot connect externally. I have checked, my port forwarding settings on my router countless times. I've tried changing ports as well. I have inbound rules for UDP and TCP in Windows Defender. 

I have tried Versions 1.14.32.1 and 1.14.1.4.

I have set up a different server (Plex) to see if that would work externally and that works fine.

I would really love to get this working for my kids and their friends during this Covid mess. Any help is much appreciated.

Thanks

@IonicEcko

It was an issue before. A friend did have a Realms world we were messing with. Not manipulated, just saved off. However when I stopped advertising over TCP and only UDP it worked. It could have been a different issue.

@Krys

Check your port forward settings on your router and your server. Are both protocols, TCP and UDP, opened up? If so, try removing the TCP hole/passthrough and only allow UDP>

@IonicEcko

It was an issue before. A friend did have a Realms world we were messing with. Not manipulated, just saved off. However when I stopped advertising over TCP and only UDP it worked. It could have been a different issue.

@Krys

Check your port forward settings on your router and your server. Are both protocols, TCP and UDP, opened up? If so, try removing the TCP hole/passthrough and only allow UDP>

@IonicEcko

It was an issue before. A friend did have a Realms world we were messing with. Not manipulated, just saved off. However when I stopped advertising over TCP and only UDP it worked. It could have been a different issue.

@Krys

Check your port forward settings on your router and your server. Are both protocols, TCP and UDP, opened up? If so, try removing the TCP hole/passthrough and only allow UDP>

Hi James, 

I solved it by forwarding both TCP and UDP on the router to the static IP of my computer.

Once done I had to completely disable the firewall on the computer. (Windows 10) 

No amount of forwarding or opening ports allows bedrock to work. This includes opening the ports completely to anything, or forwarding the ports to the server itself. I then thought it must be a bug with Firewall so I disabled it and installed Zone alarm. Exact same again. So I have to leave the server with no firewall to this day. 

As I said in the begining, multiple computers, multiple networks, all new installs of Bedrock server. 

I am seeing messages above saying that it's beneficial to keep TCP blocked, but that doen't make sense considering I have no firewall. 

Hi James, 

I solved it by forwarding both TCP and UDP on the router to the static IP of my computer.

Once done I had to completely disable the firewall on the computer. (Windows 10) 

No amount of forwarding or opening ports allows bedrock to work. This includes opening the ports completely to anything, or forwarding the ports to the server itself. I then thought it must be a bug with Firewall so I disabled it and installed Zone alarm. Exact same again. So I have to leave the server with no firewall to this day. 

As I said in the begining, multiple computers, multiple networks, all new installs of Bedrock server. 

I am seeing messages above saying that it's beneficial to keep TCP blocked, but that doen't make sense considering I have no firewall. 

Hi James, 

I solved it by forwarding both TCP and UDP on the router to the static IP of my computer.

Once done I had to completely disable the firewall on the computer. (Windows 10) 

No amount of forwarding or opening ports allows bedrock to work. This includes opening the ports completely to anything, or forwarding the ports to the server itself. I then thought it must be a bug with Firewall so I disabled it and installed Zone alarm. Exact same again. So I have to leave the server with no firewall to this day. 

As I said in the begining, multiple computers, multiple networks, all new installs of Bedrock server. 

I am seeing messages above saying that it's beneficial to keep TCP blocked, but that doen't make sense considering I have no firewall. 

Ionic, it's still very much an issue. I downloaded the latest server on a new setup and decided to try and re-activate the firewall. So no manipulation, brand new server on latest version of Windows 10. Two different firewall programs tried, each time canyouseeme says no connection unless I disable them completely. 

Ionic, it's still very much an issue. I downloaded the latest server on a new setup and decided to try and re-activate the firewall. So no manipulation, brand new server on latest version of Windows 10. Two different firewall programs tried, each time canyouseeme says no connection unless I disable them completely. 

Ionic, it's still very much an issue. I downloaded the latest server on a new setup and decided to try and re-activate the firewall. So no manipulation, brand new server on latest version of Windows 10. Two different firewall programs tried, each time canyouseeme says no connection unless I disable them completely. 

Hi Tim,

I don't believe this to be an issue with BDS though. There are thousands of online BDS servers across the world. If it wasn't accepting connections we would have far more than one report in a blue moon.

Are you making sure you're opening the UDP port you have specified in the server.properties?

Edit: You also need to make sure you "Run as administrator" in Windows as it allows the process to open the port it needs.

Ionic

Hi Tim,

I don't believe this to be an issue with BDS though. There are thousands of online BDS servers across the world. If it wasn't accepting connections we would have far more than one report in a blue moon.

Are you making sure you're opening the UDP port you have specified in the server.properties?

Edit: You also need to make sure you "Run as administrator" in Windows as it allows the process to open the port it needs.

Ionic

Hi Tim,

I don't believe this to be an issue with BDS though. There are thousands of online BDS servers across the world. If it wasn't accepting connections we would have far more than one report in a blue moon.

Are you making sure you're opening the UDP port you have specified in the server.properties?

Edit: You also need to make sure you "Run as administrator" in Windows as it allows the process to open the port it needs.

Ionic

@Alex Colter I did have portforwarding for port 19132 for both TCP and UDP on my router. I have tried just having UDP and I still get the same results. I can connect from my LAN but any attempt to use my external IP yields "Unable to connect to world."

I also saw @IonicEcko's message and made sure to run bedrock_server.exe as administrator. Same results.

@Alex Colter I did have portforwarding for port 19132 for both TCP and UDP on my router. I have tried just having UDP and I still get the same results. I can connect from my LAN but any attempt to use my external IP yields "Unable to connect to world."

I also saw @IonicEcko's message and made sure to run bedrock_server.exe as administrator. Same results.

@Alex Colter I did have portforwarding for port 19132 for both TCP and UDP on my router. I have tried just having UDP and I still get the same results. I can connect from my LAN but any attempt to use my external IP yields "Unable to connect to world."

I also saw @IonicEcko's message and made sure to run bedrock_server.exe as administrator. Same results.

@Krys I hear ya. It can be super frustrating to figure the ports out. Mostly because devices will show you the config, but those configs are not copied into running, or are not saved. I agree with IonicEcko that your issue seems to be different. I had an issue where the packets were not hitting the server, but it was resolved by limited the protocol pass through to UDP.

I think you should try allowing UDP only on the ports on all devices that you have control over that will pass the Minecraft traffic. Example, your PC, Router, Modems. Make sure on your PC you are doing outbound/inbound, and same if those are options else where. Finally, give everything a power cycle when done.

@Krys I hear ya. It can be super frustrating to figure the ports out. Mostly because devices will show you the config, but those configs are not copied into running, or are not saved. I agree with IonicEcko that your issue seems to be different. I had an issue where the packets were not hitting the server, but it was resolved by limited the protocol pass through to UDP.

I think you should try allowing UDP only on the ports on all devices that you have control over that will pass the Minecraft traffic. Example, your PC, Router, Modems. Make sure on your PC you are doing outbound/inbound, and same if those are options else where. Finally, give everything a power cycle when done.

@Krys I hear ya. It can be super frustrating to figure the ports out. Mostly because devices will show you the config, but those configs are not copied into running, or are not saved. I agree with IonicEcko that your issue seems to be different. I had an issue where the packets were not hitting the server, but it was resolved by limited the protocol pass through to UDP.

I think you should try allowing UDP only on the ports on all devices that you have control over that will pass the Minecraft traffic. Example, your PC, Router, Modems. Make sure on your PC you are doing outbound/inbound, and same if those are options else where. Finally, give everything a power cycle when done.

It’s worth noting that most of us here are perfectly capable of port forwarding and most have reported successfully port forwarding to other servers and services.

Most specifically i can make the Java edition work easily.

It’s worth noting that most of us here are perfectly capable of port forwarding and most have reported successfully port forwarding to other servers and services.

Most specifically i can make the Java edition work easily.

It’s worth noting that most of us here are perfectly capable of port forwarding and most have reported successfully port forwarding to other servers and services.

Most specifically i can make the Java edition work easily.

Hi again,

@AlexColter - Thanks for trying to help me. I have tried with only UDP allowed through my router and Firewall. Same results. (Alas, same results with no firewall at all). I also tried power cycling everything.

I don't see where IonicEcko said my issue seems to be different. I think it sounds the same as Tim's.

Also like Tim, I have a different server working successfully--a Plex server and accessible via external IP.

Hi again,

@AlexColter - Thanks for trying to help me. I have tried with only UDP allowed through my router and Firewall. Same results. (Alas, same results with no firewall at all). I also tried power cycling everything.

I don't see where IonicEcko said my issue seems to be different. I think it sounds the same as Tim's.

Also like Tim, I have a different server working successfully--a Plex server and accessible via external IP.

Hi again,

@AlexColter - Thanks for trying to help me. I have tried with only UDP allowed through my router and Firewall. Same results. (Alas, same results with no firewall at all). I also tried power cycling everything.

I don't see where IonicEcko said my issue seems to be different. I think it sounds the same as Tim's.

Also like Tim, I have a different server working successfully--a Plex server and accessible via external IP.

What I'm suggesting is that this issue is not actually a bug in BDS but an environmental issue in your setup.

There are thousands of active BDS servers which proves the software works, and works externally, so the issue must be either environmental or configuration specific.

I realize that you're likely capable of port forwarding, I never implied you weren't, but human error is possible no matter how skilled the tech. Its also possible its caused by something you've never had to deal with before. For example Plex and related services do firewall configuration automatically, BDS you have to do it manually. The fact that your server worked the moment you disabled Windows firewall proves that it is a configuration issue - guaranteed.

If disabling Windows Firewall (something completely outside of BDS's control) worked, then its a mis-configuration of the Windows Firewall.

You're welcome to join the Community Support Discord and we can try to work it out if you like but I'm fairly confident based on the discussions so far we're not dealing with a bug.

Ionic

Edit: Also worth noting CanYouSeeMe won't show an open port, even for a working BDS instance.

What I'm suggesting is that this issue is not actually a bug in BDS but an environmental issue in your setup.

There are thousands of active BDS servers which proves the software works, and works externally, so the issue must be either environmental or configuration specific.

I realize that you're likely capable of port forwarding, I never implied you weren't, but human error is possible no matter how skilled the tech. Its also possible its caused by something you've never had to deal with before. For example Plex and related services do firewall configuration automatically, BDS you have to do it manually. The fact that your server worked the moment you disabled Windows firewall proves that it is a configuration issue - guaranteed.

If disabling Windows Firewall (something completely outside of BDS's control) worked, then its a mis-configuration of the Windows Firewall.

You're welcome to join the Community Support Discord and we can try to work it out if you like but I'm fairly confident based on the discussions so far we're not dealing with a bug.

Ionic

Edit: Also worth noting CanYouSeeMe won't show an open port, even for a working BDS instance.

What I'm suggesting is that this issue is not actually a bug in BDS but an environmental issue in your setup.

There are thousands of active BDS servers which proves the software works, and works externally, so the issue must be either environmental or configuration specific.

I realize that you're likely capable of port forwarding, I never implied you weren't, but human error is possible no matter how skilled the tech. Its also possible its caused by something you've never had to deal with before. For example Plex and related services do firewall configuration automatically, BDS you have to do it manually. The fact that your server worked the moment you disabled Windows firewall proves that it is a configuration issue - guaranteed.

If disabling Windows Firewall (something completely outside of BDS's control) worked, then its a mis-configuration of the Windows Firewall.

You're welcome to join the Community Support Discord and we can try to work it out if you like but I'm fairly confident based on the discussions so far we're not dealing with a bug.

Ionic

Edit: Also worth noting CanYouSeeMe won't show an open port, even for a working BDS instance.

I would love to agree with you on that one! However to make the environmental argument you would first have to ignore that I have the Java edition of the server working too, which does require the firewall. I also configure CCTV systems, Mail servers etc.

I also considered that there may have been a recent change to Windows Firewall in Win10 that I didn't understand, a bug or a limitation so I replaced it with Zonealarm, stil the same result. 

Have you downloaded and run the BDS server on your own home/work setup? 

What I am suspecting is that there is an issue with the Xbox authentication system communicating and that opening the ports just specified for the server is not enough.

I would love to agree with you on that one! However to make the environmental argument you would first have to ignore that I have the Java edition of the server working too, which does require the firewall. I also configure CCTV systems, Mail servers etc.

I also considered that there may have been a recent change to Windows Firewall in Win10 that I didn't understand, a bug or a limitation so I replaced it with Zonealarm, stil the same result. 

Have you downloaded and run the BDS server on your own home/work setup? 

What I am suspecting is that there is an issue with the Xbox authentication system communicating and that opening the ports just specified for the server is not enough.

I would love to agree with you on that one! However to make the environmental argument you would first have to ignore that I have the Java edition of the server working too, which does require the firewall. I also configure CCTV systems, Mail servers etc.

I also considered that there may have been a recent change to Windows Firewall in Win10 that I didn't understand, a bug or a limitation so I replaced it with Zonealarm, stil the same result. 

Have you downloaded and run the BDS server on your own home/work setup? 

What I am suspecting is that there is an issue with the Xbox authentication system communicating and that opening the ports just specified for the server is not enough.

I have, my public server runs on Windows Server 2019.

Was a brand new build as of a couple of weeks ago.

How are you testing the connection? Is it from an off network device or the local machine running the server software?

I have, my public server runs on Windows Server 2019.

Was a brand new build as of a couple of weeks ago.

How are you testing the connection? Is it from an off network device or the local machine running the server software?

I have, my public server runs on Windows Server 2019.

Was a brand new build as of a couple of weeks ago.

How are you testing the connection? Is it from an off network device or the local machine running the server software?

@Tim Turnill

Looks like your firewall is blocking it have you tried configuring your firewall correctly?

@Tim Turnill

Looks like your firewall is blocking it have you tried configuring your firewall correctly?

@Tim Turnill

Looks like your firewall is blocking it have you tried configuring your firewall correctly?

Hi IonicEcko,

I have a Windows Server non gui 2019 as well, but I stopped using it because of backup issues.

So for the purposes of this test we need to use Windows 10 with BDS. 

I have two premesis with three different ISPs, so testing locally and externally are not an issue for me. 

@Hot stuff, "Looks like your firewall is blocking it have you tried configuring your firewall correctly?" Thanks for that..

Hi IonicEcko,

I have a Windows Server non gui 2019 as well, but I stopped using it because of backup issues.

So for the purposes of this test we need to use Windows 10 with BDS. 

I have two premesis with three different ISPs, so testing locally and externally are not an issue for me. 

@Hot stuff, "Looks like your firewall is blocking it have you tried configuring your firewall correctly?" Thanks for that..

Hi IonicEcko,

I have a Windows Server non gui 2019 as well, but I stopped using it because of backup issues.

So for the purposes of this test we need to use Windows 10 with BDS. 

I have two premesis with three different ISPs, so testing locally and externally are not an issue for me. 

@Hot stuff, "Looks like your firewall is blocking it have you tried configuring your firewall correctly?" Thanks for that..

Hi Tim,

I was already building a Windows 10 VM when you commented as I assumed you would point to a difference between Windows 10 and Server 2019.

Please see below, tested 5 minutes ago, on a new install of Windows 10 1909 using BDS 1.14.32.1.

As you can see from the screenshot I have connected to the server from an external IP (in this case it was my phone on 4g).

Ionic

Hi Tim,

I was already building a Windows 10 VM when you commented as I assumed you would point to a difference between Windows 10 and Server 2019.

Please see below, tested 5 minutes ago, on a new install of Windows 10 1909 using BDS 1.14.32.1.

As you can see from the screenshot I have connected to the server from an external IP (in this case it was my phone on 4g).

Ionic

Hi Tim,

I was already building a Windows 10 VM when you commented as I assumed you would point to a difference between Windows 10 and Server 2019.

Please see below, tested 5 minutes ago, on a new install of Windows 10 1909 using BDS 1.14.32.1.

As you can see from the screenshot I have connected to the server from an external IP (in this case it was my phone on 4g).

Ionic

Alrighty, thank you for doing that test,  I will setup a new BDS on one of my new work machines tomorrow and send screenshots of results and workings.