Guide pour Windows Server 2019 Support technique et ressources officielles
Guide pour Windows Server 2019 Support technique et ressources officielles
I'm running Windows Server 2019 on a compact machine with one VM of Windows Enterprise. My goal is to run a Minecraft server for myself and friends. It functions well when hosted inside Server 2019, but connections fail when moved to the VM. I've forwarded the port and kept all ports open via the firewall. I can access it only on the same network. Any advice would be greatly appreciated.
I believe the server version 2019 might be too advanced; a simpler Linux distribution like Ubuntu could work better. Still, the issue seems to lie with your virtual switch, which places it beyond the standard IP range. How was this configuration done?
I'm not very familiar with network configuration, so everything is as it currently stands. Server 2019 seems a bit too advanced for my needs—just wanted to get more experience. Through ipconfig I see the same local IP range (192.168.x.x) and can connect to it on my network. I've checked online, but all I found suggests it's related to forwarding or ports.
Open your VM configuration and verify the Virtual Switch. It must be configured as external; private and internal connections won’t reach your network. Without a Virtual Switch, create one and ensure it’s set to external.
Now check if you can reach the server via the hypervisor host and then from other machines.
The VM restart changed its IP address, and despite receiving packets, the destination host appears unreachable.
This means you can't access it from that location. When you began the virtual machine and logged in, what was its IP address? Did you send a ping to that address? Also, are you connecting from the same network range as those other devices? For example, if the VM is at 192.168.1.100 and the others are 192.168.1.10 and 192.168.1.11, they should be reachable. But if the VM is at 192.168.10.100, it won't be accessible by default.
The default network is set to 192.168.0.1, while the virtual machine is at 169.254.67.19. The VM reports it as an unrecognized network with no internet connection.
The virtual switch appears unrelated to an Ethernet adapter, so it doesn't assign IP addresses. The VM isn't linked to the switch either.