Page 1 of 2
Unable to network
Posted: 29. Dec 2016, 19:05
by Petedagrk
So I installed a VBox instance with Server 2008 and I can not get the VM to get an internet connection. Can anyone tell me how I use my wifi to use the same connection as my laptop.. thanks
Re: Unable to network
Posted: 29. Dec 2016, 19:28
by Petedagrk
This is a screenshot of my VM
Re: Unable to network
Posted: 29. Dec 2016, 20:27
by socratis
A screenshot of a computer not having internet access is not particularly useful. I believe you. The details unfortunately are the ones that are missing.
If you're on Windows Host, ppen a Command Prompt window. Navigate to the VirtualBox installation directory (typically "C:\Program Files\Oracle\VirtualBox\"). If you're on Linux, OSX, just open Terminal. Type the command:
It will generate a file. Attach that file in your response. See the "Upload attachment" tab below the reply form.
Re: Unable to network
Posted: 29. Dec 2016, 20:33
by Petedagrk
Host is runnning on Windows 8, the guest on VM is Windows Server 2008
Re: Unable to network
Posted: 29. Dec 2016, 20:37
by Petedagrk
socratis wrote:A screenshot of a computer not having internet access is not particularly useful. I believe you. The details unfortunately are the ones that are missing.
If you're on Windows Host, ppen a Command Prompt window. Navigate to the VirtualBox installation directory (typically "C:\Program Files\Oracle\VirtualBox\"). If you're on Linux, OSX, just open Terminal. Type the command:
It will generate a file. Attach that file in your response. See the "Upload attachment" tab below the reply form.
Re: Unable to network
Posted: 29. Dec 2016, 20:50
by socratis
Notice what I said:
Petedagrk wrote:Navigate to the VirtualBox installation directory (typically "C:\Program Files\Oracle\VirtualBox\")
as in:
Please note the quotes (""). They are required when there is a space in the path.
And a couple of general things:
- Do not quote the whole message. Use the "PostReply", instead of the "Quote", unless you want to quote specific parts.
- Do not attach screenshots. They occupy a lot more space than the text and they're not searchable.
Re: Unable to network
Posted: 29. Dec 2016, 20:59
by Petedagrk
The system cannot find the path specified.
Re: Unable to network
Posted: 29. Dec 2016, 21:16
by Petedagrk
ok so i executed that command and it just shows this but i dont see a file generated
C:\Program Files\Oracle\VirtualBox>
Re: Unable to network
Posted: 29. Dec 2016, 21:25
by socratis
Navigate to the VirtualBox installation directory (typically "C:\Program Files\Oracle\VirtualBox\").
That was the first part, the part you had a problem even changing the directory. Then there were other instructions following:
Make sure that you replace the
"<Your_VM_Name_here>" with your actual VM name. Within the quotes. For example
"Windows 2012".
Re: Unable to network
Posted: 29. Dec 2016, 21:33
by Petedagrk
I have no idea why it says Error no such machine when thats what i named it.
Re: Unable to network
Posted: 29. Dec 2016, 21:36
by scottgus1
I have never heard of "Vboxbugreport" so I tried it on my Windows host. At the end of the scrolling text in the command window it says: "Report was written to '2016-12-29-19-25-54-bugreport.tgz' " The location of said .tgz report file is in the folder where the command window was pointing when to command was run.
Seems to be quite an extensive stack of troubleshooting files wrapped up in a Linux-y zip folder. (Something like 7-zip will be needed on Windows to open the .tgz file and see what's inside.
Usually you can use Virtualbox's Bridged or NAT networking styles to get a guest to have access to your host's network. See Section 6 in the manual. NAT is easiest to get internet going, Brdged makes your guest look like another PC on the physical network. Note that if you are trying to Bridge to a host Wi-Fi adapter, you may not get a connection. Bridged doesn't always work with Wi-Fi, due to poorly-written Wi-Fi adapter drivers and/or wireless access point firmware. If it works, good. If it doesn't, even after updating the Wi-Fi adapter card driver, then you won't be able to Bridge with Wi-Fi.
Re: Unable to network
Posted: 29. Dec 2016, 21:42
by Petedagrk
I got the file unfortunately it is too big to attach
Re: Unable to network
Posted: 29. Dec 2016, 21:52
by scottgus1
I'm not certain why Socratis wants all the info found in the bugreport file, but you could try extracting all the info therein back to uncompressed files in a folder then zip parts of the file stack until you can get them under the forum's limit.
You could also try setting your guest's network card attachment type to NAT. If that doesn't get internet going, please attach the guest's .vbox 'recipe' file as a zip file, using the Upload Attachment tab under the textbox where you type new posts. You can find the guest's .vbox file by right-clicking the guest in the main Virtualbox window and choosing Show in Explorer/Finder/whatever-your-PC-calls-it. Be sure your host OS is set to show known extensions.
Also useful would be a text file of the output of the command 'ipconfig' run in a command window in the guest, and similar on the host if Windows or 'ifconfig' for Linux (maybe Mac?)
One other thing, make sure the guest recognizes the virtual network card presented to it by Virtualbox. I suspect it is working based on your screenshot, but let's cover as many bases as I can think of for now

Re: Unable to network
Posted: 29. Dec 2016, 21:58
by Petedagrk
One other thing, make sure the guest recognizes the virtual network card presented to it by Virtualbox. I suspect it is working based on your screenshot, but let's cover as many bases as I can think of for now
What do you mean?
Re: Unable to network
Posted: 29. Dec 2016, 22:05
by Petedagrk
Heres the vbox recipe file