Bitdefender Block Vmware Bridged Network
Hi,
I'm using Bitdefender Total Security 2013 and VMware Workstation 9 on Windows 7 64bit .
i have virtual machines need for internet access and network (Bridged Mode) but i'm unable to do it with the bitdefender firewall ON 
Only work with Firewall OFF .
Please help me to fix the problem
Best Regards
Catiaso
Comments
-
I too am having the same problem, but with VMWare Player with an XP Pro VM. No problems on the host machine, and the VM can access all local network resources and devices with no problem, just not the internet. If I disable the Firewall, then the VM can access the internet fine, when Firewall back on, again blocked. Access rules are made for VMWare and allow access, as far as I can tell.
Through the VM, I can ping the gateway, but any outside IP adx is blocked. What gives? Any ideas?
I am very close to just disabling the Bitdefender Firewall and using Windows or some other Firewall.
For reference, I'm running Bitdefender Internet security 2013 on Windows 7 Ultimate 64bit. Never had VM problems until Bitdefender installed.
Appreciate any help.0 -
As far as I know the Bitdefender set the Network Type "Untrusted" by-default in the Manage Adapters option. So first try to change the Network Type for that respective VMWare adapter. Also check in the Windows Network and Sharing settings.
0 -
As far as I know the Bitdefender set the Network Type "Untrusted" by-default in the Manage Adapters option. So first try to change the Network Type for that respective VMWare adapter. Also check in the Windows Network and Sharing settings.
Network Type setting is irrelevant. No matter how it is set, the problem persists. I tried every possible combination prior to uninstalling BD and installing Norton.0 -
To allow VMs to communicate with the outside world, you need to disable [Off] "Stealth mode" on your main adapter, the one used by the Host machine, not just the VMNet virtual adapters.
0 -
Hello,
A quick solution for the encountered issue is to upgrade to The New Bitdefender. The upgrade is absolutely free of charge and due to the many improvements brought to this lineup any issues you may have encountered with your current product are now solved.
In order to upgrade to the new version please follow the steps below:
http://forum.bitdefender.com/index.php?act...f=366&id=58
From now on, post in this area of the forum in case you encounter further issues after the upgrade:
http://forum.bitdefender.com/index.php?showforum=360
Thank you.0 -
A quick solution for the encountered issue is to upgrade to The New Bitdefender. The upgrade is absolutely free of charge and due to the many improvements brought to this lineup any issues you may have encountered with your current product are now solved.
Just tried that for "Bitdefender Windows 8 Security". No luck. I have to completely disable firewall for virtual machines to get any traffic in or out. Since I need these VMs all the time the firewall has to remain off and Bitdefender constantly reports "There are critical issues to fix".0 -
To allow VMs to communicate with the outside world, you need to disable [Off] "Stealth mode" on your main adapter, the one used by the Host machine, not just the VMNet virtual adapters.
Hello, I can confirm that, for me, this worked perfectly, thank you cmezza! I have the following setting, maybe this could help others: Windows 8, VMWare Workstation 9, local network with fixed IPs, my VM with IP from this class - no success in getting Internet on this VM unless BD firewall was completely OFF. As soon as I set "Stealth mode"on OFF, my VM was able to connect to the Internet.
Thank you again!0 -
I was able to solve it by configuring Kerio Traffic Rules. It blocks all unknown connections. So before the last rule where it blocks 'all others' I added two rules:
1 Block incoming from internet interfaces (for security)
2 Allow all from any to any (any service)
Then comes:
3 (default rule) block all0 -
A virtual network is a computer network that consists, at least in part,of virtual network links.A virtual network link is a link that does not consist of a physical connection between two computing devices but is implemented using methods of network virtualization. http://www.vcp5-dcv.com/
0 -
I'm on vmware workstation version 10 running on windows 8.1 in the same situation where none of my VM's can get inbound / outbound traffic.
Typical behavior of a virtual nic assigned to a host in a bridged fashion would show traffic from the VMware host and guest as well. tcpdump run from a guest VM shows this accurately even when firewall is turned on which shows vmware's switch is working properly.
However,
From the guest VM, I've done all your recommendations but at this point I cannot even ping a gateway, regardless of whether I choose nat or host only, it doesn't matter if I can't get to my gateway, I'm not going anywhere.
Where in your product lies the simple function to add a firewall rule or acl to allow traffic from source (guest VM subnet) to destination(gateway).
If we were working higher than application in tcpstack i wouldn't be able to see the traffic from the guest VM of host traffic on a tcpdump.
N/m figured it out.0 -
Upgraded to 2015 version of your total security product only to be in the same place as I was when i started.
Must disable stealth mode in order to get outbound/inbound access to VM's however this setting reset's itself on reboot.
Very irritating.
" />0 -
Hi. Are you using vCenter Server 5.5? Try to open the ports below.
http://kb.vmware.com/selfservice/microsite...ernalId=20515750 -
I had the same problem with VirtualBox.
Since switching off "Stealth Mode" (or "Netzwerk-Unsichtbarkeit") in Gravity Zone for the "wired network adapter", I could access the internet from within the virtual machine.
On 13.5.2013 at 10:30 AM, cmezza said:
To allow VMs to communicate with the outside world, you need to disable [Off] "Stealth mode" on your main adapter, the one used by the Host machine, not just the VMNet virtual adapters.
Compared to the reports above, I did not have to turn the mode off for the "virtual adapter".
Weird about this was that adding rules for the exec files of VirtualBox, allowing all ports, protocols ... did not solve the problem, even when moving the rule to the top.0
