1
In Windows 10 Pro PC (Win10ProPC#1) I have a Ubuntu 18.04.02 LTS VM, created quite some time ago. I have also been using ever since, the following command, as part of a script. So running the following command in Win10ProPC#1
Get-vm -Name Ubuntu18.04.2LTS | Select -ExpandProperty NetworkAdapters
Returns
VMName IPAddresses
------ -----------
Ubuntu18.04.2LTS {172.17.199.244, ffff::ffff:ffff:ffff:ffff}
I recently recreated the same environment in another PC, with similar specs (Win10ProPC#2). There is a small change, the Ubuntu VM is now Ubuntu18.04.3LTS. However running the following command in Win10ProPC#2
Get-vm -Name Ubuntu18.04.3LTS | Select -ExpandProperty NetworkAdapters
Returns
VMName IPAddresses
------ -----------
Ubuntu18.04.3LTS {}
In both cases the VM(Guest) has internet access and I can find out the ip address from inside the guest operating system. (While this confirms that there is an IP it is not what is desired. I need to get the IP from the above command.)
The problem is that there are no IPAddresses reported in NetworkAdapters in Win10ProPC#2 while there are some in Win10ProPC#1. I need to make Win10ProPC#2 able to get the IPAddresses of the VM.
The two computers use the latest Windows 10 Pro version (64bit). Also both VMs have a dynamic IP and use the "Default Switch" network configuration. The scripts run by Powershell "as Administrator" in both cases.
I fear that I miss a setting or configuration, but a have already scrutinized all settings of the HyperV and are identical. Any thoughts?
1Is there a difference in the Windows 10 versions between the two computers? Does the VM have a static IP address? – harrymc – 2019-11-26T21:29:21.623
The two computers use the latest Windows 10 Pro version (64bit). Also both VMs have a dynamic IP and use the "Default Switch". I will also edit the question to include this info. – Spyros K – 2019-11-27T08:12:22.700