virtualbox.org

"what constitutes "working" even in that sense?" ==> Both internet web browsing & LAN access to host shared folders *at the same time* not one or the other as at present!

5 ipconfig & vboxmanage data files attached!

The remaining 1 vboxmanage data files are attached!

VBoxManage list natnets data file was is blank!

Here is what I want you to try.

• 1) completely shut the guest down, not saved state.
  2) select to use the Bridged adapter *only* in the guest. Disable all other adapters.
  3) Before you try to start the guest go into hosts network settings and remove the VBox host-only adapter
  4) reboot the host start the guest and then see if you can access the Internet from the guest.
  5) then see if you see the LAN.
  6) report back and do not change anything until I tell you.

fao perryg:

I had a feeling the issue is to do with guest addition not installed or properly installed!

I tried to install the amd 64bit guest additions - it had the "dxdirect (experimental)" option ticked which I couldn't untick !

That has now ruined the Win8.1 vm with everything blanked out!

I'll try your last suggestions & let you know once I'm back in working vm!

fao perryg:

No Dice! - After uninstalling host adaptor only in device manager!

With Bridged adaptor (only) - Not only the guest doesn't get internet access but it also stops the host keeping its web access!

Q1. Can installing guest additions fix this issue?

Q2. Can guest additions (amd64) be somehow installed without the dreaded "direct3d (experimental)" option?

Guest additions have nothing to do with networking. You didn't install the guest additions in the host did you?

Now post the following.

VBoxManage list bridgedifs

VBoxManage showvminfo <guest name>

Again you do have a real router right? One that provides DHCP?

According to: https://www.virtualbox.org/manual/ch04. ... ns-windows

The Guest Additions offer the following features - including - Shared folders:
=======================================================================
These provide an easy way to exchange files between the host and the guest. Much like ordinary Windows network shares, you can tell VirtualBox to treat a certain host directory as a shared folder, and VirtualBox will make it available to the guest operating system as a network share, irrespective of whether guest actually has a network
=======================================================================
- Real - Solid Sky Broadband Router - here!
- Brand new Win8.1 vm - Guest additions - not installed on guest vm (yet) nor on host!
===================================================================================
VBoxManage info requested wouldn't copy to txt files (access denied) - so their snaps are zipped as 1 file attached!

Real - Solid Sky Broadband Router - here!
- Brand new Win8.1 vm - Guest additions - not installed on guest vm (yet) nor on host!

When I look this up is says wireless router. Is this true?
As for guest additions they are never installed on the host. That's why they are called guest additions. Installing on the host could cause lots of issues.

So if I understand right you have Internet on the host untill you start the guest ( in bridged mode ) and as soon as you start the guest you not only do not have Internet on the guest but it also causes you to loose the Internet on the host. Is this statement true?

Yes! Bridged gives the guest access to host shared folders BUT No internet connection!

The host itself can't browse the web as soon as the vm is launched!

Guest additions have NEVER been installed on host pc!

Guest additions have NOT been installed on the new Win8.1 vm either!

The broadband router is a "wireless router" - it can connect BOTH wired and wireless clients to internet at the same time!

The host pc is connected by Ethernet cable directly to the router!

Vbox_snoozer wrote:fao perryg:

No Dice! - After uninstalling host adaptor only in device manager!

With Bridged adaptor (only) - Not only the guest doesn't get internet access but it also stops the host keeping its web access!

Q1. Can installing guest additions fix this issue?

Q2. Can guest additions (amd64) be somehow installed without the dreaded "direct3d (experimental)" option?

I have seen that sort of problem on the forum a few times, and the remedy is to update the NIC driver in the host OS.

When you use bridged mode, VirtualBox installs a filter driver which works with the NIC driver in the host (to allow the virtual NIC to share the physical device). If the NIC driver and the filter driver do not work well together, you get problems, including the one you have.

I have never had any problems installing the 64-bit Guest Additions in Windows 8.1 using the WDDM drivers.

"I have seen that sort of problem on the forum a few times, and the remedy is to update the NIC driver in the host OS."

If only it was that simple! My NIC drivers are up-to-date!

"I have never had any problems installing the 64-bit Guest Additions in Windows 8.1 using the WDDM drivers."

See the attached snap of what installing the 64-bit Guest Additions does to my vm's!

I think I'll just stick to using NAT when I need internet & Bridged as & when I need access to host shared folders!

I'm surprised that a formal 1-2-3 step fix for this issue hasn't been found yet!

Internet & LAN access should both by default be made available to all vm's post setup!

Good News Everyone!

The latest VirtualBox version 4.3.16 r95972 has fixed this issue for me!

Using NAT plus Host adaptor only I have BOTH internet and LAN access to shared folders at the same time in a Win8.1 x64 VM!

My host PC internet access is also not affected at all in this scenario!

This new version however seems to be allergic to Win10 Tech prev! Doesn't boot existing or new Win10 vm's!?

But Win10 isn't supported yet I suppose!?

You suppose correctly - I expect it will be quite some time before Win10 is supported as either host or guest.

(p.s. There seems to be something wrong with your keyboard, i.e. it seems to be inserting an exclamation mark on the end of every line you type... ).

Funny that the previous version of Vbox supported Win10 (apart from networking issues) if you fooled it into believing it was Win8.1!

The ! at end of each sentence I blame on Vbox keyboard driver - I want my money back!