Windows 10: VMware - Force VM to use "Internal" Virtual Nic and not installed Nic

Hi there

Anybody know how to get VMware to use its own Virtual NIC for Windows rather than the hardware Nic's / Wifi Nic's when VM's are running on the same machine as the Host.

I've got HOST W10 PRO
Two VM's -- centos and Linux Mint running on same local machine as the Host.

Windows-> to either of the Linux machines or either of the Linux machines to windows - Max data transfer I get is about 12 MB/s (50 Mib/s). That's about right for the wifi adapter I'm using.

Strange thing is from VM1 to VM2 (or the other way around) data transfer from the SAME HDD is around 80 MB/s (320 Mib/s) or so -- so nearly 7 (yes SEVEN) times faster.


Seems Windows wants to use the physical hardware nic while the Linux machines are using "Virtual Ethernet adapter" 1 Gib/s which is what I want. I.e Disk I/O through computers I/O bus and not via networking.

Must be something in Windows setting for this - note I can't use Host only networking as I want all 3 machines to be able to access each other.

Any ideas folks.

Cheers
jimbo

:)

 

CALL-LEVEL INTERFACE- USING IP ADDRESS

You are correct that the Guest VM is connecting through the Ethernet 2 adapter. When VMWare/VMWorkstation is installed on a computer it will create virtual network adapters off the physical NIC on the computer. This is what allows you to do certain things
like create multiple virtual subnets for your VMs. This is particularly useful in lab setups but for other reasons as well. The IP address shows up as 192.168.74.1 in the command because that is the IP of the virtual adapter on the
host computer.

As for changing the IP address of the guest VM that is a matter of preference, but I would not recommend setting it to 192.168.74.254 as that appears to be the address of the DHCP server the host machine got it's IP address from, and that could create a
conflict. Otherwise in a setup like that changing the IP address to something else wouldn't offer any real advantage.

 

Hyper-V host cannot RDP into local clients running in an internal network

I have installed Hyper-V on my Windows 10 machine and are running a few different test machines on it. My test machines have two Nics -- One is disabled and primarily used when I need them to connect with the internet for various downloads etc. The other
Nic is connected to an internal switch on the host with hardcoded IP's allowing the VMs to always communicate with each other.

My problem is when I attempt to RDP into the VMs from the host machine I am not able to reach them. IF I log into the machines first through the Hyper-V console and toggle a Nic (i.e. disable/enable one of the nics) I am able to RDP into the VM until it
is rebooted again (My host is a laptop so they are being shutdown nightly).

I did mess around with the network settings on a previous setup and had it working -- but I am unable to reproduce the same settings. Currently the host is all "auto" setup by the system with three switches:

• External linked to my Wireless Nic
• External Linked to my Physical Nic
• Internal switch used for the VM's communicate amongst each other

Any ideas on what network settings I am missing that will allow me to connect to the VM's instantly through an RDP connection? (I can console connect but prefer using RDCMan).

Thanks,

HP

 

2019058, check out that kb article from vmware.

 

Have you tried poking around in the Virtual Network editor, You can add a virtual nic or hardware nic

• Open a VMware Workstation window.
• Choose Edit > Virtual Network Settings.
• The Virtual Network Editor appears, with the Summary tab active.
  https://www.tenforums.com/attachmen...editor.jpg?s=c1e8b753a573dc6e5ffc1ac8c4009171