

Start the VM in UI-less mode, then startup RDP-app and open the connection - result: full-screen Windows 10 machine on my Mac with connection to my network router, so I can access my printer, NAS etc and the internet - access to my mac only via shared folders (which is OK for me)ĭespués de mucho tiempo de batalla, encontre la solución, tengo BigSur 11.2 y dos VB con Win10, uso el puente connected in bridge-mode to en0: y FUNCIONA, corrige el problema de duplicación IP4 y acceso a Internet. RDP connection configured to connect to IP 192.168.56.101 no special settings (used the app out-of-the-box, only IP (and connection name) set Microsoft Remote Desktop App Version 10.5.0 (1841) Two Network Cards, Card 1 Host-only adapter (no changes), card 2 NAT (no changes, no port forwarding)

Remote Desktop allowed, Serverport 5940 Windows 10 VB uses half of my MacBook (2 CPUS, 8 GB RAM) VirtualBox 6.1.16 R140961, VBox Guest Additions 6.1.16 installed, shared home-folders Update 3.12.: Works fine for me - thank you all for your advice!! and will give feedback here as soon as I have a result. After some first test that looks promising with Catalina - so I will try to upgrade again to Big Sur the next days. Your article, Scott, led me to my new settings: Use two network cards: one in host-only network mode for the RDP-connection and the second in NAT mode for connection to the internet and my network (I do not need a connection from my PC VM back to the host. So I went back to Catalina (I was lucky to backup before upgrading!!!) MS Remote Desktop refused to connect to the VB machine (or did not find it. I used this solution some months before I upgraded to Big Sur - where this setting did not work any longer. This mode had the positive side effect that I could, when at home, connect from Windows to my other network appliances (printer, NAS etc.) and the internet without changing any setting.


But for this I needed access from the host to the guest - which worked fine (at least on my machine) using bridged mode for the network connection. This led to the next 'mitigation': start the VM in UI-less mode and use the MS Remote Desktop app as the windows UI. This is not really funny if you are standing on a stage trying to entertain an audience. I experienced randomly very long response times to my inputs (several seconds between click and reaction). The next challenge was that, at least in my environment, the windows UI contained in VB did not work 'flawless'. 'So my solution was: take a Mac and run a VirtualBox VM with windows 10 on it. I use a software which is only available in windows 10 - but I appreciate working on a Mac 6.1.16 is out already thank you for the article with the brief description of the network modes of VB, this (hopefully) helped me solving my challenges!!
