This is a topic that is related to the question I've posted a month ago : Wrong NIC address in the inventory (virtual adapter instead of Ethernet adapter)
After some tests I made with clients connected through CSA to the core server, now the IP address that sends to the core belongs to the Virtual Box virtual adapter instead of the right one (appart from registering the wrong primary NIC card for the device) :
This is what shows the Core console when these devices are connecting from external networks through CSA:
For the first one, device CR3533006DC0052, the network settings when connecting throgh CSA were this:
Back to the corporate network, the device reported the right IP address although the primary NIC in the "Network node" is still the one that belongs to Virtual Box.
Then I choose another device that were reporting correctly their IP address and NIC either throgh CSA or directly to the Core server : CR3533006DC0087. But I decided to install the latest version of Virtual Box 5.0 available on it and repeated the connectivity tests, the result was that it began to have the same problems as the first device.
I have been looking into the community for similar cases and the few ones that I have found, the solution that was proposed was to set up correctly the network binding order :
Both devices were configured following the recomendations that I found in this article : Issue: The IP address of the managed device isn't updated - the IP address of the wrong network connection is reported
The binding order on both devices (configured before the tests are done) is what follows : 1 Ethernet, 2 Wireless, 3 VMNet1, 4 VMnet8, 5 VirtualBox Host-Only Network.
Nonetheless, it still reporting the wrong IP and the wrong NIC address for the primary adapter. I have even uninstall the agents and reinstall again but with no results.
Has somebody experienced this issue or is any workaround I can try?
Thanks everybody for your time if you have come to the end of this article!