IP adress conflict and not launching

[Luke5704]

I use virtual box to run my android emulator. It was working fine up until about a week ago. I keep getting the windows error "Windows has detected conflicting IP address". When I launch my android emulator it does not run and just gives a blank screen. When I launch ti from virtual Box I get this error.

Failed to open a session for the virtual machine andy.

Failed to assign the machine to the session (E_FAIL).

Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
Callee RC: E_FAIL (0x80004005)

I would appreciate any help and if you need nay more info I will edit this.

[noteirak]

Provide the VM log files and the guest settings as described in Minimum information needed for assistance.
For the IP conflict, this is something outside of VirtualBox scope that you'll need to address yourself. But the error is pretty clear: two entities (computers, VMs, embeded devices, etc.) are both using the same IP. Configure them properly.
What changed on your computer a week ago?

Also, for the sake of completness, create a new empty VM using all the default values and try to start it. You should at least see the VirtualBox window open and the VirtualBox BIOS logo, then a failure to boot message. Does that work?

[mpack]

I use virtual box to run my android emulator. It was working fine up until about a week ago. I keep getting the windows error "Windows has detected conflicting IP address".

For what it's worth, I get this on a physical network at home. I have a desktop PC running XP and a tablet running Win8.1. The tablet seems to be assigned an IP on standby, but I'm guessing it sometimes uses this IP even after it has expired, e.g. periodic wakeup to check for updates. I fixed it in the router by reserving local IP addresses for devices I use a lot (PC, tablet, printer).

I don't see what this could have to do with failing to run a VM. VBox should be oblivious to the presence or not of network connections, at least not unless you located some VM media on a network share.