virtualbox.org

Hi all,

I'm running Vista 32bit and virtualbox 3.0.8, everything was working
perfectly and then the vista SP2 was forced on me.

I have xming running on the vista host and can succesfully run
terminals, emacs, etc and have windows popup on the host, I can also
browser the web from within the archlinx virtual machine (ping google,
etc).

However if I run a webserver in the virtual machine I cannot access it
from a browser running on the host. Eg http://192.168.56.101:8000/
just doesn't respond (I tried port 80 too and that didn't work
either).

I have tried turning off the firewall on the host and it doesn't make
any difference. Does anybody have any idea where I might look to fix
this issue?

It is really frustrating! Any help or ideas of where to look would be
greatly appreciated.

-- regards, Simon.

Bridged?
Can you ping the ip of the guest?

It is a Host-only adapter.

I can't ping the guest from the host.

The weird thing is that I have XMing running on the host and I can
open xterms, etc on the host from the guest and can ping from guest to
host. I tried it with the firewall disabled and it didn't make any
difference.

This was all working fine before the Vista Service Pack 2 was forced
on me.

After the upgrade I had another problem with the sound drivers which
required uninstalling the drivers and then rebooting to let vista
reinstall them (as recommended by Microsoft KB).

Maybe the upgrade has affected the virtualbox network drivers in a
similar way?

Hummm,

My update did not effect me in that way, but I guess it could. You can however see if uninstalling, rebooting, then installing by right clicking on the install and then left click on run as admin will repair this for you. If MS has messed up the drivers this would get it back for you. You should not loose the VM's or their settings but I tell everyone to backup first.

Well reinstalling the network driver didn't help, neither did using
some of the registry hacks mentioned in other forum articles related
to vista miss diagnosing the network connection as an unsafe public
network.

However the upgrade to 3.0.10 fixed it!