Apparently QV listens on all available IP adresses, and found no fine configuration of theese. It seems to work fine as it is.
However, there might be something messed up in Windows networking. At any time, 127.0.0.1 and localhost must resolve to one of the local IP addresses. And QV should be listening there too. Ask your syadmin to look at IPv6, these are not always easy.
Unfortunately I cannot confirm your observation about "listens on all addresses":
While the Management Console upon start-up lists all available addresses in an "Information" entry in its log under C:\ProgramData\QlikTech\QlikviewManagementService\Log, it definitely does NOT bind all of them in my case.
As "netstat -a" clearly shows there is no process at all bound to 0.0.0.0:4780 (or 127.0.0.1:4780 for that matter), only to <certainip-address>:4780. :-(
Looking at logs, there is line bellow listing all 3 network cards. Successfully connected to QEMC on all three. In netstat -n | find "4780" there are all 3 IP adresses.
Network Information=Connected: True, Hostname: XXXXX, IP Address 1: a.a.a.a, IP Address 2: b.b.b.b, IP Address 3: c.c.c.c,
There are many QV servers around, all have at least two network cards, and this is working fine with many releases of QV 8 and QV 9