Bridge internet issue VB Version 5.2.12 r122591 (Qt5.6.2) can't access internet

[BlurR]

I'm using windows 10 pro 64-bit (10.0, build 17134) in the host pc and windows 10 pro 32-bit (10.0, build 10240) in the vm.
My VB version is 5.2.12 r122591 (Qt5.6.2)
I searched for the solution in google and YouTube from the past few days but failed to find a solution. I'm sorry I don't understand the related forum topic and request for a clean instruction to solve this issue of mine.

I'm trying to use bridge network on my VM but I can't connect to the internet. It says "unidentified network" on the adapters tab. The network of vm can ping internal ip's of the other connected machines including the host machine on the router but can't ping default getway (192.168.1.1) or access the internet .
I've choose the correct internet adapter in the vm settings.
My host pc ip is 192.168.1.2
I've set the ip address of the vm's Ethernet adapter to 192.168.1.7 in the adapter properties (ipv4).

Please give me a solution.

[socratis]

I've set the ip address of the vm's Ethernet adapter to 192.168.1.7 in the adapter properties (ipv4).

Why did you manually assign an IP?
What happens if you choose the "Automatic" option? (hint: it should work)
Most probably you didn't assign a gateway for your VM (inside the VM, network configuration). Compare the output of the following command from your host and your guest and see the differences:

• 
  ipconfig /all

For reference, here's what a Win10 VM's above command output is ("chopped" to focus only on the Bridged adapter for brevity):

Ethernet adapter Bridged:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter #2
   Physical Address. . . . . . . . . : 08-00-27-B0-66-57
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::648c:9932:d657:3265%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Παρασκευή, 29 Ιουνίου 2018 7:26:10 μμ
   Lease Expires . . . . . . . . . . : Παρασκευή, 20 Ιουλίου 2018 7:26:10 μμ
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 285736999
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-86-EE-30-08-00-27-36-28-0C
   DNS Servers . . . . . . . . . . . : fe80::1%9
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

[BlurR]

Why did you manually assign an IP?
What happens if you choose the "Automatic" option?

I did put default gateway to 192.168.1.1 and also tried the auto assign ip method. It didn't work

[socratis]

If you can "ping <DefaultGateway>", if you can "ping 1.1.1.1", if you can "ping download.virtualbox.org", VirtualBox is working as it should. You should look elsewhere for your networking connectivity. Look in your host for firewalls, proxies, antivirus filters, web-cleaning applications, redirectors, etc.

[BlurR]

I can ping my host machine which is 192.168.1.2 also all the other connected device in the router from the vm but can't ping the default gateway. Which means I don't have internet access at all in the vm. My firewall and windows defender is disabled. Don't have any 3rd party antivirus, vpn or web cleaner installed.
I even tried reinstalling the network adapter i'm using ( Usb 2.0 to ethernet adapter)
Tried resetting my router
Still no hope
I really don't know what causing this issue.

[socratis]

Is it really a wired connection or a wireless one? What options do you have?

[fercho]

I have the almost same problem, can ping Host PC, but no other PC on LAN and no Default Gateway, nor Internet.

My setup:
Host: Ubuntu 18.04 LTS with KVM installed/enabled / Ethernet 1 Gbit
Guest: Windows 10-PRO 32bit with Paravirtualized Bridged Network (Win virtio driver OK)
VirtualBox: 5.2.10

* I will try to traduce some important words.

HOST INFO (Ubuntu):

#kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

Note:
enx0050b6850f5d interface ip is 192.168.1.10 (wich is the Host ethernet)

# route -v
Tabla de rutas IP del núcleo
Destiny         Gateway         Genmask         Indic Metric Ref    Interface
default         home            0.0.0.0         UG    100    0        0 enx0050b6850f5d
link-local      0.0.0.0         255.255.0.0     U     1000   0        0 enx0050b6850f5d
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 enx0050b6850f5d
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0

# ifconfig
enp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 4c:cc:6a:dd:5f:7d  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
        device interrupt 19  

