virtualbox.org

Hello there friend.
I am running windows XP on virtual box as guest and windows 10 as host. I try to access share folder on other physical PC (windows server 2003) from Guest OS (Windows XP) on bridged mode network, it didn't wok. But when i change the configuration to NAT mode network it worked. How this happen? I already enable the SMB1 protocol on windows 10, and turn off firewall on each PC.
I still need to access folder sharing with Bridged Mode network because of the Apps configuration that i cant modify on system. And it need specified share folder's name that it can't change too.
Help.

Bridged does not always work over Wi-fi. See Virtualbox Networks: In Pictures: Bridged Adapter

Can you ping over the Bridged network? If your firewalls are all off, Ping should be able to get through. If you turn the firewalls back on, the firewall blocks Ping (ICMP Echo Request). You can turn this on in the firewall, then Ping will get through.

If you can ping one or both directions, then the network is working and something else in either OS, not Virtualbox, would be causing the problem.

No, it is over ethernet cable. The ping worked on both side. I assume the issue on port access for sharing, but i cant figured it out. Is that any different port access (disable or enable) between nat and bridged or something about public or private network thing?
But thank you for replying.

Good that you're on wired network, that takes wi-fi glitches out of the equation.

If you can ping, then the Virtualbox network is working.

Using Bridged removes any need to open ports in Virtualbox.

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. 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". Then a Windows wizard or other program opens the ports in the Windows firewall automatically.

I also have never tried to turn on SMB1 in Windows 10 so I could share folders to XP. I figure there was a reason it was turned off (WannaCry). There may be other things needed. Web-searching will be necessary to disclose these things.

Since your Virtualbox network is working and Bridged, the problem resides in your 10 and XP OS's. Pretend Virtualbox is not involved, that you have real 10 and XP computers on your network, and you want to share folders between them. Web-search how to do this with real computers, and the solution will work in your Windows 10 and XP host and guest.

If you enabled SMB1 on the Windows 10 host, disable it ASAP. That is a very dangerous thing to do.

https://techcommunity.microsoft.com/t5/ ... a-p/425858

The only devices which need SMB1 in this case are XP and WinServer 2003, and they both have it by default. They still use the old NT-style file sharing system which uses Netbios names and the computer browser service, which rely on SMB1.

I have no idea why you have this problem. I have been using bridged networking for more that 10 years to share files between physical and virtual machines running various Windows OSs without that sort of problem. The only problems I have struck are the normal problems with Windows file sharing and networks.

With these old systems, you need to remember that they can be very slow to react. The computer browser service takes quite a while to register a device in the browse list, and browser elections can cause further delays. I suspect you were too impatient.

Thank you for the responses guys.
I enabled SMB1 just for testing to make sure that the problem is not in the host PC (thanks for the warning btw).
Because in NAT mode network, SMB1 disable --> Can't access the folder. But, when i enable SMB1 in host, work perfectly.
And for additional information, i already tried for testing in between physical PC for share folder directly for Win Server 2003 and windows XP, it worked.
The problem is when i bridged the network, it cant access share folder.

That is very odd. I would not expect it to work in NAT mode at all. If I set a vm to NAT it still appears in the browse list but is unreachable (which is what I would expect). Have you enabled file sharing on public networks?

Did you run the network setup wizard in XP after you set it to bridged mode? XP does not automatically adjust to network changes. You need to run the wizard and select the option This computer connects to the Internet through a residential gateway .... so that XP knows it is on a LAN. I use password protected sharing on private networks only.

All I can tell you is that my Windows XP vms hosted as bridged on my local network can communicate with all other machines, virtual or physical, except Windows 10. This includes Windows 7, Vista, Win2k, NT4 and even Win98SE.

Advanced IP Scanner can also see the XP machines on the LAN and display their shared files. READYSHARE is a NAS device attached to my router. Frontier Silicon is an Internet radio. Fred, Hattie and Dave are physical machines and XPONDAVE and similar names are vms running on those physical machines as vms in bridged mode.