virtualbox.org

Hello

I use VBOX 4.0.12, I install debian and oracle linux and on both i cant ping outside my network. My card is bridged and i can ping my router, and other system in my network. In VBOX I install windows and in this OS is all right. How to solve this problem?

Check your Guest network settings. See the VirtualBox FAQ for some help identifying network issues. If that doesn't solve it, post your exact set up with IP addresses, Host and Guest.

I read this FAQ, but ping still not working. My host system is windows 7 (IP : 192.168.1.2, netmask 255.255.255.0 ), my guest system is debian(192.168.1.4, netmask 255.255.255.0 ) and oracle linux (192.168.1.3, netmask 255.255.255.0 ), my router/gateway 192.168.1.1. When my guest system is windows xp ping is working correct. Iptables -L is empty. How i can solve this problem ?

type ifconfig -a in a terminal from one of the Linux guests and post the results here.

OS Debian

ifconfig -a
eth0 Link encap:Ethernet HWaddr 08:00:27:d6:7e:49
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00fed6:7e49/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:794 errors:0 dropped:0 overruns:0 frame:0
TX packets:751 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:636513 (621.5 KiB) TX bytes:136310 (133.1 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

You are configured correctly. Check the firewall on the host to see if it is blocking you. (Temporarily disable the firewall to check) If this allows you to ping then create an exception .

You were right, the problem was the firewall. When i disable firewall on host system( ESET NOD ) ping began work.
Thanks for help.

Then it seems that the network filter of the firewall blocks traffic directed to the system, but not with the IP/MAC address combination of the Host. Check the firewall documentation to make an exception for it. If there is no such option, report it to the developer (ESET in this case) so they can fix this incompatibility with VB. If you want to stay protected by a firewall, then use the default Windows one, or a different one that does work with VB. Now it seems you need to have ESET disabled (unprotected) to have the VMs work.