Hi Scott,
thanks for your suggestions. I will need some days to try them
out.
Am 21.06.2018 um 19:14 schrieb Scott
Lewis:
Since
I don't currently have access to a dual-homed server I haven't
been able to test this fully, but really the only thing it does is
to pass the bindAddress to the ServerSocket, rather than using the
default ('0.0.0.0')...which is all interfaces.
Another way (or another use case) to "test" this issue:
* get VirtualBox and fire up a virtual machine
* start the server part inside the virtual machine (this leads to an
endpoint id of the server with the hostname of the virtual machine)
* setup a port forwarding in VirtualBox from the host machine to the
virtual machine (in my example port 8889 from host to port 8889 of
the virtual machine)
* now try to connect to the server part in the virtual machine from
the host machine using "localhost" as hostname in the endpoint
description
-> leads to a network connection from client to server but
without working remote service
Thanks again!
Bye Peter
|