Page 1 of 1

[Solved] High risk sites blocked in VB

Posted: 16. Jun 2015, 21:53
by virbox77
Hello,

I currently run Windows 7 as a HOST OS and run Windows 8.1 as a GUEST OS in VirtualBox.

I've installed MBAM [Malwarebytes] premium Edition (Trail) in HOST OS (W7) with malicious website protection ON. When I try to access high risk websties in HOST OS (W7), MBAM blocks it w/ pop-up notification, which is what it supposed to do.

I did NOT install MBAM in GUEST OS (W 8.1). But, when I try to access same high risk websites as in HOST OS (W7), MBAM still seems to blocks it. I do not get the pop-up notification here. This is NOT what MBAM supposed to do. Right? I do want to access high risk websites in GUEST OS (W8) to isolate from GUEST OS.

When I uncheck malicious website protection from MBAM in HOST OS, I am now able to access high risk websites in both HOST and GUEST OS.

Is there a way to access high risk websites in GUEST OS but NOT in HOST OS w/ MBAB malicious website protection ON (checked)?

I don't know how the networking between the HOST & GUEST OSes work. It seems to have 2 separate IP addresses. At the bottom of VB, when I point the cursor at the network icon, it says "Adapter 1 (NAT): 10.0.2.15, Cable Connected"

I'd appreciate any help on this. Thanks in advance.

I've also posted this in malwarebytes forum.

Regards,

Virbox77

Re: High risk sites blocked in VB w/o installing Malwarebyte

Posted: 17. Jun 2015, 08:09
by mpack
If you are using NAT then you are using the host to make internet connections. So of course you can access the same websites as the host.

Network modes are explained in the user manual.

Re: High risk sites blocked in VB w/o installing Malwarebyte

Posted: 18. Jun 2015, 00:05
by noteirak
If you want the guest to be independant, set the Network adapter config of the VM to "Bridged". As mpack said, go check the user manual for an introduction before doing anything.
Another way is to whitelist VirtualBox in Malwarebytes

Re: High risk sites blocked in VB w/o installing Malwarebyte

Posted: 23. Feb 2016, 14:29
by virbox77
Thanks mpack, noteirak for your responses.

My apologies for such a delayed response. I thought I've already responded and closed the post.

I did tried the "bridged" approach and that did the trick on vbox 4.x versions.

Again, my apologies!!

Regards,

virbox77