On a number of occassions when we deploy an existing template or publish a template for our Hyper-V classes, the Hyper-V VMs lose the ability to connect to the internet. After some playing around I found that the NetNat service often fails to run which causes the internet to not work through the Nat created on the host VM template.
Is anyone else getting this issue?
To setup the NAT to allow internet access to the Hyper-V VMs, I run the script provided by MS doco on Azure Lab Services (https://docs.microsoft.com/en-us/azure/lab-services/classroom-labs/how-to-enable-nested-virtualizati...). I run this on the template before publishing.
I'm not sure how the Nat service works but WinNat service isn't visible in the Services.msc gui or if you do a "get-service -Name *" in Powershell. To verify if the NAT service is running, run Get-NetNat and you should see if the Nat Active status is True or False. If it's false, internet won't work for your Hyper-V VMs.
To fix it I put a script on the template and get it to run when the user logs into the VM via registry
Check_NetNat_Service.ps1
$netnat = Get-NetNat
If ($netnat.Active -eq "False") {
Start-Service WinNat
Write-Host "WinNat Service has been started" -ForegroundColor Green
}
Else
{
Write-Host "WinNat Service is already running" -ForegroundColor Cyan
}
From what I can see. The publishing breaks or causes the NAT service to not run on the deployed VMs. This is a bit annoying to configure as most teachers won't understand how to fix this, so I need to set this up for these types of labs.
Accepted Solutions