Bridged networking kills all networking

[innovine]

Hi,
I am running VirtualBox on windows 10, with a Fedora 27 guest image.
If I leave the network configuration to "Not Attached" then all is ok.
However, if I enable Bridged networking, the networking in the VM AND the win10 networking stop working. Each can ping the other, but nothing else. If I shut down the VM, the windows networking will start to work again after a short pause.

I've used VirtualBox 5.1.30 and 5.2.8, with and without the extension installed. Each time the results are the same. As the guest OS boots up, just before the login screen is shown, the host win10 OS networking stops working, and after logging into the guest, there is no networking there either (although it looks like it received an IP address from my upstream DHCP server, not entirely sure about that). On shutting the guest OS down, win10 networking is restored after about a minute.

I'd really appreciate some help in getting this to work as I'm at a total standstill right now

[mpack]

Well, this is not a systemic VirtualBox fault, otherwise we'd all see it. I assume it's a conflict with another non-Microsoft network driver installed on your host.

[innovine]

Tips on how to resolve this would be most welcome.

[mpack]

Well, tips on how to use Windows is just a teeny bit beyond our remit here. Only you can know what other software you have installed on that PC, only you are able to sit in front of that PC and look at what other network drivers are installed. That's what you need to do, and obviously you should regard with suspicion any non-native drivers attached to a NIC.

[innovine]

Actually it appears that the network does kinda work. I get nothing in the host OS, but in the guest, I get an eventual response to ping:

Code: Select all

PING google.se (172.217.20.35) 56(84) bytes of data.
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=1 ttl=53 time=8358 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=2 ttl=53 time=8990 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=3 ttl=53 time=9588 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=4 ttl=53 time=10212 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=5 ttl=53 time=10812 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=6 ttl=53 time=11387 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=7 ttl=53 time=11936 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=8 ttl=53 time=12460 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=9 ttl=53 time=13035 ms
From virtualmachine (192.168.0.111) icmp_seq=12 Destination Host Unreachable
From virtualmachine (192.168.0.111) icmp_seq=13 Destination Host Unreachable
From virtualmachine (192.168.0.111) icmp_seq=14 Destination Host Unreachable
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=10 ttl=53 time=18492 ms
64 bytes from 172.217.20.35 (172.217.20.35): icmp_seq=11 ttl=53 time=19048 ms

I don't know what could cause any conflicts, I do not have any VPN software installed. I have the motherboard drivers installed. That is not shown under Uninstall Program. I'm open for suggestions on how to remove them, if that may be the problem. I am reluctant to uninstall and reinstall windows, but I'm getting really desperate now. I don't know how to troubleshoot this issue further. Happy to open some kind of TeamViewer connection if you think you can help by looking at the computer.

I only have two network devices being shown, "VirtualBox Host Only Network #2" and "Ethernet", which is wired to my router. The properties->driver details for "Ethernet" say its Intel(R) Ethernet Connection (2) 1219-V and the driver provider is Intel Corporation, signed by Microsoft Windows Hardware Compatibility. Seems normal enough to me..

[Martin]

Are you connected to a private or a company network?
Some enterprise networks disable the port when you connect more than one system.

[innovine]

Are you connected to a private or a company network?
Some enterprise networks disable the port when you connect more than one system.

My own private network, which doesn't do anything special.
I realized I can work around the issue by using NAT (which works fine) and just port forwarding the services I require, but knowing what the issue is would still be nice.

[socratis]

From the host, post the output of:

Code: Select all

ipconfig /all

From the guest, post the output of:

Code: Select all

ifconfig -a

Right-click on the VM, Show in Explorer. ZIP that ".vbox" file and attach it to your response.

[innovine]

Ok, really strange. I was using NAT and port forwarding with an older version of VirtualBox and this was working. This morning when I fired up VirtualBox is reminded me there was a newer version available, so I performed exactly these steps:
- Uninstalled the old version via control panel
- Ran the installer for 5.2.8
- Ran the VM with the NAT settings for a little while
- Edited my VM machine settings. Turned NAT to Bridged Adapter
- Restarted the network service in Fodora (the guest)

Now bridged adaper is working fine.

I do not see anything different at all to what I was trying, multiple times, last week. I guess something is different, but I have absolutely no idea what that might be. I suppose the host was restarted during the weekend...
Anyway, I am now going to try get my planned work done, but if the problem appears again I'll post the info you requested above.
Thanks !