Hello,
Initially should not be a challenge for WSL2 to connect through the Ethernet cable. Bear in mind that in some networks, specially corporate, both Ethernet and Wireless may have different settings that need to be configured in the virtual machine in order to be able to connect. Based on the premises and tests you performed, I would recommend to look into:
1.Check Network Adapter Settings: Ensure that the network adapter of your WSL 2 virtual machine is set to the correct network profile. In some cases, it might be set to "Public," which can restrict network access. You can change this in the Hyper-V Manager settings for your VM.
- Check Firewall Settings: in case of doubt, you can define Inbound and Outbound ruled both for WSL2 machine or per application. By default the ports needed by WSL are 80, 443 and 22
- Check if the DNS configuration is correct for the Ethernet connection
Run the next command in WSL to see the configuration with cable and also with Wifi, to detect differences: cat /etc/ resolv.conf
- Check for proxy settings.
You can edit proxy settings if need in the distribution, for example for Ubunto it should be the file "/etc/environment"
--If the reply is helpful, please Upvote and Accept as answer--