Changing the ML address to "localhost", it keeps going back to the IP assigned to the virtual ethernet interface. Did we ever come up with a way to force it to change to and keep "localhost"?
Does "localhost" resolve to the IP that it assigns?
We do prefer to have the IP than localhost, as some processes with "localhost" are not completing correctly to resolve the IP (we have experienced that before).
I am having the exact same problem. THe ML server IP is shown incorrect ...some 192.168.252.136 and unable to change it to either 127.0.0.1 or the expedition server IP address. After entering the correct IP, it reverts to 192.168.252.136. How do we resolve it?
I wasn't mentioning localhost or 127.0.0.1. I was entering the correct IP (expedition server IP) for ML server but despite of clicking save, it use to revert the IP to some 192.168.x.x range which I believe would have coded while extracing the OVA/OVF image. We used OVA to build expedition. At the end, I rebooted expedition and then updated the IP again and this time is worked.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!