enx0050b6850f5d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.10  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::7307:5328:490a:8a2a  prefixlen 64  scopeid 0x20<link>
        ether 00:50:b6:85:0f:5d  txqueuelen 1000  (Ethernet)
        RX packets 1349183  bytes 1665746592 (1.6 GB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 789931  bytes 87257281 (87.2 MB)
        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 1000  (Bucle local)
        RX packets 130214  bytes 219965692 (219.9 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 130214  bytes 219965692 (219.9 MB)
        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:09:c7:16  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

GUEST INFO (Windows)

C:\Windows\system32>ipconfig /all

Configuración IP de Windows

   Nombre de host. . . . . . . . . : DESKTOP-1KQCSG7
   Sufijo DNS principal  . . . . . :
   Tipo de nodo. . . . . . . . . . : híbrido
   Enrutamiento IP habilitado. . . : no
   Proxy WINS habilitado . . . . . : no
   Lista de búsqueda de sufijos DNS: home

Adaptador de Ethernet Ethernet:

   Sufijo DNS específico para la conexión. . : home
   Descripción . . . . . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter
   Dirección física. . . . . . . . . . . . . : 08-00-27-2F-B7-FF
   DHCP habilitado . . . . . . . . . . . . . : sí
   Configuración automática habilitada . . . : sí
   Vínculo: dirección IPv6 local . . . . . . : fe80::f09e:ce1f1dca%6(Preferido)
   Dirección IPv4. . . . . . . . . . . . . . : 192.168.1.136(Preferred)
   Máscara de subred . . . . . . . . . . . . : 255.255.255.0
   Concesión obtenida. . . . . . . . . . . . : sábado, 27 de octubre de 2018 19:52:27
   La concesión expira . . . . . . . . . . . : domingo, 28 de octubre de 2018 19:52:28
   Default Gateway . . . . . . . . . . . . . : 192.168.1.1
   Servidor DHCP . . . . . . . . . . . . . . : 192.168.1.1
   IAID DHCPv6 . . . . . . . . . . . . . . . : 336068647
   DUID de cliente DHCPv6. . . . . . . . . . : 00-01-00-01-23-59-3D-3F-08-00-27-2F-B7-FF
   Servidores DNS. . . . . . . . . . . . . . : 212.231.6.7
                                               8.8.8.8
   NetBIOS sobre TCP/IP. . . . . . . . . . . : habilitado

Ping to Host working:

C:\Windows\system32>ping 192.168.1.10

Haciendo ping a 192.168.1.10 con 32 bytes de datos:
Response from 192.168.1.10: bytes=32 tiempo<1m TTL=64
Response from 192.168.1.10: bytes=32 tiempo<1m TTL=64
Response from 192.168.1.10: bytes=32 tiempo=1ms TTL=64
Response from 192.168.1.10: bytes=32 tiempo<1m TTL=64

Ping statistics for 192.168.1.10:
    Paquetes: send = 4, received = 4, lost = 0
    (0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
    Mínimo = 0ms, Máximo = 1ms, Media = 0ms

Ping to Default Gateway not working:

C:\Windows\system32>ping 192.168.1.1

Haciendo ping a 192.168.1.1 con 32 bytes de datos:
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Response from 192.168.1.136: Host de destino inaccesible.

Ping statistics for 192.168.1.1:
    Paquetes: sent = 4, received = 1, lost = 3
    (75% lost),

Ping to other PC on network not working:

C:\Windows\system32>ping 192.168.1.11

Haciendo ping a 192.168.1.11 con 32 bytes de datos:
Response from 192.168.1.136: Host de destino inaccesible.
Response from 192.168.1.136: Host de destino inaccesible.
Response from 192.168.1.136: Host de destino inaccesible.
Response from 192.168.1.136: Host de destino inaccesible.

Ping statistics for 192.168.1.11:
    Paquetes: sent = 4, received = 4, lost = 0
    (0% lost),

Same PINGs from Host working ok, so only VM guest can't access.

Hour looking for info with no luck.
I don't know what else to look for.
I'd attach the VirtualBox LOG for the Windows Guest.

[kngharv]

Did you managed to resolved this strange issue?

I have similar setup, except that both my host and guest are linux, connected via bridged network. You would think this is a such easy setup, but I ran into the exact same problem.

I can ssh to my guest OS from my host OS.

in the guest OS, I can
ping my host OS' ip address

and it shows that both are in a same class-c intranet

but, i can't ping the gateway in that class-c intranet from my guest OS, thus everything kind of stuck. i can't set DNS servers, i can't update packages

if you managed to solve the problem, please let me know

[scottgus1]

Last post before kngharv's was on 27. Oct 2018. About 7 months ago. This thread is not quite comlpetely dead, but it is in a coma.
kngharv, if there is anything different between your problem and the OP's, you need to start another thread.