Daniel
- ShadowDrakken
- shadowdrakken
- America/Chicago
- Yes
- No
Some hopefully helpful information:
As you can see below, the bedrock server executable (PID 10588 at the time I ran the command) is not actually opening a TCP listening connection in a normal way. Which is why it can only be seen over the local network, and not through routers. Between these two command below, you can see that there's some funny business going on with the way the Bedrock server and clients talk to one another.
PS C:\WINDOWS\system32> Get-NetTCPConnection -OwningProcess (Get-Process bedrock_server).Id
Get-NetTCPConnection : No MSFT_NetTCPConnection objects found with property 'OwningProcess' equal to '10588'. Verify
the value of the property and retry.
At line:1 char:1
+ Get-NetTCPConnection -OwningProcess (Get-Process bedrock_server).Id
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (10588:UInt32) [Get-NetTCPConnection], CimJobException
+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_OwningProcess,Get-NetTCPConnectionPS C:\WINDOWS\system32> Get-NetTCPConnection -LocalPort 19132
Get-NetTCPConnection : No MSFT_NetTCPConnection objects found with property 'LocalPort' equal to '19132'. Verify the
value of the property and retry.
At line:1 char:1
+ Get-NetTCPConnection -LocalPort 19132
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (19132:UInt16) [Get-NetTCPConnection], CimJobException
+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_LocalPort,Get-NetTCPConnection
I'm having the same problem as Ron. Ports forwarded correctly, even tried DMZ. Turned off both the router and computer's firewall, and still the port comes up as not being open when tested. The same computer hosts StarBound just fine, I can even host it using the same ports (not at the same time obviously) and it works just fine, so it's not an ISP blocking issue either.