Windows 10: Does Hyper-V Actively Block Some Connections Between Server and Client?

We've recently upgraded users to Windows 10 Pro. Some of our proprietary software requires legacy windows OS's so we now run Hyper-v severs on the machines and remote into them.

One user can't connect. The VM and host are on the same subnet and I can easily remote into her hyper-v Virtual machine from my desktop but she can't even ping from her own machine. The DNS knows where both machines are and they can both see other computers on the network but I can't even ping using the IP address.

It's worth noting that the VM in question is Windows XP and another virtual machine running Windows 7 has no troubles on the same machine with the same settings.

It doesn't matter if the host and virtual machine have an internal or external connection. I was even able to remote into a second machine that has access to my host and click on the link to the assets I need and was blocked.

What, pray tell, am I missing?

:)

 

Connect to Hyper-V on Win Server 2012 from Windows10 client

Hello, I have really big issue to connect to my hyper-v installed on Windows Server 2012 core, I was using it on my laptop as always, but after I upgraded to Windows 10, I am no longer able to connect. I added Windows feature Hyper-V manager, I tried to
add hyper-v to trusted host because it is not part of domain. still no luck, When I try to connect from windows 8.1 pc with the same credentials and same address and on the same network it works well.

I know there is some new version of hyper-V manager in windows10 , version 6.3 but I need to manage these servers without upgrading to Windows Server 2012 R2.

I am still getting errors like Check that the Virtual Machine Management service is running and you are authorized to connect to server. As I mentioned above, I have rights to connect because it works from another PC.

what else can I try to solve this problem ?

Thank you , Best regards Lucas

 

Why is Hyper-V-Manager consuming so much bandwidth?

Hello Jennifer,

Thank you for your support.

The setup is quite simple:

• The Hyper-V Server is a Root-Server in the Internet (not in a domain). It is only managed by myself (whatever that means )
• The server is a "Hyper-V Server 2016" (see e.g. https://www.microsoft.com/de-de/evalcenter/evaluate-hyper-v-server-2016)
• My Notebook connect's via Server Manager (This connection uses 8 kBit/se or less on average)
• When I open Hyper-V (via the Server Manager) it uses 500kBit/s permanently, without even connecting to a VM. Just listing the VMs on the server.

Michael

 

Help setting up Hyper-V to test Windows Server 2016


Hi,

I need a bit of help setting up a virtual environment, so I can try out Windows Server 2016. I'm quite new to Windows Server in general, but I'd like to get to know it better and start learning about its major features etc. I'd like to set up a virtual environment in Hyper-V but I could do with a bit of advice with setting it up please.

I'd like to test Windows Server 2016 out in Hyper-V along with having say a couple of VM's with Windows 10 Pro on so that they can connect to the Server so I can try out things like Active Directory, Group Policy etc.

What I was concerned about though is the Windows Server interfering with my home network. I would ideally like to have both Windows Server 2016 and the client VM's on their own virtual network in Hyper-V, away from my physical home network. So to summarize:

• All Virtual Machines to be in Hyper-V (Windows Server 2016 and Windows 10 Pro clients)
• The Server and Pro clients need to talk to each other and ideally have Internet access
• I'd like to use Hyper-V rather than VirtualBox etc. Not that I dislike VirtualBox and the like, it's just that I'd like to get used to using and knowing the features of Hyper-V
• Hyper-V is already installed on my physical Windows 10 Pro Desktop PC
• This Windows 10 Pro Desktop PC is currently connected to my normal home network and has Internet access

The main thing I am unsure of is the networking side. I'd like the Server and client VM's to not have full access to my home network, so they can't interfere with it. So is it possible for the VM's to talk to each other, have Internet access, but not be able to interfere or be seen by other physical machines on my home network?

I hope I've explained it correctly. I have had a look myself into this, I was thinking of maybe using an 'Internal' virtual switch in Hyper-V, which sounds like it may do the job of letting the VM's talk to each other and possibly getting Internet connection from the physical machine that Hyper-V is installed on. I'm not sure if this is the way to go though, so I thought I'd ask for some advice before setting it up in Hyper-V.

Thanks