[solved]Comodo firewall conflict, again.

Discussions related to using VirtualBox on Windows hosts.
Post Reply
NoNoNo
Posts: 51
Joined: 16. Apr 2015, 17:35
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)

[solved]Comodo firewall conflict, again.

Post by NoNoNo »

Still got some networking problem after upgrade to 5.0.4

further reading: Suspected firewall bug at comodo forums
  • HOST is Windows 7 64-bit
  • GUEST is Windows XP
Today after upgrade to 5.0.4, all bridged networking failed. it turns out another comodo related problem. Bridged networking work after I killed comodo firewall driver. (NAT networking also work with comodo firewall.)

I need Bridged networking right now, and cannot find handy replacement of comodo firewall. I might stay on version 4.3.x awhile.

Due to previously suggestion (warn users about conflict products, like Comodo...etc.), and unanswered question at comodo forums, Try not to install Virtualbox 5.0.x today if you depend on Comodo firewall product.
Last edited by NoNoNo on 11. Sep 2015, 09:49, edited 1 time in total.
NoNoNo
Posts: 51
Joined: 16. Apr 2015, 17:35
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)

Re: Comodo firewall conflict, again.

Post by NoNoNo »

I got some hint said user can switch to old version of bridged network driver.
( read here: cannot ping host <--> VMs after upgrade to VirtualBox 5.0.x )

After change to NDIS5 version, my HOST can connect GUEST now. (with VBox version 5.0.4, Bridged networking)

I'm glad to throw this problem out my window.
NoNoNo
Posts: 51
Joined: 16. Apr 2015, 17:35
Primary OS: Debian other
VBox Version: PUEL
Guest OSses: Windows XP(32bit) / Debian 8.x / Debian 7.x / Windows 7(32bit)

Re: [solved]Comodo firewall conflict, again.

Post by NoNoNo »

As test-results today, bridged networking with guest is no longer a problem with VBox 5.1.26.
Post Reply