This points at a common linux misconfiguration where the /etc/hosts file ends up
having bad values in it that map the hostname to 127.0.0.1 and vice-versa.
The end result is that the LUS binds to localhost instead of the interface
address for a network interface, and then tells you this is where it is bound,
which of course you can not connect to.
If you will do a "netstat -an |grep LISTEN" on the server that the LUS is
running on, you should see that there is no external LISTEN on 4160, only a
localhost binding.
You are finding the service via multicast, but then getting back an address that
you can't connect to it with I am guessing.
Gregg Wonderly
Patrick Wright wrote:
This reminds me of a situation where some of our BasicObjectEndpoints
were ending up with the loopback address. When a remote server would
try to contact on that endpoint, it of course wouldn't find us.
HTH
Patrick
