Host Only Adapter Missing after Update

Discussions related to using VirtualBox on Windows hosts.
Post Reply
DrBerndt
Posts: 2
Joined: 21. Nov 2014, 13:15

Host Only Adapter Missing after Update

Post by DrBerndt »

Hello everybody,

I'm using a Windows 7 host to run a Windows 7 Virtual Machine and use a host only network to make them communicate. Coming from VB version VirtualBox-4.2.16-86992-Win I'm used to having an adapter with IP 192.168.56.101 on my host machine - and I think 192.168.56.102 on the guest VM (can't reproduce since now it's broken).

Since i updated to the current version I am only left with the 192.168.56.1 DHCP adapter on the host and nothing else - the address 192.168.56.101 is now assigned to an adapter in the VM. So when trying to make a client listen to the 192.168.56.101 on the host, it fails for obvious reasons. What can I do to get the host only adapter back on the host?

I already experienced this problem with an older update and then reverted back to VirtualBox-4.2.16-86992, but now I'd really like to go with the current version of VB. What point am I missing to make it work?

I'd be glad for any hint on this.
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Host Only Adapter Missing after Update

Post by socratis »

DrBerndt wrote:the address 192.168.56.101 is now assigned to an adapter in the VM
How did that happen? Did you by any chance assigned the IP manually?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
DrBerndt
Posts: 2
Joined: 21. Nov 2014, 13:15

Re: Host Only Adapter Missing after Update

Post by DrBerndt »

Thanks for your attempt to help and sorry about the confusion - apparently the problem was a well known bug in which the Host-Only Adapter is set as a public device and the firewall denies any connection. There are several reports of a solution involving setting a registry key manually. They did help.
Post Reply