Unwanted network address translations in Windows host

[fiduce]

Hello,
What's exactly happening is yet unclear in my mind.
My host OS is Windows 7 64 bits.
Yesterday I made my first use of a bridged network in one of my VMs. I was still using virtualbox 4.3.6.
Today, I started my computer, and, while virtualbox was not running at all (well, I know that some components run anyway, like network drivers, aso), I tried to access my phone using its a local address : 192.168.0.10
But I could not reach that phone.
Some other computer on my network was able to reach it, but not this one on which I had used the bridged VM.
The web access was still possible.
So I tried a ping toward 192.168.0.10 ... and to my surprise, I saw that some unwanted address translation was occurring in my host system : the ping was not going to 192.168.0.10 but to 192.168.0.101, and that later address is my host computer address.

C:\Windows\System32\drivers\etc\hosts is genuin (there's nothing in it, except commented lines)

I struggled a while, when I finally thought about virtual box.
At first I thought the problem was linked to virtualbox's adapter position in the list of adapters ... but this was not the case : it's position was at the end.
So I started virtual box, thinking about reverting back to a NAT network adapter in the VM.
My best move was to upgrade to version 4.3.12 of virtualbox (as the reminder was showing, I was already thinking about this forum ... and the fact that usually nobody wants to talk about an old version) ... and upgraded to 4.3.12 from 4.3.6.
After I downloaded the upgrade and installed it, everything was again okay : no more address translation and I could reach my phone.

But now I'm a bit scared : is this going to happen again if I start this VM using the bridged network adapter ?

Edit:  Ok, now I'm a few minutes later. After I had written the preceding lines, I looked at virtualbox and accepted the extension pack download. During the download process, I tried another ping ... and, again, the host system was translating the address to my host computer. I tried a second time ... and it came back to the "no-translation" behaviour. Two other tries ... and it stays ok. Then I installed the latest extension pack ... quit virtual box ... and again, I have the bug. So what is happening ? Can this be linked to virtualbox or do I have some other problem (like a virus) ? Before considering virtualbox as the source of this problem, I've spent an hour running an avast analysis, and nothing was wrong. I keep on trying those pings, and they fail now. But the statistic line is false also : it says that 4 packets were received out of 4 ... but I see that the faulty address made my phone unreachable. Can this be linked to virtual box ? I even have some "mixed tries", that means that the four ping attempts are not going to the same address ! (in french) : Code: Select all C:\>ping 192.168.0.10 Envoi d'une requête 'Ping' 192.168.0.10 avec 32 octets de données : Réponse de 192.168.0.101 : Impossible de joindre l'hôte de destination. Réponse de 192.168.0.10 : octets=32 temps=3 ms TTL=64 Réponse de 192.168.0.10 : octets=32 temps=176 ms TTL=64 Réponse de 192.168.0.10 : octets=32 temps=203 ms TTL=64 Statistiques Ping pour 192.168.0.10: Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%), Durée approximative des boucles en millisecondes : Minimum = 3ms, Maximum = 203ms, Moyenne = 127ms Only 3 packets have reached the phone ... but the statistics say that 4 did it ! The more I try, the less I understand what's happening. This problem jeopardizes every private network feature (I was trying to communicate with my wifi android phone running "DroidOverWifi" application). Some informations about the hardware/software configuration : Network adapter : Intel(R) Ethernet Connection I217-V OS : Windows 7 Pro 64 SP1 Memory : 32 GB Processor : i7-4770S My local network is 192.168.0.x and the problem occurs only when I'm pinging a local machine (when I ping 8.8.8.8 or 192.168.1.x, the behaviour is normal : ping is successful or fails, but no address translation occurs). If I ping 192.168.0.11, where there is nothing, I get the same result as with 192.168.0.10 (where my phone should respond) : the address is changed to my host address, and since then, the statistics show 4 packets sent, 4 packets received, but none reached its real destination.

[fiduce]

After further experiments, a must say that, maybe, this "bug" was not related to virtualbox at all.
Maybe I was simply misunderstanding the way Ping works, and the way it reports.

A phone isn't constantly online, especially whaen the screen is off. That can lead to some strange ping behaviour.
The way Ping was reporting the offline periods of my phone, especially as a wifi device, made me suspect virtualbox and some unwanted address translation to be the problem. But maybe I was wrong.

I still don't understand why ping is reporting that my host computer is the target of the ping packets when my phone is sleeping or when there is a problem at the Android side of the connection (the later is more seldom, but not rare : this problem occurs even when the screen of my phone is on and the listening app active ... but that doesn't mean that the ping responding app is also active at that time).

[fiduce]

Ok, this was definitely an Android side problem.
To my defense, I will say that my phone is new (a OnePlus One).
I tried to uncheck the "clever" battery management I found in the "advanced" sub-menu of the wifi settings, and now, the problem seems to be gone ... at least almost