Hacker News new | past | comments | ask | show | jobs | submit login

I tried Hyper-V for a while but I found the network configuration really cumbersome. Therefore I went back to Virtualbox but I should probably request my employer to buy a license for Vmware.



Is it because you switched frequently from one adapter to another (like wifi to ethernet)? Otherwise I don't think I ever had any problem with the network configuration.


In Windows 10, we provide a NAT network option by default. This should work seamlessly even if you switch between WiFi and Ethernet. So even this problem should go away for most people now.


Didn't the NAT get pulled from hyper-V?


I don’t think so. It’s only there by default on client, not server, though.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: