Host Only Adapter Missing after Update
Posted: 21. Nov 2014, 13:32
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.
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.