ShaneCC
asked on
Hyper V Server has no network connection after upgrade from 2012 to 2019
I upgraded a server that lives on a 2019 Hyper-V. I upgraded from 2012 to 2019. The server now has a Bang over the network connection. I disabled the adapter and enabled the adapter, I changed from dhcp to static and still nothing. I created a new virtual switch but and connected to that but it did not help.
When I attempt to ping the gateway I get the error
PING: Transmit Failed General Failure
When I attempt to ping the gateway I get the error
PING: Transmit Failed General Failure
is there an updated nic driver that needs to be installed?
ASKER
Hello,
Select the driver that is with the warning, right click and then update driver, once update the driver, validate if the vm has the same problem with the gateway.
Additional validates that you have enabled the services integrated in the vm.
Wan Miniport is a driver that allows the connection of alternative methods in Windows, such as Point-to-Point Protocols over Ethernet (PPPoE) and wireless WAN networks.
Select the driver that is with the warning, right click and then update driver, once update the driver, validate if the vm has the same problem with the gateway.
Additional validates that you have enabled the services integrated in the vm.
Wan Miniport is a driver that allows the connection of alternative methods in Windows, such as Point-to-Point Protocols over Ethernet (PPPoE) and wireless WAN networks.
At the level of virtual adapter, do you have any advanced features enabled at the adapter level in hyper-v ?. Check the vm configuration on the virtual hardware
ASKER
I reinstalled the driver for the WAN Miniport(IP). The Bang went away but still no connection. I opened an elevated command prompt and ran
netsh winsock reset. Still, after the restart, there is still no network connection.
netsh winsock reset. Still, after the restart, there is still no network connection.
Here are the settings I have on the virtual switch
screenshot shows a broadcom adapter but don't see that in device manager
i'd say that could be your problem
what kind of server is this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
validate the DNS of the virtual machine, also execute an ipconfig / flushdns and validate the connection of the vm again
ASKER
1) Stopping the VM,
2) removing the Network adapter,
3) re-adding the network adapter and connecting to the virtual switch.
4) starting the VM
2) removing the Network adapter,
3) re-adding the network adapter and connecting to the virtual switch.
4) starting the VM