virtualbox.org

Hi,

I am writing this with my hands folded, head bowed down.

Please help me, anyone.

I have Windows 10 pro host in which I have installed virtualbox Version 6.1.16 r140961. I have an image running CentOS 7 on it. I am using bridged network.
after I start my vbox image. I am able to ping it from my host perfectly fine. but guest is not able to ping host. But another strange thing is that I have another laptop. both this laptop and vbox image are able to ping each other. I am even able to ssh into vbox from that laptop. But i am not able fix why my vbox image is not able to ping the host and also internet is not available on it. Everything is on my home-wifi network. From my vbox image I am even able to ping my router, 192.168.0.1

I have put static IP address in the guest.


I used terms guest and vbox image interchangeably. But they mean same.

I have tried everything for last 48 hours (literally). I don't even remember what all I have tried. please be my god and help me out so I can sleep atleast. This problem is driving me crazy like hell. Whatever information you want to help me, i will provide.

My network configuration is as below:

************************************************

On Host:

Windows IP Configuration

Host Name . . . . . . . . . . . . : server
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 9E-B6-D0-01-EE-E1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : AE-B6-D0-01-EE-E1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Killer Wireless-n/a/ac 1535 Wireless Network Adapter
Physical Address. . . . . . . . . : 9C-B6-D0-01-EE-E1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::89fe:bb61:f1ee:211c%19(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.27(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, 17 January 2021 14.13.40
Lease Expires . . . . . . . . . . : Monday, 18 January 2021 14.13.40
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 161265360
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-94-DF-01-80-FA-5B-21-58-E9
DNS Servers . . . . . . . . . . . : 193.162.153.164
194.239.134.83
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 9C-B6-D0-01-EE-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

************************************************************************************

************************************************************************************
on guest (centos 7)

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.42 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::b93c:7428f344 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:e7:59:07 txqueuelen 1000 (Ethernet)
RX packets 139 bytes 13195 (12.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 379 bytes 39486 (38.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 4 bytes 340 (340.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4 bytes 340 (340.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:13:7d:6a txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
*****************************************************************************************

Thanks

bentex wrote:after I start my vbox image. I am able to ping it from my host perfectly fine.

If you can ping even one direction then the network is connected.

bentex wrote:but guest is not able to ping host.

Windows defaults to blocking Ping in its firewall. Have you enabled it?

ICMP Echo Request is the Windows firewall item to enable.

hi scottgus1,

Thanks you so much for your reply.

while I was waiting for someone to reply. I thought to create a fresh image of CentOS 7 and check if that works. To my surprise, everything is OK with the new image. all the settings in the new image are same as in the faulty one. I really don't understand what is causing issue in it. This faulty image I had exported from a linux host and added onto the Windows 10 host. I am not sure if a migrated image is the reason here. Though I have migrated images in past also and they have always worked.
If new image is able to connect to internet then I think firewall may not be the issue.
I have decided to create all new images and migrate my apps and data from the old images. Very long process for me as I have almost 15 images.

bentex wrote:If new image is able to connect to internet then I think firewall may not be the issue.

Windows firewall typically does not interfere with network traffic getting out of the computer. Also, VM's attached with Bridged are connected to the network before the firewall is placed. So Bridged VMs are not filtered by the firewall.

The firewall does filter traffic into the host OS, so it would block ping from the VM to the host.

However, if you have tried another VM and you can ping the host from the new VM, then the host firewall is not interfering with ping. I don't know why one VM could ping the host and the other one can't. Your IP listings seem to show correctly-matched IP addresses.