How to get Virtual Box to see Workgroup

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

So... I have got Virtual Box installed on my PC, and I am playing around with Windows PE, which is only command prompt based.

I want to map a network drive from the VM of Windows PE to a drive on my own host PC. Can someone take me through where I am probably going wrong here, does it require bridging a network connection between my own connection and the Virtual Box Network Adapter?

For arguments sake, please use the below information:

PC Name: \\james-pc\
Workgroup: estoril

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Ok first things first, are you getting a DHCP address assigned to the PE image or did you manually assign one? Have you configured DNS correctly and can you ping internal network devices?

In the past when I have played with VMware Player it would create a couple of additional vNIC's to the OS and you would need to bridge between the vNIC and the pNIC to let you share the normal network.

Usually working with PE it's a simple case of using net use * \\james-pc\sharename /user:james-pc\james * where the first * assigns the next available drive letter and the second * requests you to put the password in.

I would check the networking configuration you have configured at the moment as that would be my guess.

 

You need to set your network adaptor to a bridged adaptor in Virtualbox for your VM to "talk" to your host pc.

 

reverb, that is what i thought was the case also... i will attach a screen grab later and you can tell me where i am going wrong, possibly.

 

as promised, I have attached both my network connections and virtual box network settings. if you need any more info, please say the word and i will send these over.

 

You've bridged your VM with your wired NIC, but seem to be connected to your network through your wireless NIC.

I'm not sure why you've bridged your other connections in network settings?

 

in the VM, which setting should it be selected on as i only have the below (attached) options available... i know i am probably missing the obvious here but has been a 'heavy' weekend

- - - Updated - - -

to add just that little bit extra confusion to the table, one of my VMs can see the network share i have setup through oracle virtualbox, but the other cannot and yet settings are exactly the same across them both...

 

Bridged, i think

 

This is the answer for you.

You are using the wrong adaptor. Change it from the Realtek one to the Broadcom one which your are connected to and it should get an IP from your router or dhcp server.

Btw not sure if you know, but in VirtualBox you can create a shared folder on your host and access it from your VM without even bridging your connections. Just create a folder anymore on your host and browse for that folder under "Shared Folder" in your VM settings.

 

I have changed the network setting in VirtualBox from Realtek to the other option after selecting Bridge which is MAC Bridge Miniport... I presume this must be the correct case?

Also, I did find the shared folder on the host settings within VirtualBox which I had already setup, my Server 2008 vm could see this shared folder without a problem and I could map to it, however the Windows-PE couldn't see it and when trying to map said network resource not found.

- - - Updated - - -

Just an update to say that I have resolved this, I must have been half asleep for the last few days as it really was quite obvious what the cause was and this morning i have figured it.

Thanks all

 

What was it?

 

Essentially, it was exactly what you guys were saying that I needed to select the other device, which indeed once changed to MAC Bridge Miniport within Virtual Box settings, and ensuring 'cable connected' tick was in place it then worked after rebooting to ensure settings kicked in.

both VMs and my host pc are now all talking, although I did have another problem where I couldn't write to the folder on the network drive and permissions all appeared to be fine, even administrator could not write to the folder... once again, was just a tick box within folder permissions missing as well as local users & groups settings that i had to adjust.

 

Easy to miss if you're not sure.
I still can't figure out why your other settings are bridged, but if it works, job done