virtualbox.org

I have a Windows 7 Host running both Ubuntu and CentOS guests. The guests can connect and surf the net fine. The guests have bridged adapters.

I cannot however access any services on the Guests. Web Servers, SSH. The guests also do not respond to pings.

I made sure to shut down all firewalls / IPTables and i've never had this issue before so I'm a little at a loss on how to start troubleshooting it.

Anyone have any ideas?

Same problem here.

VirtualBox: 5.0.4
Host: Windows 10 64bit
Guests: Linux Mint, Windows 7
Network: Bridged

All guests have fine internet connectivity. But i cannot reach the guest from the host, not even ping them.

Same issue.

Virtualbox 5.0.5 last build
Windows 10 Pro 64bit host.
Virtual Machines : FreeNas 0.9 , Windows Xp, Linux Mint.
Bridge Network
No ping / Services (web/ftp) IN host but VM works ok with ethenet and others VM with bridge adapter.
Windows 10 not show VM in workgroup or share resources.

So is this an actual bug? Has it been reported?

There is already a bug filed:
https://www.virtualbox.org/ticket/14457

It a also contains a workaround:
- Open the network adapters in Windows 10
- Open properties of the adapter used in your guest OS
- Disable IPv6 -> OK
- Open properties again
- Enable IPv6 -> OK

This fixed the issue on my machine.

I believe that this test build resolves the issue properly.

flof wrote:There is already a bug filed:
https://www.virtualbox.org/ticket/14457

It a also contains a workaround:
- Open the network adapters in Windows 10
- Open properties of the adapter used in your guest OS
- Disable IPv6 -> OK
- Open properties again
- Enable IPv6 -> OK

This fixed the issue on my machine.

if i choose network bridge i'm not able to start the WM
so i cannot use the workaround because i'm not able to start the guest..
win 10 home 64 host
win xp sp3 pro guest

with NAT no issue

Giusi wrote:
if i choose network bridge i'm not able to start the WM
so i cannot use the workaround because i'm not able to start the guest..
win 10 home 64 host
win xp sp3 pro guest

with NAT no issue

Presumably you are still falling foul of the issue that you raised on ticket 14428 which most likely is down to something else on your computer that is affecting the VirtualBox installation.

If you aren't going to provide the information from the installer logs onto that ticket to help the developers figure out what is going wrong then don't expect it to magically get fixed. The general rule in software development is "if you can't reproduce a problem, you can't fix it".

Ok! Thanks for the info. I'll try that when I get back to my computer this evening and report back. Thanks for the pointers everyone

andyp73 wrote:I believe that this test build resolves the issue properly.

WORKS GREAT! Thanks for the help everyone!