AutoVue Server provides IP of wrong adapter if using SERVERNAME or FQDN instead of IP as hostname

Hello AutoVue Community,

A curious behaviour that we have encountered, I relate here...

As a little background, a customer was using an IP address as jvueserver.hostname e.g. jvueserver.hostname=10.0.0.1 as a workaround.

The AutoVue server itself has 2 network adapters, the first appears setup for an internal (backup) network (has the lower Index# and appears first on the network list) set as e.g. IP=10.1.1.1. The second adapter is actually the one that AutoVue should only use and is IP=10.0.0.1. In testing, it was discovered if jvueserver.hostname=SERVERNAME_or_FQDN - plus, the same is set in the hosts file(s) to 10.0.0.1, and the application/client configuration point to the same SERVERNAME_or_FQDN set to IP 10.0.0.1 etc. The clients will still fail at initialization of the AutoVue (JVue) viewer, showing an error pointing at 10.1.1.1:5099 (AutoVue socket