I have confirmed what Valiante commented as resolving my issues.
"Indeed, sudo ethtool -K eth0 tx off worked a treat for me too."
Running that command results in the following
Actual changes:
tx-checksumming: off
tx-checksum-ipv4: off
tx-checksum-ipv6: off
tcp-segmentation-offload: off
tx-tcp-segmentation: off [requested on]
tx-tcp6-segmentation: off [requested on]
Edit:
I was able to use the regular non legacy network adapter and not have to keep doing the ethtool script as well.
Adding the following to my netplan yaml file fixed the issue the same as using the ethtool command
transmit-checksum-offload: off tcp-segmentation-offload: off tcp6-segmentation-offload: off
The other option is to run a Legacy Network Adapter on Hyper-V hosts which is not ideal either.
My config:
Host: Windows Server Core 2019 Hyper-V role
BDS: v1.19.41
Guest VM: Ubuntu 20.04 LTS
Host Network: Intel X710
Running either Legacy Network Adapter or using 'sudo ethtool K eth0 tx off' on a regular Hyper-V network adapter allows a remote Windows Client connect successfully. On the same VM Host a Windows guest VM running the same Windows BDS version has worked previously as well.
I have actually had this problem all the way back into v1.18. Same VM that was working migrated from vSphere 6.7 to a Hyper-V host no longer works without the above listed changes.
Kal326
I have confirmed what Valiante commented as resolving my issues.
"Indeed, sudo ethtool -K eth0 tx off worked a treat for me too."
Running that command results in the following
Edit:
I was able to use the regular non legacy network adapter and not have to keep doing the ethtool script as well.
Adding the following to my netplan yaml file fixed the issue the same as using the ethtool command
transmit-checksum-offload: off
tcp-segmentation-offload: off
tcp6-segmentation-offload: off
The other option is to run a Legacy Network Adapter on Hyper-V hosts which is not ideal either.
My config:
Host: Windows Server Core 2019 Hyper-V role
BDS: v1.19.41
Guest VM: Ubuntu 20.04 LTS
Host Network: Intel X710
Running either Legacy Network Adapter or using 'sudo ethtool
K eth0 tx off' on a regular Hyper-V network adapterallows a remote Windows Client connect successfully. On the same VM Host a Windows guest VM running the same Windows BDS version has worked previously as well.I have actually had this problem all the way back into v1.18. Same VM that was working migrated from vSphere 6.7 to a Hyper-V host no longer works without the above listed changes.