After having upgraded to Windows 10 I found that I had some networking issues running the Xamarin Android Player. When trying to start the emulator it would attempt to create a new Host-Only adapter and would constantly fail. I ended up with 6 adapters configured. It was constantly asking me to reboot the computer as well. None of this worked.
The Xamarin Android Player is also expecting a very specific network configuration. What I ended up doing to fix this issue is:
Launch VirtualBox
- Go to File -> Preferences -> Network then the “Host-Only Networks” tab
- Delete all the spurious adapters named “VirtualBox Host-Only Ethernet Adapter <somenumber>#” leaving just one
- Double-click the remaining adapter and enter all these details:
Adapter;
IPv4 Address: 10.71.34.1
IPv4 Network Mask: 255.255.255.0
DHCP Server;
Enabled
Server Address: 10.71.34.2
Server Mask: 255.255.255.0
Lower Address Bound: 10.71.34.101
Upper Address Bound: 10.71.34.199
Now when starting a Xamarin Android Player instance you should see it boot as expected but with full network access and without attempting to create new Host-Only adapters.
After having upgraded to Windows 10 I found that I had some networking issues running the Xamarin Android Player. When trying to start the emulator it would attempt to create a new Host-Only adapter and would constantly fail. I ended up with 6 adapters configured. It was constantly asking me to reboot the computer as well. None of this worked.
The Xamarin Android Player is also expecting a very specific network configuration. What I ended up doing to fix this issue is:
Launch VirtualBox
Adapter;
IPv4 Address: 10.71.34.1
IPv4 Network Mask: 255.255.255.0
DHCP Server;
Enabled
Server Address: 10.71.34.2
Server Mask: 255.255.255.0
Lower Address Bound: 10.71.34.101
Upper Address Bound: 10.71.34.199
Now when starting a Xamarin Android Player instance you should see it boot as expected but with full network access and without attempting to create new Host-Only adapters.