Windows 10 Build 10041 - Bridged Network Can't See Ethernet

[loukingjr]

So my Host is Windows 10 Home edition.
and my Guest is OSX 10.11 El Capitain.

Important notice regarding Mac OS X as Guest

[Giusi]

I have just Upgrade my Windows 7 to Windows 10.
Encountered same problem as describe above "Bridge network can't see Ethernet"
Then I downloaded latest VB 5.0.3 Build R102290.
Including extention pack for this version.

And now I can work with bridge.
So my Host is Windows 10 Home edition.
and my Guest is OSX 10.11 El Capitain.

"If a test build wasn't advertised in some ticket or -> a forum post <- as fixing some specific problem, it's safe to assume that it doesn't fix that problem. You don't need to post "build xyz didn't fix my issue" over and over and over
->when no one ever claimed it did.<- "..:

in my case that latest test build did not solve at all

cheers

[loukingjr]

in my case that latest test build did not solve at all

cheers

Giusi, do you not understand your posts are exactly what michaln was talking about? There is no need to keep posting "it didn't work for me" over and over.

[mpack]

I can tell you that I'm going to start deleting such redundant posts if they keep happening.

[Giusi]

is there anyone that has just proved the last r102449 ?

[Giusi]

5.0.3.102449 do not solve bridge network..and for me has been a backward step in the countrary direction cause
,instead of r102375,
i not able again to see my realtek adapt if i choose network bridge..
so may be the enumerating issues has come back..
a nightmare..

[Giusi]

latest r102467 restablish the situation of r102375 netadapter realtek now visible and choosable but if selected bridge network vm fails to start

so even with some steps in the right direction the issue is still there..

[Xlot]

I've got bridged networking working fine on a Windows 10 Pro host (my desktop), with one caveat..

Using VB 5.0.3-102467
Motherboard has 2x Realtek RTL8111E onboard (its an old gigabyte x58a-ud5 - has vt-d support and a hex-core xeon @ 3.7GHz)

I can set up a bridged network adapter on a guest (Centos7 in this case) and it works fine - gets ipv4 address from my internal dhcp server (on another host), and can see the network in the house, as well as be seen from other hosts.

The only issue I have now is that there's no traffic exchange between the host's interface and the bridged interface. Both of them work fine, just no route between them.

My workaround is to plug the second Realtek into my switch too, and use the second adapter for the bridge to the guest VM's, and because the host's default route is via the other adapter, I can get traffic between guest/vm via the switch.

[fragtion]

I've got bridged networking working fine on a Windows 10 Pro host (my desktop), with one caveat..

Using VB 5.0.3-102467
Motherboard has 2x Realtek RTL8111E onboard (its an old gigabyte x58a-ud5 - has vt-d support and a hex-core xeon @ 3.7GHz)

I can set up a bridged network adapter on a guest (Centos7 in this case) and it works fine - gets ipv4 address from my internal dhcp server (on another host), and can see the network in the house, as well as be seen from other hosts.

The only issue I have now is that there's no traffic exchange between the host's interface and the bridged interface. Both of them work fine, just no route between them.

My workaround is to plug the second Realtek into my switch too, and use the second adapter for the bridge to the guest VM's, and because the host's default route is via the other adapter, I can get traffic between guest/vm via the switch.

Exact same problem here. VB 5.0.3-102467 working great on Win10, apart from host being unable to see guest when using bridged networking. Other devices on the network see it fine. Workaround which worked for me was to route the guest's IP, on the host, via the network's default gateway

ADSL Router/gateway: 192.168.0.1
Windows Host: 192.168.0.10 (default gw: 192.168.0.1)
Linux Guest: 192.168.0.20 (default gw: 192.168.0.1)

After adding the following to the Windows Host, they could see each other:
C:\windows\system32> route add 192.168.0.20 mask 255.255.255.255 192.168.0.1 -p

Will just have to remember to delete this persistent static route once the bug is fixed...

[Giusi]

" to route the guest's IP, on the host, via the network's default gateway"..:

so you are able before this yr workaround to start the guest machine?
and anyway yr guest is a linux
or have you tried also with a guest of windows?

thxs!

cheers!

[hakster]

Hi all,

Just saw that 5.0.4 (non-dev build) is just out for download, and the red warning about Win 10 guests and hosts not being fully supported has disappeared. Not in a position to try it myself right now, but can anyone confirm if this bridged networking issue has been addressed in 5.0.4? The changelog has this which looks hopeful:

•Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437)

If anyone can confirm actual success/fail, that would be appreciated.

[Giusi]

just to let you know that the stable 5.04 vbox release, with no more advice of incompatibility with win 10,
has still the issue already reported for bridge network
any ideas..?

[ExoTitan]

Hi all,

Just saw that 5.0.4 (non-dev build) is just out for download, and the red warning about Win 10 guests and hosts not being fully supported has disappeared. Not in a position to try it myself right now, but can anyone confirm if this bridged networking issue has been addressed in 5.0.4? The changelog has this which looks hopeful:

•Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437)

If anyone can confirm actual success/fail, that would be appreciated.

Just installed 5.0.4 and my network still gets hosed.

[bobBuilder]

No unfortunately the bridge is not working on my host OS (Windows 10). The NAT adapters are not even connecting my directly to the internet. Not sure if it is my OS or VB is not fully supported yet.

[Giusi]

latest r102588 doesn't solve
network bridge