Windows Server 2019 Help

[PUGZSZ]

I have windows server 2019 on a small server I have. The server has 1 vm on it of windows enterprise and the only thing i want to have running on it is a Minecraft server for me and my friends. When I have the server running inside Server 2019 it works fine and everyone can connect, but when i move it to the vm no one is able to connect. I have made sure to foward the port for the vm and allow all the ports through the firewall. I am able to connect to is if im on the same network. Any help would be appreciated

[Dujith]

I think the server 2019 is a bit overkill, something like Ubuntu or any other linux based server would be better.

Having said that: The problem at hand is most likely your virtual switch which puts it outside the normal ip range.

 

How did you set that up?

[PUGZSZ]

4 minutes ago, Dujith said:

How did you set that up?

I'm not very knowledgeable with network setup, whatever is default is how its setup currently. And yes server 2019 is overkill i just wanted to learn more using it.

Using ipconfig i see that is still the same 192.168.0.xx setup for a local ip, and i can connect to it on my network. Ive been looking online and all ive been able to find is that it probaly has something to do with the fowarding or ports.

[Dujith]

Go into your VM settings and check the Virtual Switch. It should be set to external (private and internal will not connect to your network).

If you do not have a Virtual switch you should create one and set it to external.

[PUGZSZ]

1 minute ago, Dujith said:

Go into your VM settings and check the Virtual Switch. It should be set to external (private and internal will not connect to your network).

If you do not have a Virtual switch you should create one and set it to external.

I already have the vitrual switch set to external.

[Dujith]

Just now, PUGZSZ said:

I already have the vitrual switch set to external.

Okay, so next step is to see if you can ping the server from the hyperv server and then the other computers.

[PUGZSZ]

6 minutes ago, Dujith said:

Okay, so next step is to see if you can ping the server from the hyperv server and then the other computers.

Ok so i restarted the vm and the ip is now not 192.xxx.x.xx and i tried pinging it and i received all the packets but it says destination host is unreachable 

[Dujith]

1 minute ago, PUGZSZ said:

Ok so i restarted the vm and the ip is now not 192.xxx.x.xx and i tried pinging it and i received all the packets but it says destination host is unreachable 

That means you cannot reach it at that adres. When you started the VM and logged it. What ip adress has it and did you ping that adres?

Also from where you are pinging the VM, is that in the same ip range?

 

Example: the VM is at 192.168.1.100

The other computers are at 192.168.1.10 and 192.168.1.11 then they should be able to ping each other. If the VM is something like 192.168.10.100 then you cannot reach it by default.

[PUGZSZ]

11 minutes ago, Dujith said:

That means you cannot reach it at that adres. When you started the VM and logged it. What ip adress has it and did you ping that adres?

Also from where you are pinging the VM, is that in the same ip range?

 

Example: the VM is at 192.168.1.100

The other computers are at 192.168.1.10 and 192.168.1.11 then they should be able to ping each other. If the VM is something like 192.168.10.100 then you cannot reach it by default.

My default range is 192.168.0.1 and the vm is 169.254.67.19

Now the vm says that it is an unidentified network and that it has no internet access

 

[Dujith]

1 minute ago, PUGZSZ said:

My default range is 192.168.0.1 and the vm is 169.254.67.19

 

Okay, back to the virtual switch. It looks like its not tied to a ethernet adapter and thus does not give out an IP adress (169.x.x.x is the fallback IP when DHCP does not work)

Or the VM is not connected to the virtual switch. 

[PUGZSZ]

I have the network adapter assigned and so is the Ethernet adapter

 

I restarted the vm again and it now has a normal local ip

[Franck]

If it has the same class C assigned you should see it now. I was about to say you needed to setup the passthrough but seems ok now. I am not that much familiar with VMWave but looks good.

[Dujith]

Okay, that looks good so far. No its time to check the server why its not getting an adres.

Now my experience with windows server is pretty basic but i do believe that if it has a dhcp role it will not be able to receive an adres.

Someone with more Windows Server knowledge should see this thread and might know what is up.

 

nvm, just saw that i has a good i[ adres now.  

Can you ping it now?

[PUGZSZ]

18 minutes ago, Dujith said:

Okay, that looks good so far. No its time to check the server why its not getting an adres.

Now my experience with windows server is pretty basic but i do believe that if it has a dhcp role it will not be able to receive an adres.

Someone with more Windows Server knowledge should see this thread and might know what is up.

 

nvm, just saw that i has a good i[ adres now.  

Can you ping it now?

yes i can ping it

[Dujith]

2 minutes ago, PUGZSZ said:

yes i can ping it

Well, then you should be able to connect to it now, just make sure the firewall settings on the Server are correct (and that the network on the Server is not set to public)

[PUGZSZ]

What ip should i have the port fowarded to? The server or the vm.

[Dujith]

The VM

[PUGZSZ]

idk what it is now but i still cannot connect.

[Dujith]

2 minutes ago, PUGZSZ said:

idk what it is now but i still cannot connect.

You should prob set a static ip in the vm. And then write it down  

[Akolyte]

So, I think it's best I try to highlight everything since you might've missed something.  In fact, I guarantee this whole problem is just because you overlooked something simple and so it's important we highlight every possible step to raise awareness as to what that might be.  The easiest way we can tell if your ISP has natted your network is by hosting a simple server like a web server from the host server and port forwarding it, and if you cannot connect to it from the external IP address then, there is something wrong with your WAN setup, or your ISP has your network behind a locked NAT. 

 

So, you've made sure you have your adapter bridged as a physical adapter on the server, you've also made sure the VM is accessible from outside the server by being able to ping the server across the LAN and that the Minecraft server works and is not blocked by the Windows Firewall by being able to play over LAN. 

 

So, this means the problem has got to be between the router and the VM.  It's worthwhile disabling the Windows Firewall for a period because it might be blocking any external addresses connecting to your server, and make sure the rules on your router point to the VM's IP address, and that they are enabled, and then connect to the server via the external IP address.  I'm sure you know how it works, I just want to make it absolutely specific for the purposes of troubleshooting. 

 

Lastly, check over the minecraft server configs and make sure there's no option set for blocking external IP addresses from connecting.  If you do all of this and you still can't connect I don't know how to help you.  

 

There is software called Hamachi that's pretty much a VPN over Teredo, meaning it doesn't require any port forwarding, but it needs clients to all connect to each other and can lead to your friends access to your whole LAN, and that's not really what you want.  Otherwise, you'll have to setup a VPN through something like SoftEther which isn't too hard to do either, and use that.  The problem is it would be slower, but in good news if you configure it properly your network would be more secure from the outside.