Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
Can one confirm IP address range changed to 192.168.X.Y Subnet 255.255.255.240 from 172.X.X.X
Also changes the subnet randomly on every Hyper-V services startup. 192.168.X.Y . X can change from 51 thru 180.
Although this is working on DHCP based IP assignment on guests, It is causing issues on static IP as it keeps changing after every boot
Regards,
Bala
135 Replies
- H3ALYCopper Contributor
Take a look at your Default Switch in Virtual Switch Manager, is it set to "External Network" with a defined controller or is it set to "Internal Network"?
- Bala SundaramBrass ContributorErratic IP address assignment issue is fixed in Build 17763. 134.
I am bit confused about the last post about checking in the VSM for External/Internal network that is association. We are talking about Default Switch supplied by MS for NATing from Configuration version >7.0. MS easy way of old fashioned internet connection sharing. It is always EXTERNAL. I am sorry not able to make any sense. We are not taking about a custom Switch that is associated with any network type (External/Internal/Private)- cbj4074Brass Contributor
Bala Sundaram is correct in that the Connection type cannot be changed for the Default Switch (all of the options are grayed-out), H3ALY , even with all VMs powered-off.
In any case, I have the same problem/question as Remon li . All I'm trying to do is assign a static IP address to a guest VM so that it doesn't change on me unexpectedly. I'd really like to satisfy the following requirements:
- Be able to specify the IP address to be used in the guest VM, e.g., 192.168.10.10.
- Be able to accomplish the above programatically, so that it can be done as part of an automated provisioning process (e.g., via Vagrant).
- Give Internet access to the guest VM via NAT (exactly as is done with the Default Switch). To be clear, I am amenable to using the Default Switch (instead of creating a new one), as long as its IP address does not change on me.
It sounds as though this is a two-part problem, and the first part is fixed in Build 17763.134, so at least the subnet will no longer change at random.
Bala Sundaram , when you say, "Erratic IP address assignment issue is fixed in Build 17763. 134", how many of the four octets are now "fixed"? The first three? In other words, do you now find that the address is predictably set to 192.168.XX, where XX never changes unexpectedly (nor the 192.168 part)?
Thanks for any clarification that you're able to provide!
- Bala SundaramBrass Contributor
It appears to be very random.
Default switch again reverted back to 172.17.X.X .
Strange.
- Remon liCopper Contributor
Yes, I got same problem and can not find any answers to get a fixed ip for default switch.