If I set a vm to NAT it still appears in the browse list but is unreachable (which is what I would expect). I would not expect it to work in NAT mode at all. Dec 2009, 20:14 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Windows, Linux scottgus1 Site Moderator Posts: 16602 Joined: 30. Web-search how to do this with real computers, and the solution will work in your Windows 10 and XP host and guest. Pretend Virtualbox is not involved, that you have real 10 and XP computers on your network, and you want to share folders between them.
Since your Virtualbox network is working and Bridged, the problem resides in your 10 and XP OS's. Web-searching will be necessary to disclose these things. I figure there was a reason it was turned off (WannaCry). I also have never tried to turn on SMB1 in Windows 10 so I could share folders to XP. Then a Windows wizard or other program opens the ports in the Windows firewall automatically. Windows handles this when I have tried to share the first folder in the OS: A popup asks if I want to turn on "File and Printer Sharing" or "Network discovery".
I have never had to set up special ports either in Virtualbox or in Windows to get shared folders to work, though I believe there are ports necessary in the Windows firewalls. Using Bridged removes any need to open ports in Virtualbox. If you can ping, then the Virtualbox network is working. Good that you're on wired network, that takes wi-fi glitches out of the equation.
0 kommentar(er)
