Hello! I'm wondering if you could help me with this problem. I'm trying to set Virtualbox so that the host can access services on the virtual machine and has permission to stop and start them. I've tried all the things recommended for ordinary remote computers and haven't met with any luck. I'm thinking the reason it's not working is something to do with the specifics of the virtual machines. Each machine pings the other but apart from that neither seems to know the other exists. I can't add the host to a group in Computer Management > Local Users and Groups because there is no remote computer listed there.
I've looked at tutorials on networking but they only go up to the stage where each computer pings the other. I haven't a clue what I'm supposed to do beyond that to give the host permissions. Can anyone give me some advice on this? Thanks.
Granting host permissions
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Granting host permissions
First you have to establish a working network between the host and guest. See the manual chapter 6 for Virtualbox networking.
If you want the host and guest to have their own private network, use Host-Only networking. If you want the guest to be visible on your host and all other devices on your house/office network, use Bridged networking. (Note that Bridged doesn't always work on host Wi-Fi adapters because of poorly-written host Wi-Fi adapter drivers or Wi-Fi access point firmware.)
After the network is set up, then everything else is done the same way you'd do between two physical PCs. Keep in mind any firewalls that have to have ports opened for the desired services. On the permissions angle, often you need to have the username and password of a valid account that can use or modify the things you want on one PC. Then you give that username and password to the other PC and that PC can get into the first PC. For Windows PCs you use the pc name or domain name and the account user name like this:
PC in a non-domain peer-to-peer network: (typical with home routers)
PCname\username
password
PC in a Windows domain: (common in offices)
domainname\username
password
If you want the host and guest to have their own private network, use Host-Only networking. If you want the guest to be visible on your host and all other devices on your house/office network, use Bridged networking. (Note that Bridged doesn't always work on host Wi-Fi adapters because of poorly-written host Wi-Fi adapter drivers or Wi-Fi access point firmware.)
After the network is set up, then everything else is done the same way you'd do between two physical PCs. Keep in mind any firewalls that have to have ports opened for the desired services. On the permissions angle, often you need to have the username and password of a valid account that can use or modify the things you want on one PC. Then you give that username and password to the other PC and that PC can get into the first PC. For Windows PCs you use the pc name or domain name and the account user name like this:
PC in a non-domain peer-to-peer network: (typical with home routers)
PCname\username
password
PC in a Windows domain: (common in offices)
domainname\username
password